linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: Tejun Heo <tj@kernel.org>,
	axboe@kernel.dk, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, kay.sievers@vrfy.org, jack@suse.cz,
	James.Bottomley@HansenPartnership.com
Subject: Re: [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling
Date: Thu, 4 Nov 2010 11:37:57 -0700	[thread overview]
Message-ID: <20101104183757.GA3883@linux.vnet.ibm.com> (raw)
In-Reply-To: <4CD2E83A.9020309@interlog.com>

Douglas Gilbert <dgilbert@interlog.com> wrote:
<snip>
> Ideally I would like to see a way from the user space
> to uncouple a unit from the sd (or sr) driver, in a
> similar way to how an LLD can use
> scsi_device::no_uld_attach . That would restrict user
> space access to the bsg or sg driver. 

I am not sure if this is exactly what you want but you can unbind a
device from the sd driver today.

E.x.

# cd /sys/bus/scsi/drivers/sd
# ls
0:0:0:0  4:0:0:0  4:0:1:0  5:0:0:0  5:0:1:0  bind  unbind
# sg_map
/dev/sg0  /dev/sda
/dev/sg1  /dev/sdb
/dev/sg2  /dev/sdc
/dev/sg3  /dev/sdd
/dev/sg4  /dev/sde
# echo "5:0:1:0" > unbind
# ls
0:0:0:0  4:0:0:0  4:0:1:0  5:0:0:0  bind  unbind
# sg_map
/dev/sg0  /dev/sda
/dev/sg1  /dev/sdb
/dev/sg2  /dev/sdc
/dev/sg3  /dev/sdd
/dev/sg4

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com

      reply	other threads:[~2010-11-04 18:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 18:44 [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling Tejun Heo
2010-11-01 18:44 ` [PATCH 1/7] block: kill genhd_media_change_notify() Tejun Heo
2010-11-01 18:44 ` [PATCH 2/7] block: move register_disk() and del_gendisk() to block/genhd.c Tejun Heo
2010-11-01 18:44 ` [PATCH 3/7] implement in-kernel gendisk events handling Tejun Heo
2010-11-01 18:44 ` [PATCH 4/7] cdrom: add ->check_events() support Tejun Heo
2010-11-01 18:44 ` [PATCH 5/7] scsi: replace sr_test_unit_ready() with scsi_test_unit_ready() Tejun Heo
2010-11-01 18:44 ` [PATCH 6/7] sr: implement sr_check_events() Tejun Heo
2010-11-01 18:44 ` [PATCH 7/7] sd: implement sd_check_events() Tejun Heo
2010-11-04 17:07 ` [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling Douglas Gilbert
2010-11-04 18:37   ` Mike Anderson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101104183757.GA3883@linux.vnet.ibm.com \
    --to=andmike@linux.vnet.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=dgilbert@interlog.com \
    --cc=jack@suse.cz \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).