lkml.org 
[lkml]   [1999]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: FIBMAP ioctl restrictions: why?
Date
From
> to GDBM) and I want to sort file accesses before feeding them to the kernel,
> so that they will be executed in linear sector order and seek time will be
> minimized. Unfortunately, this plan breaks on the FIBMAP ioctl requiring
> CAP_SYS_RAWIO capability. To be honest, I don't see why -- can the kernel
> gurus advise me what deep reasons are behind this restriction?

Well firstly you should think very hard before trying this because most
operations will be filled from cache and many file systems dont have
constant block numbering - NFS for example. Block numbers may also be in
a logical not physical space so not relate to the media.

To answer the detail question. Several parts of the linux system do
insufficient checking for FIBMAP currently to be user accessible.

Alan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:2.034 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site