From: Mike Christie <michaelc@cs.wisc.edu>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/5] convert st to use scsi_execte_async
Date: Sun, 18 Sep 2005 10:46:33 -0500 [thread overview]
Message-ID: <432D8BD9.2070300@cs.wisc.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0509182031090.15507@kai.makisara.local>
Kai Makisara wrote:
>
> init_command() is _not_ called. I added a printk to it and it did not
> print anything. If you look at scsi_prep_fn(), init_command() is called
> only if req->rq_disk is set. scsi_execute_async() does not set it.
oh yeah, sorry. I meant to add that back but would have had to add
another argument to the scsi_execute* functions since I could not figure
out how to go from scsi_device or request_queue to disk.
>
> Setting command parameters through the separate init_command() function
> seems like a horrible idea. You have to do hacks to pass the information.
This is how sd works :(
> The command triggering these problems is a 6-byte read of 10240 bytes. It
> should not a this point return anything but finish with some sense data.
>
> I am debugging the problem but it is going slowly because the system disk
> is a SCSI disk. I have to be careful with the debugging output and changes
> outside st.c require a reboot ;-) So far I have found out that
> scsi_check_sense() is called correctly and returns SUCCESS as it should.
> What happens after that is a mystery.
>
ok
next prev parent reply other threads:[~2005-09-18 17:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 4:39 [PATCH 4/5] convert st to use scsi_execte_async Mike Christie
2005-09-17 11:57 ` Kai Makisara
2005-09-17 15:43 ` Mike Christie
2005-09-17 15:55 ` Mike Christie
2005-09-17 16:25 ` Mike Christie
2005-09-18 12:01 ` Kai Makisara
2005-09-18 15:03 ` Mike Christie
2005-09-18 15:17 ` Mike Christie
2005-09-18 17:40 ` Kai Makisara
2005-09-18 15:46 ` Mike Christie [this message]
2005-09-18 16:13 ` Mike Christie
2005-09-18 16:08 ` Mike Christie
2005-09-18 16:36 ` Mike Christie
2005-09-18 16:38 ` Mike Christie
2005-09-18 19:03 ` Kai Makisara
2005-09-18 17:01 ` Mike Christie
2005-09-19 18:39 ` Kai Makisara
2005-09-19 19:22 ` Mike Christie
2005-09-20 19:23 ` Kai Makisara
2005-09-20 19:55 ` Mike Christie
2005-09-20 20:20 ` James Bottomley
2005-09-20 21:17 ` Kai Makisara
2005-09-20 22:39 ` Douglas Gilbert
2005-09-22 20:12 ` Kai Makisara
2005-09-23 3:20 ` Mike Christie
2005-09-17 15:57 ` Kai Makisara
2005-09-17 16:48 ` Kai Makisara
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=432D8BD9.2070300@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=Kai.Makisara@kolumbus.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.