From: Andrew Morton <akpm@linux-foundation.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>,
Greg KH <greg@kroah.com>
Subject: Re: WARNING: at lib/kref.c:33 kref_get() (-mm 2007-11-06-02-32++)
Date: Sat, 10 Nov 2007 14:54:52 -0800 [thread overview]
Message-ID: <20071110145452.f6cf6326.akpm@linux-foundation.org> (raw)
In-Reply-To: <200711100212.lAA2Cll0015004@agora.fsl.cs.sunysb.edu>
On Fri, 9 Nov 2007 21:12:47 -0500 Erez Zadok <ezk@cs.sunysb.edu> wrote:
> Setup: FC6 system with MM snapshot broken-out-2007-11-06-02-32
That's a bit old.
> and these two
> patches added:
>
> r-o-bind-mounts-track-number-of-mount-writer-fix-buggy-loop.patch
> r-o-bind-mounts-track-number-of-mount-writer-fix-buggy-loop-checkpatch-fixes.patch
>
> Booting the machine, waiting a few minutes (not logging in or doing anything
> else). I get:
>
> WARNING: at lib/kref.c:33 kref_get()
> [<c020282a>] show_trace_log_lvl+0x12/0x25
> [<c0203024>] show_trace+0xd/0x10
> [<c0203120>] dump_stack+0x15/0x17
> [<c02c7f85>] kref_get+0x26/0x30
> [<c02c731b>] kobject_get+0x12/0x17
> [<c02c7770>] kobject_add+0x97/0x162
> [<c02164e5>] uids_user_create+0x41/0x5d
> [<c0216850>] alloc_uid+0xc9/0x171
> [<c0219b50>] set_user+0x1f/0x93
> [<c021b445>] sys_setuid+0x4b/0xcb
> [<c02021fe>] sysenter_past_esp+0x5f/0x91
> =======================
>
> There's no other indication where the setuid(2) came from, perhaps cron?
>
I have a feeling that this was reported before and that Dave and/or Greg
looked into it. Were those two patches which Dave sent yesterday applied?
It might be worth checking my current tree:
http://userweb.kernel.org/~akpm/mmotm/
next prev parent reply other threads:[~2007-11-10 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 2:12 WARNING: at lib/kref.c:33 kref_get() (-mm 2007-11-06-02-32++) Erez Zadok
2007-11-10 22:54 ` Andrew Morton [this message]
2007-11-11 0:27 ` Erez Zadok
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=20071110145452.f6cf6326.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.