Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756539Ab0HNAoR (ORCPT ); Fri, 13 Aug 2010 20:44:17 -0400 Received: from cantor.suse.de ([195.135.220.2]:52711 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752406Ab0HNAoQ (ORCPT ); Fri, 13 Aug 2010 20:44:16 -0400 Date: Fri, 13 Aug 2010 17:11:58 -0700 From: Greg KH To: Grant Coady Cc: linux-kernel@vger.kernel.org, stable@kernel.org, stable-review@kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk Subject: Re: [0/3] 2.6.27.52 stable review Message-ID: <20100814001158.GA2849@suse.de> References: <20100813214704.GA18960@kroah.com> <20100813230712.GA1703@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2397 Lines: 63 On Sat, Aug 14, 2010 at 09:47:08AM +1000, Grant Coady wrote: > Hi Greg, > > I scraped the patches out of the messages and edited Makefile :) > > On Fri, 13 Aug 2010 16:07:12 -0700, you wrote: > > >On Sat, Aug 14, 2010 at 08:36:34AM +1000, Grant Coady wrote: > >> On Fri, 13 Aug 2010 14:47:04 -0700, you wrote: > >> > >> >NOTE! > >> > > >> >If I could get some people to please test this -rc release? It contains > >> >a few core changes that I couldn't validate myself as I don't seem to > >> >have a machine that will even boot the .27 kernel anymore after my move. > > Machine is running, but there's a lot of these in the dmesg: > > WARNING: at include/linux/security.h:1826 acct_stack_growth+0xe7/0xf0() > Modules linked in: > Pid: 320, comm: khelper Not tainted 2.6.27.52-rc1a #57 > [] warn_on_slowpath+0x5f/0x90 > [] __alloc_pages_internal+0x93/0x420 > [] buffered_rmqueue+0x11d/0x210 > [] allocate_slab+0x4a/0xd0 > [] setup_object+0x29/0x30 > [] new_slab+0xb4/0x130 > [] __slab_alloc+0xac/0x120 > [] acct_stack_growth+0xe7/0xf0 > [] expand_stack+0x7a/0x90 > [] do_anonymous_page+0x121/0x130 > [] handle_mm_fault+0x1b8/0x1e0 > [] get_user_pages+0xe4/0x270 > [] get_arg_page+0x49/0xc0 > [] copy_strings+0xdb/0x180 > [] copy_strings_kernel+0x29/0x40 > [] do_execve+0xde/0x1d0 > [] sys_execve+0x2f/0x60 > [] syscall_call+0x7/0xb > [] ioapic_register_intr+0x10b/0x110 > [] kernel_execve+0x1c/0x30 > [] ____call_usermodehelper+0x5c/0xc0 > [] ____call_usermodehelper+0x0/0xc0 > [] kernel_thread_helper+0x7/0x1c > ======================= > ---[ end trace 62e879f3daf4be6a ]--- I'm guessing that 2.6.27.51 didn't cause those warnings as well? That's a warning that current->mm is null. I don't know enough about the mm subsystem to say if this is normal or not, and I don't at first glance, see how this patch could have caused this to happen. Anyone else have an idea? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/