Thread (24 messages) 24 messages, 5 authors, 2012-09-12

Re: [Ping^3] Re: [PATCH] sg_io: allow UNMAP and WRITE SAME without CAP_SYS_RAWIO

From: Paolo Bonzini <pbonzini@redhat.com>
Date: 2012-09-06 06:31:54
Also in: lkml

Il 05/09/2012 22:18, Ric Wheeler ha scritto:
quoted
Hi Paolo,

Both of these commands are destructive. WRITE_SAME (if done without the
discard bits set) can also take a very long time to be destructive and
tie up the storage.
FORMAT_UNIT has the same characteristics and yet it is allowed (btw, I
don't think WRITE SAME slowness is limited to the case where a real
write is requested; discarding can be just as slow).

Also, the two new commands are anyway restricted to programs that have
write access to the disk.  If you have read-only access, you won't be
able to issue any destructive command (there is one exception, START
STOP UNIT is allowed even with read-only capability and is somewhat
destructive).

Honestly, the only reason why these two commands weren't included, is
that the current whitelist is heavily tailored towards CD/DVD burning.
I think that restricting them to CAP_SYS_RAWIO seems reasonable - better
to vet and give the appropriate apps the needed capability than to
widely open up the safety check?
CAP_SYS_RAWIO is so wide in its scope, that anything that requires it is
insecure.

Paolo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help