From: Neil Brown <neilb@cse.unsw.edu.au>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.9-rc1: kernel BUG at mm/slab.c:1828 (sunrpc)
Date: Fri, 27 Aug 2004 11:50:28 +1000 [thread overview]
Message-ID: <16686.37732.565804.886087@cse.unsw.edu.au> (raw)
In-Reply-To: message from Alex Riesen on Thursday August 26
On Thursday August 26, fork0@users.sourceforge.net wrote:
> I get this running X and some gnome applications for a while (~10sec).
> After the bug, keyboard stays locked, mouse (usb) works, and I can
> finish the session. It brings me to a blank console:
>
> kernel: <6>SysRq : Emergency Sync
> kernel: Emergency Sync complete
> gconfd (raa-3333): Received signal 1, shutting down cleanly
> gconfd (raa-3333): Exiting
> init: open(/dev/console): Input/output error
>
> Ctrl-Alt-Del worked, though:
>
> init: Switching to runlevel: 6
>
> It is reproducable with latest bk as of Aug 26 20:00 CET.
> The system is ht/smt P4 with preempt, Gentoo (no hotplug and udev).
>
> There is a suspect:
> struct auth_domain *auth_unix_lookup(struct in_addr addr)
> ...
> key.m_class = "nfsd";
> key.m_addr = addr;
>
> And ip_map_put contains a "kfree(im->m_class)".
> I wasn't able to reproduce the bug after removing the kfree.
> The strdups to m_class will leak now, I suppose.
Yep, thanks.
Andrew has received a patch so it should be fixed in the next
release. For now, removing the "kfree" is safe enough.
NeilBrown
prev parent reply other threads:[~2004-08-27 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 19:00 Alex Riesen
2004-08-27 1:50 ` Neil Brown [this message]
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=16686.37732.565804.886087@cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=akpm@osdl.org \
--cc=fork0@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®