[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D2FFD5D.9070709@ce.jp.nec.com>
Date: Fri, 14 Jan 2011 16:38:05 +0900
From: "Jun'ichi Nomura" <j-nomura@...jp.nec.com>
To: Milan Broz <mbroz@...hat.com>, Kay Sievers <kay.sievers@...y.org>,
Tejun Heo <tj@...nel.org>
CC: Karel Zak <kzak@...hat.com>,
device-mapper development <dm-devel@...hat.com>,
Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org
Subject: Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
On 01/14/11 00:03, Milan Broz wrote:
> On 01/13/2011 03:43 PM, Kay Sievers wrote:
>
>>> On Thu, Jan 13, 2011 at 3:25 PM, Milan Broz <mbroz@...hat.com> wrote:
>>>> Maybe, but this was not invented in DM/MD camp:-)
>>>> Probably Kay or Greg can answer why it was done this way?
>>
>> It's not from Greg or Kay. It just appeared some day in the context of dm. :)
>
> ah, then sorry, I am just confused:-)
> But DM does not need it for operation at all so it must had some other reason.
> (We have dmsetup ls --tree using dm-ioctls for years.)
Sorry. It's from me 5 years ago. :)
See this for backgrounds:
[PATCH 0/3] sysfs representation of stacked devices (dm/md)
http://lwn.net/Articles/172689/
And I don't adhere to my implementation if there's better one.
Thanks,
--
Jun'ichi Nomura, NEC Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists