| 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
| ||
|
Message-ID: <20080721152539.3d8684f9@halley.suse.de> Date: Mon, 21 Jul 2008 15:25:39 +0200 From: Bernhard Walle <bwalle@...e.de> To: Vivek Goyal <vgoyal@...hat.com> Cc: Dave Hansen <dave@...ux.vnet.ibm.com>, Stephen Rothwell <sfr@...b.auug.org.au>, Vegard Nossum <vegard.nossum@...il.com>, Pekka Enberg <penberg@...helsinki.fi>, Greg KH <gregkh@...e.de>, kexec <kexec@...ts.infradead.org>, LKML <linux-kernel@...r.kernel.org>, Mariusz Kozlowski <m.kozlowski@...land.pl>, linux-next@...r.kernel.org, Ingo Molnar <mingo@...e.hu>, kernel-testers@...r.kernel.org Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller * Vivek Goyal [2008-07-21 09:17]: > > Is /proc/iomem updated upon memory hotplug event. Yes. I just checked that (yesterday). I think it would make sense to extend /sys/firmware/memmap on hot-plugging. Just because on reboot, the firmware will see that memory, too, and report it. However, we need a way to discriminate the originally firmware-provided memory map with later added memory. I'm not sure how that can be done, I have to think about it. Bernhard -- Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development -- 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/
Powered by blists - more mailing lists