From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org, edumazet@google.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, willemb@google.com,
syzkaller@googlegroups.com, liuhangbin@gmail.com,
linux-kernel@vger.kernel.org, joneslee@google.com
Subject: Re: kernel BUG in __skb_gso_segment
Date: Thu, 22 Dec 2022 11:20:01 +0200 [thread overview]
Message-ID: <544202ef-37f8-9055-7f2e-69fa46907930@linaro.org> (raw)
In-Reply-To: <Y6L/F2Hwm7BRdYj8@kroah.com>
On 21.12.2022 14:41, Greg KH wrote:
> On Wed, Dec 21, 2022 at 09:42:59AM +0200, Tudor Ambarus wrote:
>>
>>
>> On 21.12.2022 09:37, Greg KH wrote:
>>> On Wed, Dec 21, 2022 at 09:28:16AM +0200, Tudor Ambarus wrote:
>>>> Hi,
>>>>
>>>> I added Greg KH to the thread, maybe he can shed some light on whether
>>>> new support can be marked as fixes and backported to stable. The rules
>>>> on what kind of patches are accepted into the -stable tree don't mention
>>>> new support:
>>>> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>>>
>>> As you say, we don't take new features into older kernels. Unless they
>>> fix a reported problem, if so, submit the git ids to us and we will be
>>> glad to review them.
>>>
>>
>> They do fix a bug. I'm taking care of it. Shall I update
>> Documentation/process/stable-kernel-rules.rst to mention this rule as
>> well?
>
> How exactly would you change it, and why?
Something like this:
https://lore.kernel.org/linux-kernel/20221222091658.1975240-1-tudor.ambarus@linaro.org/T/#u
Cheers,
ta
prev parent reply other threads:[~2022-12-22 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 13:12 Tudor Ambarus
2022-12-20 18:27 ` Willem de Bruijn
2022-12-21 7:28 ` Tudor Ambarus
2022-12-21 7:37 ` Greg KH
2022-12-21 7:42 ` Tudor Ambarus
2022-12-21 12:41 ` Greg KH
2022-12-22 9:20 ` Tudor Ambarus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544202ef-37f8-9055-7f2e-69fa46907930@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=joneslee@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®