All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	James.Bottomley@SteelEye.com
Subject: Re: [PATCH 1/2] streamline block SG_IO error processing
Date: Thu, 20 Jan 2005 11:13:30 +0000	[thread overview]
Message-ID: <20050120111330.GB32550@infradead.org> (raw)
In-Reply-To: <41E88F84.4000304@torque.net>

On Sat, Jan 15, 2005 at 01:35:32PM +1000, Douglas Gilbert wrote:
> I am working on the assumption that users of the
> SG_IO ioctl in the block layer (or via st or osst)
> want SCSI status and sense data returned
> via the ioctl immediately without:
>   - the error/warning silently disappearing and/or being
>     hidden by a retry (e.g. UNIT ATTENTION, lu becoming
>     ready)
>   - noise in the log (or console)
>   - any other side effects (save clearing expecting_cc_ua
>     if a UNIT ATTENTION was expected)

that's probably the right assumption.

> Changelog:
>   - cleanup scsi_end_request() documentation
>   - shorten path for block SG_IO through scsi_io_completion()
>   - for non-SG_IO sense processing in scsi_io_completion():
>      - ignore deferred errors (report + retry should suffice)
>      - consolidate into a cleaner switch statement

The patch looks extremly nice to me!

One extremly tiny nitpick though:

+	if (sense_valid && (! sense_deferred)) {

Both the space between ! and the variable and the superflous additional
bracket are against normal kernel style:

	if (sense_valid && !sense_deferred) {

But I think we can fix this while or after applying ;-)


      reply	other threads:[~2005-01-20 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15  3:35 [PATCH 1/2] streamline block SG_IO error processing Douglas Gilbert
2005-01-20 11:13 ` Christoph Hellwig [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=20050120111330.GB32550@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@SteelEye.com \
    --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 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.