linux-kernel - Re: [PATCHSET RFC] block/SCSI: implement in-kernel disk event handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101104183757.GA3883@linux.vnet.ibm.com>
Date:	Thu, 4 Nov 2010 11:37:57 -0700
From:	Mike Anderson <andmike@...ux.vnet.ibm.com>
To:	Douglas Gilbert <dgilbert@...erlog.com>
Cc:	Tejun Heo <tj@...nel.org>, axboe@...nel.dk,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	kay.sievers@...y.org, jack@...e.cz,
	James.Bottomley@...senPartnership.com
Subject: Re: [PATCHSET RFC] block/SCSI: implement in-kernel disk event
 handling

Douglas Gilbert <dgilbert@...erlog.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@...ux.vnet.ibm.com
--
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/