linux-kernel - Re: [PATCH] block: look up block device path in sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1201545839.25736.10.camel@dwillia2-linux.ch.intel.com>
Date:	Mon, 28 Jan 2008 11:43:59 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	akpm@...ux-foundation.org, jens.axboe@...cle.com, neilb@...e.de,
	kay.sievers@...y.org, linux-kernel@...r.kernel.org,
	viro@...IV.linux.org.uk
Subject: Re: [PATCH] block: look up block device path in sysfs

On Sat, 2008-01-26 at 13:22 -0700, Christoph Hellwig wrote:
> On Fri, Jan 25, 2008 at 10:04:51PM -0700, Dan Williams 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.
> >
> > Ideally we should have an ioctl that works on char devices as well,
> > but that seems far from trivial, so it seems reasonable to have
> > this until the latter can be implemented.
> 
> What did you do to address Viro's reasonable rejection of this when
> it came up last time?

What was the objection?

My search only came up with a discussion about possibly making this a
generic capability for all devices:
http://marc.info/?t=118646704500006&r=1&w=2

Regards,
Dan

--
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/