From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.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
Message-ID: <20090818095718.GA21869@basil.fritz.box>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1758080AbZHRJ5X@vger.kernel.org>
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org


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.