linux-kernel - Re: [01/38] PCI: Set PCI-E Max Payload Size on fabric

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: <20111011200335.GJ10838@kvack.org>
Date:	Tue, 11 Oct 2011 16:03:35 -0400
From:	Benjamin LaHaise <bcrl@...ck.org>
To:	Greg KH <greg@...ah.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>, Greg KH <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	stable-review@...nel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	Jon Mason <mason@...i.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [01/38] PCI: Set PCI-E Max Payload Size on fabric

On Tue, Oct 11, 2011 at 01:56:11PM -0600, Greg KH wrote:
> > On Tue, Oct 11, 2011 at 1:24 PM, Greg KH <greg@...ah.com> wrote:
...
> > I'd like to know more about this regression.
> 
> It shows up as an oops that prevents the machine from booting.

If it's a regression, the patch should be limited to fixing the bug.  As 
it stands, this patch series introduces new functionality, and because it 
goes through a known broken state with the first patch, it may cause 
failures for people if they land in the middle during a bisect.  This 
doesn't seem like the right approach for -stable.

		-ben
--
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/