From: Greg KH <gregkh@linuxfoundation.org>
To: Maik Stohn <maik.stohn@seal-one.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
nsaenzjulienne@suse.de, stable@vger.kernel.org
Subject: Re: patch "xhci: Fix crash if scatter gather is used with Immediate Data" added to usb-linus
Date: Sun, 28 Jul 2019 13:41:42 +0200 [thread overview]
Message-ID: <20190728114142.GA12033@kroah.com> (raw)
In-Reply-To: <0430A0F6-6777-4EC3-B0D6-BBAF3AAF900C@seal-one.com>
On Sun, Jul 28, 2019 at 01:25:32PM +0200, Maik Stohn wrote:
> Hello Greg,
>
> Sorry to trouble you again.
>
> I was waiting and observing how the FIX is applied and it looks like
> it will not be applied to 5.2.x (5.2.3 and 5.2.4 came out without this
> patch).
> Personally I think it is a big mistake not to merge the fix but this
> is your decision.
>
> I have to tell my users now to AVOID KERNEL 5.2 at all since it is
> buggy and most likely will never be fixed.
>
> But since it is also not part of any 5.3 (right now) I'm a bit afraid
> I also need to put a warning to avoid 5.3 as well.
>
> Would be nice to get an official statement like: "Linux kernel will
> not merge the USB fix to 5.2, maybe 5.3 will have it, but better wait
> for 5.4", so I can quote this to my users.
How about an official statement like "wait a week please" :)
Or, "if you have problems, please apply this patch."
We _just_ found the fix, it _just_ went into my tree a few days ago. A
patch can not be in a stable kernel until it shows up in Linus's kernel,
in a release (like a -rc).
So, ideally this patch gets into 5.3-rc2. Then I can add it to the
queue of patches to go into the 5.2.y release, which should happen
sometime next week or the week after at worst case.
Please read Documentation/process/ for how all of this works if you are
curious, we have tests to pass, releases to make it through, and reviews
to happen here. Give us a chance please, there is no major rush. And
if there is a rush, you have the fix to apply to your kernel to solve
the problem! You are not dependant on any of us here anymore, anyone
can patch their machines if they run into this issue and can not wait a
week or so.
Also, odds are that most people are even running the 5.2.y kernel yet is
pretty low... :)
So, again, patience. Your fix is just one of hundreds winding its way
through the ether to get out to users. You are not alone, and at the
same time, not special. It will happen, just relax.
greg k-h
prev parent reply other threads:[~2019-07-28 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:27 patch "xhci: Fix crash if scatter gather is used with Immediate Data" added to usb-linus gregkh
2019-07-28 11:25 ` Maik Stohn
2019-07-28 11:41 ` 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=20190728114142.GA12033@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=maik.stohn@seal-one.com \
--cc=mathias.nyman@linux.intel.com \
--cc=nsaenzjulienne@suse.de \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).