mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
To: "Ju, Seokmann" <Seokmann.Ju@engenio.com>,
	"James Bottomley" <James.Bottomley@SteelEye.com>
Cc: "linux-scsi" <linux-scsi@vger.kernel.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Question: where should the SCSI driver place MODE_SENSE data ?
Date: Tue, 21 Mar 2006 15:43:17 -0700	[thread overview]
Message-ID: <9738BCBE884FDB42801FAD8A7769C265142117@NAMAIL1.ad.lsil.com> (raw)

Any comment on this question would be appreciated.
Thanks you, 

> -----Original Message-----
> From: Ju, Seokmann 
> Sent: Tuesday, March 21, 2006 11:45 AM
> To: 'James Bottomley'
> Cc: linux-scsi; linux-kernel
> Subject: Question: where should the SCSI driver place 
> MODE_SENSE data ?
> 
> In the 2.6 (2.6.9 and scsi-misc in git) kernel, MODE_SENSE 
> SCSI command packet (scsi_cmnd) carries following entries 
> with unexpectedly small in size.
> - request_bufflen
> - bufflen
> 
> Especially for MODE SENSE with page code 8 (caching page), 
> driver has minumum 12 Bytes MODE_SENSE data to deliver 
> besides 'mode parameter header' and 'block descriptors'.
> When I dump those entries, they both are 4 Bytes in size.
> To me, it seems like that SCSI mid layer allocated 512 Bytes 
> for MODE_SENSE data buffer, but the buffer length passed down 
> to LLD incorrectly.
> 
> Please guide me if there is anything missing.
> 
> Thank you,
> 
> Seokmann

             reply	other threads:[~2006-03-21 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 22:43 Ju, Seokmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-22 15:52 Ju, Seokmann
2006-03-22 16:14 ` James Bottomley
2006-03-21 16:44 Ju, Seokmann
2006-03-21 23:01 ` James Bottomley

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=9738BCBE884FDB42801FAD8A7769C265142117@NAMAIL1.ad.lsil.com \
    --to=seokmann.ju@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Seokmann.Ju@engenio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®