linux-kernel - Re: [PATCH] Ignore pre-1.1 ASPM quirking when ASPM is disabled

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: <20120307202553.50b6c91c@jbarnes-x220>
Date:	Wed, 7 Mar 2012 20:25:53 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Greg KH <greg@...ah.com>
Cc:	Matthew Garrett <mjg@...hat.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] Ignore pre-1.1 ASPM quirking when ASPM is disabled

On Tue, 6 Mar 2012 21:48:59 -0800
Greg KH <greg@...ah.com> wrote:

> On Tue, Mar 06, 2012 at 01:41:49PM -0500, Matthew Garrett wrote:
> > Right now we won't touch ASPM state if ASPM is disabled, except in
> > the case where we find a device that appears to be too old to
> > reliably support ASPM. Right now we'll clear it in that case, which
> > is almost certainly the wrong thing to do. The easiest way around
> > this is just to disable the blacklisting when ASPM is disabled.
> > 
> > Signed-off-by: Matthew Garrett <mjg@...hat.com>
> > Cc: stable@...nel.org
> 
> That's <stable@...r.kernel.org> if we want to get it right :)
> 
> Anyway, Jesse, this needs to get into 3.3-final to prevent
> regressions...

Any bz links to add to the changelog?  I'll fix up the stable cc when I
commit...

Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/