From: Greg KH <gregkh@linuxfoundation.org>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Crash/hung task in usb-storage thread
Date: Thu, 23 May 2019 20:05:34 +0200 [thread overview]
Message-ID: <20190523180534.GA19685@kroah.com> (raw)
In-Reply-To: <5c127181fd1e46dfa6efe8e6ea85b750@SVR-IES-MBX-03.mgc.mentorg.com>
On Thu, May 23, 2019 at 01:16:12PM +0000, Schmid, Carsten wrote:
> > > >
> > > > 4.14.102 is still old.
> > > I agree
> > >
> > > > > Porting a 5.1 will take a lot of effort.
> > > >
> > > > Then that implies you have an SoC with a few million lines of code added
> > > > to the kernel, right? Nothing we can do here about that mess, you need
> > > > to go ask for support from the vendor that is forcing you to use that
> > > > kernel, sorry :(
> > > >
> > >
> > > Well its at least an x86-64 based SoC.
> >
> > An x86 SoC should work on 5.1, what is missing there to keep it from
> > functioning? Why hasn't it already been updated to 4.19.y?
> >
> > thanks,
> >
> > greg k-h
> - Long term stabilisation of product.
> - Concerns a product update - already in production
So, you have a huge list of known bugs/vulnerabilities in that device
now, yet they refuse to update. Not good :(
Best of luck,
greg k-h
next prev parent reply other threads:[~2019-05-23 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:57 Crash/hung task in usb-storage thread Schmid, Carsten
2019-05-23 12:04 ` Greg KH
2019-05-23 12:16 ` AW: " Schmid, Carsten
2019-05-23 12:26 ` Greg KH
2019-05-23 12:30 ` AW: " Schmid, Carsten
2019-05-23 12:35 ` Greg KH
2019-05-23 13:16 ` AW: " Schmid, Carsten
2019-05-23 18:05 ` Greg KH [this message]
2019-05-23 16:50 ` Alan Stern
2019-05-24 13:33 ` AW: " Schmid, Carsten
2019-05-24 14:59 ` Greg KH
2019-05-24 15:24 ` AW: " Alan Stern
2019-05-24 15:47 ` AW: " Schmid, Carsten
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=20190523180534.GA19685@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Carsten_Schmid@mentor.com \
--cc=linux-usb@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).