From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-btrfs@vger.kernel.org
Subject: Device names
Date: Mon, 18 Jun 2012 17:29:59 -0700 [thread overview]
Message-ID: <4FDFC807.2080209@zytor.com> (raw)
I just found out that all the device handling in btrfs is based on
pathnames, but shorter pathnames (1024) that PATH_MAX (4096).
This is confusing, and concerning for multiple reasons:
1. pathnames are namespace-specific; what is a pathname in one namespace
might not be in another.
2. different truncation rules in the rest of the kernel.
There seem to be no way one can do the equivalent of BTRFS_IOC_DEV_INFO
but actually get a device number or other stable information for that
device (that could be compared to a file descriptor for verification);
is that an accurate observation?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next reply other threads:[~2012-06-19 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 0:29 H. Peter Anvin [this message]
2012-06-19 23:51 ` Device names Chris Mason
2012-06-20 0:00 ` H. Peter Anvin
2012-06-20 13:37 ` Chris Mason
2012-06-20 17:06 ` Goffredo Baroncelli
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=4FDFC807.2080209@zytor.com \
--to=hpa@zytor.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).