From: Milan Broz <mbroz@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-raid@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
Date: Thu, 13 Jan 2011 01:23:45 +0100 [thread overview]
Message-ID: <4D2E4611.90002@redhat.com> (raw)
In-Reply-To: <16069.1294853673@localhost>
On 01/12/2011 06:34 PM, Valdis.Kletnieks@vt.edu wrote:
> Seen in a boot of yesterday's linux-next. The 'W' flag was due to the
> already-reported 'WARNING: at kernel/workqueue.c:1202 worker_enter_idle'.
> Not sure if it's a block_dev or dm/LVM issue, so I'm cc:'ing both groups. I wonder
> if the fact I still have 'CONFIG_DEVTMPFS=n' is involved (it's apparently ticking off
> dracut before and after the warning).
>
> [ 16.840333] dracut: Found volume group "vg_blackice" using metadata type lvm2
> [ 16.892282] dracut: The link /dev/vg_blackice/opt should had been created by udev but it was not found. Falling back to direct link creation.
> [ 16.912627] ------------[ cut here ]------------
> [ 16.912635] WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
That seems to be
WARN_ON_ONCE(!bdev->bd_holder || bdev->bd_holder_disk);
added in patch
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=e09b457bdb7e8d23fc54dcef0930ac697d8de895
"block: simplify holder symlink handling"
dm linear just claims device in table constructor, I don't think it is bug in DM code.
> [ 16.912638] Hardware name: Latitude E6500
> [ 16.912640] Modules linked in:
> [ 16.912644] Pid: 1920, comm: lvm Tainted: G W 2.6.37-next-20110111 #1
> [ 16.912647] Call Trace:
> [ 16.912653] [<ffffffff8103a989>] ? warn_slowpath_common+0x80/0x98
> [ 16.912657] [<ffffffff8103a9b6>] ? warn_slowpath_null+0x15/0x17
> [ 16.912660] [<ffffffff8111fb03>] ? bd_link_disk_holder+0x92/0x1ac
> [ 16.912665] [<ffffffff8139b875>] ? open_dev+0x76/0x9e
> [ 16.912668] [<ffffffff8139bc9d>] ? dm_get_device+0x147/0x1dc
> [ 16.912672] [<ffffffff8139d088>] ? linear_ctr+0x98/0xd4
> [ 16.912676] [<ffffffff8139c289>] ? dm_table_add_target+0x149/0x1d4
> [ 16.912679] [<ffffffff8139e57c>] ? table_load+0xf0/0x27b
> [ 16.912683] [<ffffffff8139e48c>] ? table_load+0x0/0x27b
> [ 16.912686] [<ffffffff8139f326>] ? ctl_ioctl+0x1c6/0x21e
> [ 16.912690] [<ffffffff8139f38c>] ? dm_ctl_ioctl+0xe/0x12
> [ 16.912695] [<ffffffff8110258e>] ? do_vfs_ioctl+0x4c4/0x505
> [ 16.912699] [<ffffffff81102626>] ? sys_ioctl+0x57/0x95
> [ 16.912703] [<ffffffff8100253b>] ? system_call_fastpath+0x16/0x1b
> [ 16.912706] ---[ end trace 4eaa2a86a8e2da24 ]---
> [ 16.925289] dracut: The link /dev/vg_blackice/src should had been created by udev but it was not found. Falling back to direct link creation.
>
Milan
next prev parent reply other threads:[~2011-01-13 0:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 17:34 linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac() Valdis.Kletnieks
2011-01-13 0:23 ` Milan Broz [this message]
2011-01-13 2:19 ` Jun'ichi Nomura
2011-01-13 11:06 ` Tejun Heo
2011-01-13 11:26 ` [dm-devel] " Milan Broz
2011-01-13 12:27 ` Karel Zak
2011-01-13 13:12 ` Tejun Heo
2011-01-13 13:26 ` Karel Zak
2011-01-13 13:37 ` Tejun Heo
2011-01-13 13:52 ` Tejun Heo
2011-01-13 13:58 ` Milan Broz
2011-01-13 14:11 ` Tejun Heo
2011-01-13 14:25 ` Milan Broz
2011-01-13 14:30 ` Tejun Heo
2011-01-13 14:43 ` Kay Sievers
2011-01-13 15:03 ` Milan Broz
2011-01-14 7:38 ` Jun'ichi Nomura
2011-01-13 15:59 ` Karel Zak
2011-01-13 16:10 ` [dm-devel] " Kay Sievers
2011-01-14 15:07 ` Karel Zak
2011-01-14 15:23 ` Kay Sievers
2011-01-13 14:45 ` Theodore Tso
2011-01-13 20:18 ` NeilBrown
2011-01-13 20:41 ` Ted Ts'o
2011-01-14 16:20 ` Tejun Heo
2011-01-14 17:59 ` Ted Ts'o
2011-01-14 18:23 ` Tejun Heo
2011-01-13 14:49 ` Milan Broz
2011-01-14 16:35 ` Tejun Heo
2011-01-13 17:21 ` [PATCH] block: restore multiple bd_link_disk_holder() support Tejun Heo
2011-01-13 18:42 ` Milan Broz
2011-01-14 7:31 ` Jun'ichi Nomura
2011-01-14 16:10 ` [PATCH UPDATED] " Tejun Heo
2011-01-14 21:09 ` Milan Broz
2011-01-17 0:18 ` Jun'ichi Nomura
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=4D2E4611.90002@redhat.com \
--to=mbroz@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dm-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).