From: "Johan Kullstam" <kullstam@ne.mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: Re: old bug in sym53c8xx still lurks in 2.2.20pre
Date: 26 Oct 2001 20:19:32 -0400 [thread overview]
Message-ID: <m21yjqdje3.fsf@euler.axel.nom> (raw)
In-Reply-To: <20011024235950.A25854@mail.harddata.com>
In-Reply-To: <20011024235950.A25854@mail.harddata.com>
Michal Jaegermann <michal@harddata.com> writes:
> Gerard Roudier posted at the beginning of an April a fix to a queue
> handling in that driver which seems to be forgotten. I was looking
> through 2.2.20pre and found that the bug is still there.
>
> There are two things about the bug - it may actually hit (some got it
> while running cdparanoia) and if you look closer at the original code
> you will see that it is quite suspicious. :-)
>
> Here it is again the fix as posted by Gerard re-diffed against
> 2.2.19something sources. It still applies cleanly to 2.2.20pre11.
>
>
> --- linux-2.2.19aa2/drivers/scsi/sym53c8xx.c.symx Sun Mar 25 09:31:33 2001
> +++ linux-2.2.19aa2/drivers/scsi/sym53c8xx.c Fri Apr 27 10:39:16 2001
> @@ -10125,14 +10125,13 @@
> if (i >= MAX_START*2)
> i = 0;
> }
> - assert(k != -1);
> - if (k != 1) {
> + if (k != -1) {
> np->squeue[k] = np->squeue[i]; /* Idle task */
> np->squeueput = k; /* Start queue pointer */
> - cp->host_status = HS_ABORTED;
> - cp->scsi_status = S_ILLEGAL;
> - ncr_complete(np, cp);
> }
> + cp->host_status = HS_ABORTED;
> + cp->scsi_status = S_ILLEGAL;
> + ncr_complete(np, cp);
> }
> break;
> /*
>
> Hm, I should possibly check the latest 2.4s as well.
i just checked 2.4.14-pre2 and this patch is in there. i didn't check
on older version or when it arrived so it may be in 2.4.X going way
back.
--
J o h a n K u l l s t a m
[kullstam@mediaone.net]
prev parent reply other threads:[~2001-10-27 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 5:59 old bug in sym53c8xx still lurks in 2.2.20pre Michal Jaegermann
2001-10-27 0:19 ` Johan Kullstam [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=m21yjqdje3.fsf@euler.axel.nom \
--to=kullstam@ne.mediaone.net \
--cc=linux-kernel@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.