| 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: <1303937713.2583.28.camel@mulgrave.site> Date: Wed, 27 Apr 2011 15:55:13 -0500 From: James Bottomley <James.Bottomley@...senPartnership.com> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Parisc List <linux-parisc@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, Linux/m68k <linux-m68k@...r.kernel.org> Subject: Re: [GIT PULL] parisc fixes for 2.6.39-rc5 On Wed, 2011-04-27 at 22:36 +0200, Geert Uytterhoeven wrote: > On Wed, Apr 27, 2011 at 22:18, James Bottomley > <James.Bottomley@...senpartnership.com> wrote: > > These two fixes contain the agreed fix for our slub panic (agreed with > > the mm folks that we'll define SLUB broken in the !NUMA && DISCONTIGMEM > > case, which should fix m86k as well) and another buglet that turned up > > examining the parisc discontigmem code. > > Do we still need to mark SLUB broken? > On m68k, the issue seems to have been fixed by setting the N_NORMAL_MEMORY flag > (pull request scheduled after one more linux-next build cycle). > > Or do you plan to unmark it broken once every affected arch sets the > N_NORMAL_MEMORY flag? Yes ... simply doing N_NORMAL_MEMORY doesn't fix parisc to not oops. James -- 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