From: William Lee Irwin III <wli@holomorphy.com>
To: John Zielinski <grim@undead.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Rootfs mounted from user space - problem with umount
Date: Fri, 28 Nov 2003 22:21:36 -0800 [thread overview]
Message-ID: <20031129062136.GH8039@holomorphy.com> (raw)
In-Reply-To: <3FC8394A.7010702@undead.cc>
William Lee Irwin III wrote:
>> Could you do a sysrq t and send in a backtrace?
On Sat, Nov 29, 2003 at 01:14:34AM -0500, John Zielinski wrote:
> Here's the trace for umount:
> umount D DF9D98C0 3920 380 245 (NOTLB)
[...]
> Call Trace:
> [<c015be66>] path_release+0x16/0x40
> [<c0169f59>] umount_tree+0xa9/0x100
> [<c01e169c>] rwsem_down_write_failed+0x8c/0x140
> [<c0155e0b>] .text.lock.super+0x12/0x187
> [<c016a22c>] sys_umount+0x3c/0x90
> [<c016a299>] sys_oldumount+0x19/0x20
> [<c010938f>] syscall_call+0x7/0xb
Looks like either namespace->sem or sb->s_umount; you should be able
to put some instrumentation code in down_write() and/or down_read() to
see who acquired it first by checking to see if the sem acquired belongs
to rootfs' sb or some namespace (doubtful you'll create many of them).
-- wli
next prev parent reply other threads:[~2003-11-29 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 5:24 Rootfs mounted from user space - problem with umount John Zielinski
2003-11-29 5:31 ` William Lee Irwin III
2003-11-29 6:14 ` John Zielinski
2003-11-29 6:21 ` William Lee Irwin III [this message]
2003-11-29 9:40 ` John Zielinski
2003-11-29 9:44 ` William Lee Irwin III
2003-11-29 20:02 ` John Zielinski
2003-11-29 20:20 ` John Zielinski
2003-11-29 20:25 ` William Lee Irwin III
2003-11-29 21:05 ` John Zielinski
2003-11-29 21:17 ` Sean Neakums
2003-11-29 21:42 ` John Zielinski
2003-11-30 0:38 ` [OT] " Sean Neakums
2003-11-29 5:38 ` Valdis.Kletnieks
2003-11-29 6:25 ` John Zielinski
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=20031129062136.GH8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=grim@undead.cc \
--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;
as well as URLs for NNTP newsgroup(s).