Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, axboe@suse.de, patmans@us.ibm.com
Subject: Re: [PATCH] until blockdev --setrw /dev/scd$n works
Date: 08 Dec 2003 10:10:31 -0700	[thread overview]
Message-ID: <1070903431.2263.16.camel@patibmrh9> (raw)
In-Reply-To: <1070674338.2939.31.camel@patibmrh9>

> > +		printk("lk 2.5 ide-cd.c would refuse write\n"); ...
> > +			printk("lk 2.5 sr.c would refuse write\n"); ...
> > +			printk("lk 2.5 cdrom.c would refuse write\n"); ...
> ...
> 2) I have two pre-production samples of the same device: one ATAPI, one
> USB.  Without my patch my ATAPI device never writes, and for my USB
> device I have to volunteer `blockdev --setrw` or `blockdev --setro`
> again after each disc insertion.

Ouch this English doesn't say what I mean.  Instead I should have said:

a) cdrom.ko refuses to pass thru writes unless patched.

b) sr_mod.ko refuses to pass thru writes unless patched.

c) ide-cd.ko refuses to pass thru writes unless patched or asked via
ioctl e.g. via blockdev --setrw.

I'm guessing the maintainers of cdrom.ko sr_mod.ko would accept a patch
to make blockdev --setrw work for those as well as it already does for
ide-cd.ko.

Pat LaVarre

      reply	other threads:[~2003-12-08 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  1:24 [PATCH] until blockdev --setrw /dev/scd$n works Pat LaVarre
2003-12-06  1:32 ` Pat LaVarre
2003-12-08 17:10   ` Pat LaVarre [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=1070903431.2263.16.camel@patibmrh9 \
    --to=p.lavarre@ieee.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    /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