mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jeff Garzik <jeff@garzik.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-ide@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] ata: fix wrong WARN_ON_ONCE
Date: Tue, 13 Jan 2009 10:38:36 +0100	[thread overview]
Message-ID: <200901131038.36593.borntraeger@de.ibm.com> (raw)
In-Reply-To: <20090110152800.44308491@lxorguk.ukuu.org.uk>

Jeff, Alan,

this is still not fixed upstream. What about:

[PATCH] ata: fix wrong WARN_ON_ONCE

This patch fixes a wrong WARN_ON that was triggered by 32bit PIO support:
WARNING: at drivers/ata/libata-sff.c:1017 ata_sff_hsm_move+0x45e/0x750()

__atapi_pio_bytes simply doesnt know enough to decide if there is a bug.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 drivers/ata/libata-sff.c |    9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

Index: linux-2.6/drivers/ata/libata-sff.c
===================================================================
--- linux-2.6.orig/drivers/ata/libata-sff.c
+++ linux-2.6/drivers/ata/libata-sff.c
@@ -1013,9 +1013,12 @@ next_sg:
 		qc->cursg_ofs = 0;
 	}
 
-	/* consumed can be larger than count only for the last transfer */
-	WARN_ON_ONCE(qc->cursg && count != consumed);
-
+	/*
+	 * There used to be a  WARN_ON_ONCE(qc->cursg && count != consumed);
+	 * Unfortunately __atapi_pio_bytes doesn't know enough to do the WARN
+	 * check correctly as it doesn't know if it is the last request being
+	 * made. Somebody should implement a proper sanity check.
+	 */
 	if (bytes)
 		goto next_sg;
 	return 0;

  parent reply	other threads:[~2009-01-13  9:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 12:34 todays git: WARNING: at drivers/ata/libata-sff.c:1017 ata_sff_hsm_move+0x45e/0x750() Christian Borntraeger
2009-01-09 12:44 ` Alan Cox
2009-01-09 13:09   ` Christian Borntraeger
2009-01-10  9:09   ` Christian Borntraeger
2009-01-10 10:41     ` Alan Cox
2009-01-10 11:42       ` Christian Borntraeger
2009-01-10 11:49         ` Sergei Shtylyov
2009-01-10 12:21           ` Alan Cox
2009-01-10 13:01             ` Sergei Shtylyov
2009-01-10 13:55               ` Alan Cox
2009-01-10 13:04             ` Christian Borntraeger
2009-01-10 13:14               ` Jeff Garzik
2009-01-10 13:27                 ` Christian Borntraeger
2009-01-10 13:51                 ` Alan Cox
2009-01-10 21:21                   ` Arjan van de Ven
2009-01-10 13:07             ` Ingo Molnar
2009-01-10 13:12               ` Jeff Garzik
2009-01-10 13:24                 ` Ingo Molnar
2009-01-10 13:36                   ` [bisected] " Ingo Molnar
2009-01-10 13:57                     ` Alan Cox
2009-01-10 15:10                       ` Sergei Shtylyov
2009-01-10 15:28                         ` Alan Cox
2009-01-10 15:59                           ` Sergei Shtylyov
2009-01-10 20:06                             ` Sergei Shtylyov
2009-01-10 20:31                               ` Jeff Garzik
2009-01-10 20:50                                 ` Sergei Shtylyov
2009-01-11  0:10                               ` Alan Cox
2009-01-11  9:18                                 ` Sergei Shtylyov
2009-01-11 11:24                                   ` Alan Cox
2009-01-13  9:38                           ` Christian Borntraeger [this message]
2009-01-10 13:57                     ` Christian Borntraeger
2009-01-10 13:53               ` Alan Cox
2009-01-10 14:36             ` James Bottomley
2009-01-10 15:03               ` Jeff Garzik
2009-01-10 15:12               ` Alan Cox
2009-01-10 15:22                 ` James Bottomley
2009-01-10 15:29                   ` Alan Cox
2009-01-10 15:34                   ` Sergei Shtylyov
2009-01-10 15:29                 ` Sergei Shtylyov
2009-01-10 15:32                   ` Alan Cox

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=200901131038.36593.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sshtylyov@ru.mvista.com \
    /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®