From: Florian Weimer <fw@deneb.enyo.de>
To: linux-fsdevel@vger.kernel.org
Subject: FIBMAP/FIEMAP discrepancy for CAP_SYS_RAWIO
Date: Sun, 06 Sep 2009 13:39:07 +0000 [thread overview]
Message-ID: <87y6osry4k.fsf@mid.deneb.enyo.de> (raw)
The FIBMAP ioctl requires CAP_SYS_RAWIO, but FIEMAP doesn't. Why's
that? Is it that there is no backwards-compatible way to introduce
locking on the bmap path?
(Sorting file access based on the first block number of the file
really improves performance, even compared to inode number sorting,
that's why I'm asking.)
next reply other threads:[~2009-09-06 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 13:39 Florian Weimer [this message]
2009-09-07 10:50 ` FIBMAP/FIEMAP discrepancy for CAP_SYS_RAWIO Andreas Dilger
2009-09-07 13:28 ` Theodore Tso
2009-09-07 16:26 ` Florian Weimer
2009-09-08 7:23 ` Andreas Dilger
2009-09-08 8:47 ` Jamie Lokier
2009-09-09 16:13 ` Andreas Dilger
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=87y6osry4k.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.