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]
Date:	Thu, 23 Feb 2012 13:01:06 -0800
From:	Andrew Morton <>
To: (Eric W. Biederman)
Cc:, "J. Bruce Fields" <>,
	Matthew Wilcox <>,
	lkml <>,
	linux-fsdevel <>
Subject: Re: [PATCH] locks: new procfs lockinfo

On Wed, 22 Feb 2012 16:38:27 -0800 (Eric W. Biederman) wrote:

> Davidlohr Bueso <> writes:
> > From: Davidlohr Bueso <>
> >
> > Based on our previous discussion we came to
> > agree on deprecating the current /proc/locks in favor of a more extensible interface.
> > The new /proc/lockinfo file exports similar information - except instead of maj:min the
> > device name is shown - and entries are formated like those in /proc/cpuinfo, allowing us
> > to add new entries without breaking userspace.
> You can't know the device name, attempt to say what you don't know seems
> very dangerous.  It may be reasonable to simply give the deivce number
> and not split the device number into major/minor any more and I am
> concerned about reality.

I don't think we've ever been told any *reason* for switching from
major:minor to device-name.  This is a problem.

And yes, major:minor reliably and uniquely identifies the device.  I'm
not sure that the human-readable string which is largely a convenience
thing is as reliable as this.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists