From: Christoph Hellwig <hch@infradead.org>
To: pc-linscsi2@crowcastle.net
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] always check write protect
Date: Thu, 26 Jun 2003 08:37:19 +0100 [thread overview]
Message-ID: <20030626083719.A22880@infradead.org> (raw)
In-Reply-To: <20030624210448.486.qmail@emc.com>; from pc-linscsi2@crowcastle.net on Tue, Jun 24, 2003 at 09:04:48PM -0000
On Tue, Jun 24, 2003 at 09:04:48PM -0000, pc-linscsi2@crowcastle.net wrote:
> The current version of sd.c only checks the write protect status for
> removable media. This is wrong--you can have write-protected non-removable
> media. This is common with high-end storage arrays. This patch corrects
> the behaviour. It applies with slight line offsets to recent 2.4 kernels,
> including 2.4.21.
What about a patch like the following for 2.5? It also address your
fixme by calling check_disk_change (and thus sd_revalidate_disk) in
->open when the write_prot flag is set.
diff -Nru a/drivers/scsi/sd.c b/drivers/scsi/sd.c
--- a/drivers/scsi/sd.c Wed Jun 25 11:47:26 2003
+++ b/drivers/scsi/sd.c Wed Jun 25 11:47:26 2003
@@ -368,25 +368,24 @@
if (!scsi_block_when_processing_errors(sdev))
goto error_out;
- if (sdev->removable) {
+ if (sdev->removable || sdkp->write_prot)
check_disk_change(inode->i_bdev);
- /*
- * If the drive is empty, just let the open fail.
- */
- retval = -ENOMEDIUM;
- if ((!sdkp->media_present) && !(filp->f_flags & O_NDELAY))
- goto error_out;
+ /*
+ * If the drive is empty, just let the open fail.
+ */
+ retval = -ENOMEDIUM;
+ if (sdev->removable && !sdkp->media_present &&
+ !(filp->f_flags & O_NDELAY))
+ goto error_out;
- /*
- * Similarly, if the device has the write protect tab set,
- * have the open fail if the user expects to be able to write
- * to the thing.
- */
- retval = -EROFS;
- if ((sdkp->write_prot) && (filp->f_mode & FMODE_WRITE))
- goto error_out;
- }
+ /*
+ * If the device has the write protect tab set, have the open fail
+ * if the user expects to be able to write to the thing.
+ */
+ retval = -EROFS;
+ if ((sdkp->write_prot) && (filp->f_mode & FMODE_WRITE))
+ goto error_out;
/*
* It is possible that the disk changing stuff resulted in
prev parent reply other threads:[~2003-06-26 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 21:04 [PATCH] always check write protect pc-linscsi2
2003-06-26 7:37 ` Christoph Hellwig [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=20030626083719.A22880@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pc-linscsi2@crowcastle.net \
/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