Re: [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP

Hi!

> Remove the need for having CAP_SYS_RAWIO when doing a FIBMAP call on an open file descriptor.
> 
> It would be nice to allow users to have permission to see where their data is landing on disk, and there really isn't a good reason to keep them from getting at this information.

I believe it is to prevent users from intentionally creating extremely
fragmented files...

You can read 60MB in a second, but fragmented 60MB file could take
10msec * 60MB/4KB = 150 seconds. That's factor 150 slowdown...

...but I agree that SYS_RAWIO may be wrong capability to cover this.

							Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP
    • From: Ric Wheeler <[email protected]>

• References:
  • [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP
    • From: Mike Waychison <[email protected]>

• Prev by Date: Re: [patch 1/4] spinlock: lockbreak cleanup
• Next by Date: Re: IRQ off latency of printk is very high
• Previous by thread: Re: [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP
• Next by thread: Re: [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]