From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: fs/namespace.c:638 mntput_no_expire warn_on in 2.6.30.2
Date: Tue, 18 Aug 2009 11:57:18 +0200 [thread overview]
Message-ID: <20090818095718.GA21869@basil.fritz.box> (raw)
To whom it concerns or for kerneloops.org. I didn't look too closely,
but it seems to have leaked a reference on a device mapper mount point
so I couldn't umount anymore. This was with a kpartx loop back mount
of a file.
Kernel 2.6.30.2 (+ some totally unrelated patches)
-Andi
------------[ cut here ]------------
WARNING: at /home/lsrc/linux-2.6.30/fs/namespace.c:638 mntput_no_expire+0xcf/0x11b()
Hardware name:
Modules linked in: ...
Pid: 7180, comm: umount Tainted: G D 2.6.30.2-BASIL #7
Call Trace:
[<ffffffff8020e284>] dump_trace+0x6e/0x292
[<ffffffff805bccb3>] dump_stack+0x69/0x6f
[<ffffffff802376db>] warn_slowpath_common+0x77/0xa2
[<ffffffff802b78a1>] mntput_no_expire+0xcf/0x11b
[<ffffffff802b7e27>] sys_umount+0x2b7/0x2e2
[<ffffffff8020ba6b>] system_call_fastpath+0x16/0x1b
[<00007fa4d9d1c1c7>] 0x7fa4d9d1c1c7
---[ end trace 12f3f532ce924b4b ]---
--
ak@linux.intel.com -- Speaking for myself only.
reply other threads:[~2009-08-18 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090818095718.GA21869@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).