[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: Milan Broz <mbroz redhat com>
- To: Tejun Heo <tj kernel org>
- Cc: Valdis Kletnieks vt edu, linux-kernel vger kernel org, linux-raid vger kernel org, linux-fsdevel vger kernel org, device-mapper development <dm-devel redhat com>, Karel Zak <kzak redhat com>, Alexander Viro <viro zeniv linux org uk>, Jun'ichi Nomura <j-nomura ce jp nec com>
- Subject: Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- Date: Thu, 13 Jan 2011 14:58:23 +0100
On 01/13/2011 02:37 PM, Tejun Heo wrote:
> So, just don't do it. Sysfs is for device hierarchy. Don't try to
> shove pretty looking things there (unless it's something widely agreed
> on and necessary, of course).
Hi,
I think that it is exactly what holders/slaves do - displaying device
hierarchy. So application can check which underlying device are related
and ask them for more info if needed (=> with system specific call,
it can be simple sysfs attribute, ioctl, whatever).
So the only request here is to keep these symlinks correct, nothing more.
Or am I missing anything?
Milan
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]