[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1347449024-26387-1-git-send-email-pbonzini@redhat.com>
Date: Wed, 12 Sep 2012 13:23:41 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Tejun Heo <tj@...nel.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Jens Axboe <axboe@...nel.dk>,
Ric Wheeler <rwheeler@...hat.com>, linux-iscsi@...r.kernel.org
Subject: [PATCH 0/3] block: add queue-private command filter, editable via sysfs
The set of use cases for SG_IO is quite variable that no single filter can
accomodate all of them. The current filter is tailored very much to
CD burning, and includes many MMC-specific commands that may have
other meanings in different standards. Someone may want to remove
those commands; at the same time, people that trust their users may
want to add persistent reservations, trim/discard, or even access to
vendor-specific commands.
Filters used to be mutable via sysfs, but the implementation was
never enabled. Add it back, and let the admin set this up per device.
The ideal is that we would be much more restrictive by default and
give root the ability to override this both globally and per-device.
But this piece of the policy should probably be implemented in userspace
for better backwards compatibility.
In the meanwhile, 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).
Paolo Bonzini (3):
block: add back queue-private command filter
scsi: create an all-zero filter for scanners
block: add back command filter modification via sysfs
Documentation/block/queue-sysfs.txt | 16 +++++
block/Kconfig | 10 +++
block/blk-sysfs.c | 43 +++++++++++++
block/bsg.c | 2 +-
block/scsi_ioctl.c | 117 +++++++++++++++++++++++++++++++----
drivers/scsi/scsi_scan.c | 6 ++-
drivers/scsi/sg.c | 7 +-
include/linux/blkdev.h | 31 +++++++++-
8 files changed, 213 insertions(+), 19 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists