From: Pat LaVarre <p.lavarre@ieee.org>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org
Subject: Re: zero block writes
Date: 14 Oct 2003 17:18:46 -0600 [thread overview]
Message-ID: <1066173526.3037.51.camel@patehci2> (raw)
In-Reply-To: <3F8C79F0.6070105@torque.net>
> Also when I tested this on scsi_debug, it complained
> about getting a NULL data buffer pointer.
CONFIG_SCSI_DEBUG option of .config was new to me, thanks.
> > $ sg_dd of=/dev/sg0 if=/dev/null bs=2k count=1
> > ...
> > usb-storage: Command WRITE_10 (10 bytes)
> ...
> bugs ...
Is this a bug?
Because CONFIG_SCSI_DEBUG complains of NULL pointers?
What patch do you like? No command at all? A zeroed command with no
NULL pointers?
I vote for the patch of no command at all because for me sg_dd exists to
let me read and write fragments longer than I can conveniently in the
single cdb of a single SG_IO. For me sg_dd doesn't exist to pass thru
creative variations of SG_IO. Ditto for you?
I'm guessing I have a clue what round means near hear because to get
that clue I reinvented the sg_dd wheel myself. In my pldd I included a
-v option to give me a cdb trace without reconfiguring the kernel to run
slow, so there I noticed this issue more quickly.
> A new beta (1.05) ... tomorrow ...
> one up about 1 hour ago).
Highly responsive, thank you.
I do enjoy perusing the links to the sg home page i.e.
http://www.google.com/search?q=link:www.torque.net/sg/
A google mystery of this moment is why google doesn't yet know that the
page where I discuss my reinvented sg_dd indeed does link to sg utils,
I can prove Google has my page cached. The search:
http://www.google.com/search?q=LaVarre+pldd
finds:
http://members.aol.com/plscsi/tools/pldd/
Yet seemingly Google hasn't yet parsed all the links from pldd.
Pat LaVarre
next prev parent reply other threads:[~2003-10-14 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 19:48 zero block writes Pat LaVarre
2003-10-14 22:34 ` Douglas Gilbert
2003-10-14 23:18 ` Pat LaVarre [this message]
2003-10-20 17:55 ` Pat LaVarre
2003-10-20 22:46 ` Pat LaVarre
2003-10-14 22:43 ` Pat LaVarre
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=1066173526.3037.51.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=dougg@torque.net \
--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