On Wed, 2011-04-27 at 22:36 +0200, Geert Uytterhoeven wrote:
On Wed, Apr 27, 2011 at 22:18, James Bottomley
<James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> 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-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
