lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YAk6+ZgNPQy3snB1@kroah.com>
Date:   Thu, 21 Jan 2021 09:27:37 +0100
From:   "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:     吳昊澄 Ricky <ricky_wu@...ltek.com>
Cc:     "arnd@...db.de" <arnd@...db.de>,
        "ricky_wu@...ltek.corp-partner.google.com" 
        <ricky_wu@...ltek.corp-partner.google.com>,
        "sashal@...nel.org" <sashal@...nel.org>,
        "levinale@...gle.com" <levinale@...gle.com>,
        "keitasuzuki.park@...ab.ics.keio.ac.jp" 
        <keitasuzuki.park@...ab.ics.keio.ac.jp>,
        "kdlnx@...h.eu" <kdlnx@...h.eu>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rtsx: pci: fix device aspm state bug

On Thu, Jan 21, 2021 at 08:15:46AM +0000, 吳昊澄 Ricky wrote:
> > -----Original Message-----
> > From: gregkh@...uxfoundation.org <gregkh@...uxfoundation.org>
> > Sent: Thursday, January 21, 2021 4:07 PM
> > To: 吳昊澄 Ricky <ricky_wu@...ltek.com>
> > Cc: arnd@...db.de; ricky_wu@...ltek.corp-partner.google.com;
> > sashal@...nel.org; levinale@...gle.com; keitasuzuki.park@...ab.ics.keio.ac.jp;
> > kdlnx@...h.eu; linux-kernel@...r.kernel.org
> > Subject: Re: [PATCH] rtsx: pci: fix device aspm state bug
> > 
> > On Thu, Jan 21, 2021 at 07:33:03AM +0000, 吳昊澄 Ricky wrote:
> > > Hi Greg kh,
> > >
> > > This patch to fix misc: rtsx bug for kernel 5.4
> > 
> > I do not understand what this means, sorry.  Can you please explain it?
> > 
> On the newest upstream we don’t set config space for en/disable aspm, 
> so it will not happen this issue
> but on kernel 5.4 longterm version we need to fix it

Please read
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to submit patches to the stable tree properly.

And if this is not an issue in Linus's tree, why not just backport the
commits that fixed this issue?  That's the best way to do this.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ