linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, htejun@gmail.com
Subject: Re: [PATCH] libata-eh: Add a simple mechanism for silencing error reporting
Date: Fri, 23 Feb 2007 05:27:05 -0500	[thread overview]
Message-ID: <45DEC179.1080308@garzik.org> (raw)
In-Reply-To: <20070205161124.48bf16c6@localhost.localdomain>

Alan wrote:
> We want to be able to issue commands that fail silently some of the time
> (set_features/xfer rate to CF 1.4 devices, perhaps some others such as
> user SG_IO commands ought to be silent too as the error is for the app)
> 
> This is a minimal implementation, we can extend it so the QUIET flag
> isn't quiet about errors that are not command errors but indicate
> infrastructre problems (CRC errors, HSM violation, DeviceFault) if need
> be.
> 
> Signed-off-by: Alan Cox <alan@redhat.com>
> 
> diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.20-rc6-mm3/drivers/ata/libata-eh.c linux-2.6.20-rc6-mm3/drivers/ata/libata-eh.c
> --- linux.vanilla-2.6.20-rc6-mm3/drivers/ata/libata-eh.c	2007-01-31 14:20:39.000000000 +0000
> +++ linux-2.6.20-rc6-mm3/drivers/ata/libata-eh.c	2007-01-31 14:27:25.000000000 +0000
> @@ -1407,6 +1407,8 @@
>  			continue;
>  		if (qc->flags & ATA_QCFLAG_SENSE_VALID && !qc->err_mask)
>  			continue;
> +		if (qc->tf.flags & ATA_TFLAG_QUIET)
> +			continue;
>  
>  		nr_failed++;
>  	}

I would rather pass an ok-to-fail-without-recovery type flag to EH. 
This TFLAG_QUIET approach is poorly defined, probably temporary, and not 
really interesting for upstream

	Jeff




  parent reply	other threads:[~2007-02-23 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 16:11 [PATCH] libata-eh: Add a simple mechanism for silencing error reporting Alan
2007-02-05 17:29 ` Tejun Heo
2007-02-23 10:27 ` Jeff Garzik [this message]
2007-02-23 12:10   ` Alan

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=45DEC179.1080308@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).