> > In one use case, the administrator then needs the ability to configure > > devices easily, for example to be much more restrictive on non-MMC > > devices. It must be done with the same tools it uses for other > > aspects of the policy---which will be a combination of DAC (Unix > > permissions and ACLs) and sysfs. Different SCSI standards may give > > different > > meanings for the same byte value, but a simple bitmap is enough for this. > > > > In the virtualization case, the problem is really that you want to > > pass through everything or almost everything, while still running > > as confined as possible (i.e. CAP_SYS_RAWIO is not a choice). But > > in this case a more complex filtering can be done just as easily in > > userspace, in the virtual machine monitor. > > > > One alternative is a ioctl to disable the filter altogether, to be > > used together with SCM_RIGHTS file descriptor passing. This works in > > the virtualization case but not for policy decisions. So this patch > > series provides the sysfs knob. It is a tweaked revert of commit > > 018e044 (block: get rid of queue-private command filter, 2009-06-26). > > If your use case at hand is mostly virtualization, I personally would > prefer the latter solution instead of extending in-kernel SG_IO > filter. It could be that I'm just not aware but I don't think there > have been too many complaints regarding other use cases. This type > of deep inspection and filtering has fairly strong tendency to be > unpopular. Userland configurable one is even scarier and I don't > think too many would know and make use of it in the end.
Actually I plan to set up the filtering in udev, so that we need not pass through many MMC commands (some of which have completely different meanings) to SBC devices. So it would really be useful. Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
