From: Ming Zhang <mingz@ele.uri.edu>
To: berthiaume_wayne@emc.com
Cc: matthew@wil.cx, linux-scsi@vger.kernel.org, daper@daper.net
Subject: RE: read only scsi disk
Date: Thu, 09 Feb 2006 14:38:59 -0500 [thread overview]
Message-ID: <1139513939.9367.103.camel@localhost.localdomain> (raw)
In-Reply-To: <9EC133AF75DDC14683C0573992FB8AC10195ECB4@srlombardi.eng.emc.com>
thx.
but if i am correct, cdrom is handled in sr while disk is handled in sd.
so they are independent issues. of course, might be same reason. :P
the key here is why sd.c need to judge write protect only for removable
disk. is there no case that a disk is read only but not removable? for
example, if later a secure disk has internal security protection and
after authentication, the allowed option is only to read? this can be
common for networked disks.
ming
On Thu, 2006-02-09 at 14:32 -0500, berthiaume_wayne@emc.com wrote:
> I seem to recall this behavior had something to do with the handling of
> CD/ROM disks at one time.
>
> Regards,
> Wayne.
>
> -----Original Message-----
> From: linux-scsi-owner@vger.kernel.org
> [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Ming Zhang
> Sent: Thursday, February 09, 2006 2:19 PM
> To: Matthew Wilcox
> Cc: linux-scsi; Damian Pietras
> Subject: Re: read only scsi disk
>
> so fc disk is also removable, since anyone could unplug the fc cable at
> any time...
>
> so even parallel scsi disk, sata disk...
>
> i donot think this is a good reason. ;)
>
> ming
>
> On Thu, 2006-02-09 at 12:02 -0700, Matthew Wilcox wrote:
> > On Thu, Feb 09, 2006 at 12:04:07PM -0500, Ming Zhang wrote:
> > > We are adding the support for an OSS iscsi target to support export an
> > > iscsi disk as readonly. We set correct read only bit in sense dbd. But
> > > we found that only when we set the removable bit, the linux will
> > > actually check the ro bit. more detail information can be found from
> >
> > Surely all iSCSI discs are removable, since anyone could unplug the
> > network cable at any time ...
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-02-09 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 19:32 read only scsi disk berthiaume_wayne
2006-02-09 19:38 ` Ming Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 17:04 Ming Zhang
2006-02-09 19:02 ` Matthew Wilcox
2006-02-09 19:19 ` Ming Zhang
2006-02-09 19:54 ` Stefan Richter
2006-02-09 20:01 ` Ming Zhang
2006-02-10 10:35 ` Christoph Hellwig
2006-02-09 19:36 ` Stefan Richter
2006-02-09 19:41 ` Ming Zhang
2006-02-09 20:57 ` Stefan Richter
2006-02-09 21:11 ` Ming Zhang
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=1139513939.9367.103.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=berthiaume_wayne@emc.com \
--cc=daper@daper.net \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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