From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: [PATCH 007 of 7] md: Get name for block device in sysfs Date: Mon, 17 Dec 2007 09:43:25 +1100 Message-ID: <18277.43533.991986.323212@notabene.brown> References: <20071214171950.1308.patches@notabene> <1071214062647.1928@suse.de> <3ae72650712150858v14681823td2b0410eb67b1d04@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: message from Kay Sievers on Saturday December 15 Sender: linux-raid-owner@vger.kernel.org To: Kay Sievers Cc: Andrew Morton , linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, Jens Axboe , Greg KH List-Id: linux-raid.ids On Saturday December 15, kay.sievers@vrfy.org wrote: > On Dec 14, 2007 7:26 AM, NeilBrown wrote: > > > > Given an fd on a block device, returns a string like > > > > /block/sda/sda1 > > > > which can be used to find related information in /sys. .... > > As pointed out to when you came up with the idea, we can't do this. A devpath > is a path to the device and will not necessarily start with "/block" for block > devices. It may start with "/devices" and can be much longer than > BDEVNAME_SIZE*2 + 10. When you say "will not necessarily" can I take that to mean that it currently does, but it might (will) change?? In that case can we have the patch as it stands and when the path to block devices in /sys changes, the ioctl can be changed at the same time to match? Or are you saying that as the kernel is today, some block devices appear under /devices/..., in which case could you please give an example? Thanks, NeilBrown