linux-kernel - Re: [PATCH] pci device ensure sysdata initialised v2

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] [day] [month] [year] [list]

Message-ID: <4551BDF1.7050302@pobox.com>
Date:	Wed, 08 Nov 2006 06:22:25 -0500
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Andy Whitcroft <apw@...dowen.org>, Andrew Morton <akpm@...l.org>
CC:	Greg KH <gregkh@...e.de>, Martin Bligh <mbligh@...igh.org>,
	Badari Pulavarty <pbadari@...ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	sukadev@...ibm.com
Subject: Re: [PATCH] pci device ensure sysdata initialised v2

Andy Whitcroft wrote:
> Ok, I've gone over the patches and retested them.  Other than having
> to extend them to cover x86_64 they still seem to work as planned.  I
> have updated the commentry to better explain the problem and the
> fix as encapsulated here.
> 
> When this was proposed last time there was push back to get the
> nodes right.  Whist this is clearly a good thing, I think we need
> this as a first step if the underlying patches are going to stay
> in.

We definitely need something like this.  Having some sysdata static and 
some sysdata dynamic makes me nervous, and so I want to review the code 
paths in depth before applying this.  My gut feeling is that there is a 
bug remaining in this area, that this patch might exacerbate.

	Jeff


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