Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #78089 > unrolled thread

Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y

Started byComputer Enthusiastic <computer.enthusiastic@gmail.com>
First post2023-01-27 21:10 +0100
Last post2023-02-05 18:20 +0100
Articles 4 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Request to cherry picking a patch to fix bug #989705 for kernels  5.10.y Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2023-01-27 21:10 +0100
      Re: Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y Diederik de Haas <didi.debian@cknow.org> - 2023-01-27 22:40 +0100
      Re: Request to cherry picking a patch to fix bug #989705 for kernels  5.10.y Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2023-01-28 16:10 +0100
      Re: Request to cherry picking a patch to fix bug #989705 for kernels  5.10.y Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2023-02-05 18:20 +0100

#78089 — Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y

FromComputer Enthusiastic <computer.enthusiastic@gmail.com>
Date2023-01-27 21:10 +0100
SubjectRequest to cherry picking a patch to fix bug #989705 for kernels 5.10.y
Message-ID<FSDcR-1A08-13@gated-at.bofh.it>
Hello,

The bug #989705 [1] is currently closed. It was solved for kernels 
version 5.15+ using the patch [2] from upstream.

This patch [2] applies to kernel version 5.10.y, too. I used it with a 
custom built kernel since it was published .

The author of the patch acknowledged that the patch applies to kernel 
version 5.10.y asking me to send it out to the stable mailing list. I 
did it, but I did not receive an answer. I tried to peek upstream, but 
again no answer.

Therefore, I'm sending this post to ask the debian-kernel mailing list 
if it is possibile to cherry pick the patch [1] to make it land in the 
next release of Debian Kernel 5.10.y.

Let me know if I can help in any way. I cannot update bug #989705 
because it is currently closed.

Thanks in advance for your attention.

---
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5&id=6b04ce966a738ecdd9294c9593e48513c0dc90aa

[toc] | [next] | [standalone]


#78091 — Re: Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-01-27 22:40 +0100
Subject Re: Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y
Message-ID<FSEBX-1AIM-9@gated-at.bofh.it>
In reply to#78089

[Multipart message — attachments visible in raw view] — view raw

On Friday, 27 January 2023 21:05:47 CET Computer Enthusiastic wrote:
> This patch [2] applies to kernel version 5.10.y, too. I used it with a
> custom built kernel since it was published .
> 
> The author of the patch acknowledged that the patch applies to kernel
> version 5.10.y asking me to send it out to the stable mailing list. I
> did it, but I did not receive an answer. I tried to peek upstream, but
> again no answer.

I noticed in [2] this: "Cc: stable@vger.kernel.org # v5.15+"

The post on marc.info (try to use lore.kernel.org links as that works easier 
for most people) seems to be posted to the 'linux-kernel' list, which I 
*think* is not the same as 'stable@vger.kernel.org'.

So I would suggest to try again by sending it to stable.vger.k.o with explicit 
mention of kernel 5.10.
GKH is a busy man so I recommend to take your time to construct an email which 
is as short as possible, but still contains all the info needed to evaluate 
the request.

I would recommend to mention the following things:

Commit ID in 5.15 = 3640cdccbe75b8922e5bfc0191dd37e3aaa24833

Link to post in which the patch author said they'd ACK it for 5.10:
https://lore.kernel.org/all/CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw@mail.gmail.com/

In your mail make sure the link doesn't break over 2 lines like it does above.

HTH,
  Diederik
> ---
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h
> =v6.0-rc5&id=6b04ce966a738ecdd9294c9593e48513c0dc90aa

[toc] | [prev] | [next] | [standalone]


#78098

FromComputer Enthusiastic <computer.enthusiastic@gmail.com>
Date2023-01-28 16:10 +0100
Message-ID<FSV05-1LbM-3@gated-at.bofh.it>
In reply to#78091
Hello,

On 27/01/2023 22:35, Diederik de Haas wrote:
> On Friday, 27 January 2023 21:05:47 CET Computer Enthusiastic wrote:
>> This patch [2] applies to kernel version 5.10.y, too. I used it with a
>> custom built kernel since it was published .
>>
>> The author of the patch acknowledged that the patch applies to kernel
>> version 5.10.y asking me to send it out to the stable mailing list. I
>> did it, but I did not receive an answer. I tried to peek upstream, but
>> again no answer.
> 
> I would recommend to mention the following things:
> 
> Commit ID in 5.15 = 3640cdccbe75b8922e5bfc0191dd37e3aaa24833
> 
> Link to post in which the patch author said they'd ACK it for 5.10:
> https://lore.kernel.org/all/CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw@mail.gmail.com/
> 
> In your mail make sure the link doesn't break over 2 lines like it does above.
> 
> HTH,
>    Diederik

Thanks for your suggestions. This [1] is the reference to my new 
request. I hope I dit it right.

---
[1] 
https://lore.kernel.org/stable/20220819200928.401416-1-kherbst@redhat.com/T/#ebac71b81ccec2fb3d1c467e73f4f46667ef75296

[toc] | [prev] | [next] | [standalone]


#78198

FromComputer Enthusiastic <computer.enthusiastic@gmail.com>
Date2023-02-05 18:20 +0100
Message-ID<FVQQh-3Fj4-1@gated-at.bofh.it>
In reply to#78091
Hello Diederik,

On 27/01/2023 22:35, Diederik de Haas wrote:
> On Friday, 27 January 2023 21:05:47 CET Computer Enthusiastic wrote:
>> This patch [2] applies to kernel version 5.10.y, too. I used it with a
>> custom built kernel since it was published .
>>
>> The author of the patch acknowledged that the patch applies to kernel
>> version 5.10.y asking me to send it out to the stable mailing list. I
>> did it, but I did not receive an answer. I tried to peek upstream, but
>> again no answer.
> 
> I noticed in [2] this: "Cc: stable@vger.kernel.org # v5.15+"
> 
> The post on marc.info (try to use lore.kernel.org links as that works easier
> for most people) seems to be posted to the 'linux-kernel' list, which I
> *think* is not the same as 'stable@vger.kernel.org'.
> 
> So I would suggest to try again by sending it to stable.vger.k.o with explicit
> mention of kernel 5.10.
> GKH is a busy man so I recommend to take your time to construct an email which
> is as short as possible, but still contains all the info needed to evaluate
> the request.
> 
> I would recommend to mention the following things:
> 
> Commit ID in 5.15 = 3640cdccbe75b8922e5bfc0191dd37e3aaa24833
> 
> Link to post in which the patch author said they'd ACK it for 5.10:
> https://lore.kernel.org/all/CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw@mail.gmail.com/
> 
> In your mail make sure the link doesn't break over 2 lines like it does above.
> 
> HTH,
>    Diederik
>> ---
>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705
>> [2]
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h
>> =v6.0-rc5&id=6b04ce966a738ecdd9294c9593e48513c0dc90aa
> 

Just a feedback.

Thanks for your tips.

Greg Kroah-Hartman backported the patch into Linux 5.10.166 [1].

Therefore it will hopefully land in the next Debian stable point release 
when it will be released.

I would like to thank Salvatore Bonaccorso who helped me to explain Greg 
the request for backporting the patch:

---
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.166&id=8fe3e574b3ac426ff4a11299f098e1c91538f3e5

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web