public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Cameron <smcameron@yahoo.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, james.bottomley@steeleye.com,
	mike.miller@hp.com, steve.cameron@hp.com
Subject: Re: [PATCH] Perverting cciss
Date: Sun, 8 Apr 2007 09:26:06 -0700 (PDT)	[thread overview]
Message-ID: <759655.87535.qm@web33012.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070408101902.GA2275@infradead.org>


--- Christoph Hellwig <hch@infradead.org> wrote:
 
> Also is there a reason you don't want to pass down the various
> other ioctls scsi_cmd_ioctl can handle to it?

Didn't think about it, SG_IO is the one people were
clamoring for.

SG_GET_VERSION_NUM:
easily doable.

SCSI_IOCTL_GET_IDLUN:
Hmm, cciss is a block driver, and doesn't
really have an ID/LUN which are meaningful
in the normal sense of this ioctl.  If we
report something for this one, it is going to
conflict with some other device on the system
if that info is used in the usual way.  That is,
disk devices on cciss do not have any bus/target/lun
as far as linux is concerned, and aren't addressable
using those.

SCSI_IOCTL_GET_BUS_NUMBER:
Same problem as SCSI_IOCTL_GET_IDLUN.

SG_SET_TIMEOUT:
SG_GET_TIMEOUT:
Doable.  I don't think timeout will be honored though,
and I think this has to do with the sg driver, which
isn't involved with cciss anyhow, as cciss is not
a scsi driver (except for tape drives).

SG_GET_RESERVED_SIZE:
SG_SET_RESERVED_SIZE:
I think this is an sg driver thing and won't make
any difference for cciss, but we could pass it
through, I guess.

SG_EMULATED_HOST:

Er....  I guess we can do it:

/*
 * will always return that we are ATAPI even for a real SCSI drive, I'm not
 * so sure this is worth doing anything about (why would you care??)
 */
static int sg_emulated_host(request_queue_t *q, int __user *p)
{
        return put_user(1, p);
}

What's it for?



CDROM_SEND_PACKET:
CDROMCLOSETRAY:
CDROMEJECT:

I think all the CDROM stuff doesn't really apply.  CD-ROMs
on smartarray are not supported, nor are CD-ROMs presented
even if you attach one (excepting some weird tape device
that HP sells which sometimes pretends to be a CDROM for
booting purposes.) (Why would you put a cdrom on a RAID 
controller?)  I guess we could pass it through, it might not 
hurt, probably doesn't help though, and might give people
the mistaken impression that they can connect a SCSI cd-rom 
to a smartarray.

SCSI_IOCTL_SEND_COMMAND:

Doable, I think.

It'll be tomorrow at best before I can try anything out
or fix the other stuff you pointed out though.

-- steve




 
____________________________________________________________________________________
Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front

  reply	other threads:[~2007-04-08 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 17:07 [PATCH] Perverting cciss Stephen Cameron
2007-04-08 10:19 ` Christoph Hellwig
2007-04-08 16:26   ` Stephen Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-05  9:58 Hannes Reinecke
2007-04-05 10:03 ` Christoph Hellwig
2007-04-05 14:09   ` James Bottomley
2007-04-05 14:37     ` Miller, Mike (OS Dev)

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=759655.87535.qm@web33012.mail.mud.yahoo.com \
    --to=smcameron@yahoo.com \
    --cc=hch@infradead.org \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=steve.cameron@hp.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