linux-kernel - fs locks: export informational name

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>] [day] [month] [year] [list]

Message-ID: <1327765053.3336.7.camel@offbook>
Date:	Sat, 28 Jan 2012 16:37:33 +0100
From:	Davidlohr Bueso <dave@....org>
To:	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Cc:	lkml <linux-kernel@...r.kernel.org>, Karel Zak <kzak@...hat.com>,
	util-linux <util-linux@...r.kernel.org>
Subject: fs locks: export informational name

Hi,

I'm currently rewritting lslk(8) from scratch so we can integrate it in
util-linux, and continue maintaining it.

In order to not break userspace, the kernel is currently exporting the
major:minor numbers of the device where the locked file resides.  Could
we agree on defining WE_CAN_BREAK_LSLK_NOW and start exporting the
informational name instead?

Thanks,
Davidlohr

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