[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: "Jun'ichi Nomura" <j-nomura ce jp nec com>
- To: Milan Broz <mbroz redhat com>, Kay Sievers <kay sievers vrfy org>, Tejun Heo <tj kernel org>
- Cc: Valdis Kletnieks vt edu, linux-kernel vger kernel org, linux-raid vger kernel org, device-mapper development <dm-devel redhat com>, Karel Zak <kzak redhat com>, Alexander Viro <viro zeniv linux org uk>, linux-fsdevel vger kernel org
- Subject: Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- Date: Fri, 14 Jan 2011 16:38:05 +0900
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 redhat 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
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]