From: Greg KH <gregkh@suse.de>
To: Grant Coady <gcoady.lk@gmail.com>
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
Date: Fri, 13 Aug 2010 17:11:58 -0700 [thread overview]
Message-ID: <20100814001158.GA2849@suse.de> (raw)
In-Reply-To: <t5mb661vmb2a33gev3tqki89410a0795kc@4ax.com>
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
> [<c011b54f>] warn_on_slowpath+0x5f/0x90
> [<c0145a53>] __alloc_pages_internal+0x93/0x420
> [<c01456bd>] buffered_rmqueue+0x11d/0x210
> [<c015e09a>] allocate_slab+0x4a/0xd0
> [<c015e149>] setup_object+0x29/0x30
> [<c015e204>] new_slab+0xb4/0x130
> [<c015e6ec>] __slab_alloc+0xac/0x120
> [<c01529e7>] acct_stack_growth+0xe7/0xf0
> [<c0152afa>] expand_stack+0x7a/0x90
> [<c014fc61>] do_anonymous_page+0x121/0x130
> [<c0150268>] handle_mm_fault+0x1b8/0x1e0
> [<c014e724>] get_user_pages+0xe4/0x270
> [<c0166ac9>] get_arg_page+0x49/0xc0
> [<c0166e5b>] copy_strings+0xdb/0x180
> [<c0166f29>] copy_strings_kernel+0x29/0x40
> [<c0167dae>] do_execve+0xde/0x1d0
> [<c0101f1f>] sys_execve+0x2f/0x60
> [<c0103036>] syscall_call+0x7/0xb
> [<c011007b>] ioapic_register_intr+0x10b/0x110
> [<c0106bfc>] kernel_execve+0x1c/0x30
> [<c0128efc>] ____call_usermodehelper+0x5c/0xc0
> [<c0128ea0>] ____call_usermodehelper+0x0/0xc0
> [<c0103b1b>] 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
next prev parent reply other threads:[~2010-08-14 0:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 21:47 [0/3] 2.6.27.52 stable review Greg KH
2010-08-13 21:42 ` [1/3] mm: keep a guard page below a grow-down stack segment Greg KH
2010-08-13 21:42 ` [2/3] mm: fix missing page table unmap for stack guard page failure case Greg KH
2010-08-13 21:42 ` [3/3] x86: dont send SIGBUS for kernel page faults Greg KH
2010-08-13 22:36 ` [0/3] 2.6.27.52 stable review Grant Coady
2010-08-13 23:07 ` Greg KH
2010-08-13 23:47 ` Grant Coady
2010-08-14 0:11 ` Greg KH [this message]
2010-08-14 0:51 ` Linus Torvalds
2010-08-14 2:53 ` Greg KH
2010-08-14 5:43 ` [Stable-review] " Willy Tarreau
2010-08-14 18:47 ` [stable] " Greg KH
2010-08-14 21:46 ` Greg KH
2010-08-14 7:24 ` Grant Coady
2010-08-14 19:12 ` [stable] " Greg KH
2010-08-15 1:28 ` Grant Coady
2010-08-14 0:12 ` Linus Torvalds
2010-08-14 0:47 ` Greg KH
2010-08-14 7:34 ` Grant Coady
2010-08-14 7:43 ` [Stable-review] " Willy Tarreau
2010-08-14 8:52 ` Grant Coady
2010-08-13 22:45 ` Willy Tarreau
2010-08-14 11:11 ` Gabor Z. Papp
2010-08-14 15:00 ` 2.6.27.52 " Grant Coady
2010-08-14 21:01 ` Greg KH
2010-08-14 22:11 ` Thomas Backlund
2010-08-23 22:27 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100814001158.GA2849@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).