Thread (9 messages) 9 messages, 4 authors, 2017-05-10

Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl

From: Darrick J. Wong <hidden>
Date: 2017-05-08 18:41:18
Also in: linux-api, linux-fsdevel, linux-man, linux-xfs

On Mon, May 08, 2017 at 12:17:53AM +0200, Jann Horn wrote:
On Sun, May 7, 2017 at 5:58 PM, Darrick J. Wong [off-list ref] wrote:
quoted
Document the new GETFSMAP ioctl that returns the physical layout of a
(disk-based) filesystem.
[...]
quoted
+.B EPERM
+This query is not allowed.
Please document the circumstances under which a query is allowed.
For the two current implementations, queries are always allowed.

(The doc could be more explicit about this decision being left to the
implementation.)
Also: From a quick glance at the XFS implementation, I don't see any
privilege checks. Am I missing something, or does this API permit an
unprivileged user to determine the number of physical blocks allocated
for any inode, even for inodes the user can't ordinarily see in any
way?
Correct.

--D
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help