From: Davidlohr Bueso <dave@gnu.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Karel Zak <kzak@redhat.com>,
util-linux <util-linux@vger.kernel.org>
Subject: fs locks: export informational name
Date: Sat, 28 Jan 2012 16:37:33 +0100 [thread overview]
Message-ID: <1327765053.3336.7.camel@offbook> (raw)
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
next reply other threads:[~2012-01-28 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 15:37 Davidlohr Bueso [this message]
2012-01-30 9:43 ` fs locks: export informational name Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327765053.3336.7.camel@offbook \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox