[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D2F1430.50906@redhat.com>
Date: Thu, 13 Jan 2011 16:03:12 +0100
From: Milan Broz <mbroz@...hat.com>
To: Kay Sievers <kay.sievers@...y.org>
CC: Tejun Heo <tj@...nel.org>, Karel Zak <kzak@...hat.com>,
device-mapper development <dm-devel@...hat.com>,
"Jun'ichi Nomura" <j-nomura@...jp.nec.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/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.)
> And yes, symlinks *look* nice and simple for the outside, but they are
> not, and have all sorts of problems like non-atomic updates, make it
> impossible to ever rename a device (as long as they copy the device
> name), and and and .... we should not add more of this.
Yes, I agree, if there is better way, let's switch to that.
Milan
--
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