From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760019Ab1D0UzS (ORCPT ); Wed, 27 Apr 2011 16:55:18 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:47857 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751227Ab1D0UzQ (ORCPT ); Wed, 27 Apr 2011 16:55:16 -0400 Subject: Re: [GIT PULL] parisc fixes for 2.6.39-rc5 From: James Bottomley To: Geert Uytterhoeven Cc: Andrew Morton , Linus Torvalds , Parisc List , linux-kernel , Linux/m68k In-Reply-To: References: <1303935518.2583.27.camel@mulgrave.site> Content-Type: text/plain; charset="UTF-8" Date: Wed, 27 Apr 2011 15:55:13 -0500 Message-ID: <1303937713.2583.28.camel@mulgrave.site> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2011-04-27 at 22:36 +0200, Geert Uytterhoeven wrote: > On Wed, Apr 27, 2011 at 22:18, James Bottomley > 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