mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: rmk@arm.linux.org.uk (Russell King)
Cc: adam@yggdrasil.com (Adam J. Richter), linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.6 scsi DMA mapping and compilation fixes (not yet working)
Date: Wed, 13 Mar 2002 16:51:49 +0000 (GMT)	[thread overview]
Message-ID: <E16lByf-0006ph-00@the-village.bc.nu> (raw)
In-Reply-To: <20020312234256.B13558@flint.arm.linux.org.uk> from "Russell King" at Mar 12, 2002 11:42:56 PM

> I believe changes to NCR53c80 were recently reverted back because
> these "fixes" lead to massive data corruption.  It is preferable
> that the driver remains unbuildable, and therefore doesn't cause
> data corruption than to be buildable and case data corruption.

Someone "fixed" the 2.5 one by just frobbing randomly with the
io_request_lock without noticing its not always used per queue in the driver
(study the host list code - and dont think you can just clean that up by
 using SHIRQ - that wont help on some non x86 stuff). I fed Dave Jones
the 2.4 stuff where the locking is fixed (tho using io_request_lock) and
actually works SMP.

Dave then I suspect fed it to Linus

  reply	other threads:[~2002-03-13 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 20:56 Adam J. Richter
2002-03-12 23:42 ` Russell King
2002-03-13 16:51   ` Alan Cox [this message]
2002-03-12 23:55 Adam J. Richter
2002-03-13  0:02 ` Russell King
2002-03-13 14:31   ` Dave Jones
2002-03-13  0:23 Adam J. Richter
2002-03-13 14:33 ` Dave Jones
2002-03-13 15:51 Adam J. Richter
2002-03-13 16:22 ` Alan Cox
2002-03-13 17:17 Adam J. Richter
2002-03-13 17:38 ` Alan Cox
2002-03-14  1:02 Adam J. Richter
2002-03-14  1:27 ` 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=E16lByf-0006ph-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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®