From: Greg KH <gregkh@linuxfoundation.org>
To: Tadeusz Struk <tadeusz.struk@linaro.org>
Cc: stable@vger.kernel.org, Oliver Neukum <oneukum@suse.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] usbnet: sanity check for maxpacket
Date: Tue, 26 Oct 2021 17:19:02 +0200 [thread overview]
Message-ID: <YXgcZuPl+R/w28ye@kroah.com> (raw)
In-Reply-To: <6e76d1d0-fb73-13b4-0881-6bdd8b69588f@linaro.org>
On Tue, Oct 26, 2021 at 08:08:37AM -0700, Tadeusz Struk wrote:
> On 10/26/21 08:03, Greg KH wrote:
> > On Tue, Oct 26, 2021 at 07:52:00AM -0700, Tadeusz Struk wrote:
> > > On 10/25/21 22:43, Greg KH wrote:
> > > > > It should be applied to stable kernels: 5.14, 5.10, 5.4, 4.19, 4.14, 4.9, 4.4
> > > > It's already in the latest stable -rc releases, do you not see it there?
> > >
> > > I haven't checked the rc releases, just the latest stable versions.
> > > Now I also see Sasha Levin's submissions on the stable mailing list archive.
> > > All good. Sorry for the noise.
> >
> > Also note that there is a bug in this commit, so it was dropped from the
> > stable queues until the fix for this hits Linus's tree.
> >
>
> Good to know. Ideally we could also add some netif_warn() message for the user.
Why? It's an "obviously broken" device that is created just to try to
harm the kernel. No need to be noisy about it.
thanks,
greg k-h
prev parent reply other threads:[~2021-10-26 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:20 [PATCH] usbnet: sanity check for maxpacket Tadeusz Struk
2021-10-26 5:43 ` Greg KH
2021-10-26 14:52 ` Tadeusz Struk
2021-10-26 15:03 ` Greg KH
2021-10-26 15:08 ` Tadeusz Struk
2021-10-26 15:19 ` Greg KH [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=YXgcZuPl+R/w28ye@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=oneukum@suse.com \
--cc=stable@vger.kernel.org \
--cc=tadeusz.struk@linaro.org \
/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