From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: FIBMAP/FIEMAP discrepancy for CAP_SYS_RAWIO Date: Sun, 06 Sep 2009 13:39:07 +0000 Message-ID: <87y6osry4k.fsf@mid.deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: linux-fsdevel@vger.kernel.org Return-path: Received: from mail.enyo.de ([212.9.189.167]:48978 "EHLO mail.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757942AbZIFOCI (ORCPT ); Sun, 6 Sep 2009 10:02:08 -0400 Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1MkHxU-0003Sr-0V for linux-fsdevel@vger.kernel.org; Sun, 06 Sep 2009 15:39:08 +0200 Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from ) id 1MkHxT-0003yG-H3 for linux-fsdevel@vger.kernel.org; Sun, 06 Sep 2009 13:39:07 +0000 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.)