linux-kernel - Re: [EDAC ABI v13 09/25] edac: rewrite the sysfs code to use struct device

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: <20120509132455.GE22737@aftab.osrc.amd.com>
Date:	Wed, 9 May 2012 15:24:55 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Doug Thompson <norsk5@...oo.com>,
	Greg K H <gregkh@...uxfoundation.org>
Subject: Re: [EDAC ABI v13 09/25] edac: rewrite the sysfs code to use struct
 device

On Wed, May 09, 2012 at 10:10:33AM -0300, Mauro Carvalho Chehab wrote:
> This is fixed by this patch, already acked-by Greg:
> 	[EDAC ABI v13 17/25] edac: Create a per-Memory Controller bus
> 	http://git.infradead.org/users/mchehab/edac.git/commit/a2c90149c2e87e51908003b1ba504f92d749f74b
> 
> Basically, on devices with multiple controllers, there a separate per-memory controller bus
> is needed due to sysfs nodes under /sys/bus.
> 
> I opted to keep it on a separate patch, in order to preserve the history, and properly
> document why this is needed.

We don't apply patches causing oopses like that because this breaks
bisection.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/