From: "Neil Conway" <nconway_kernel@yahoo.co.uk>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH, IDE corruption, 2.4.18
Date: Sun, 5 May 2002 21:44:31 +0100 (BST) [thread overview]
Message-ID: <20020505204431.74013.qmail@web21501.mail.yahoo.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0205051741140.23671-100000@mion.elka.pw.edu.pl>
--- Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>
> You've got been mistaken by unfortunate name (Martin changed
> name dmaproc() to udma() in 2.5.12).
> [snip]
> btw. udma() name is really misleading,
> it should be read (u)dma() not udma() :)
Ouch, thanks for the wakeup. I was scanning the code a little too
rapidly it seems...
Martin: why? The old IDE code was admittedly in need of some work, but
a name like dmaproc is very obviously a function. A name like udma is
likely to be (a) misconstrued by lusers like me as a variable, and (b)
misconstrued by all and sundry as something UDMA-specific, rather than
DMA-specific. Would it really be too much grief to rename it back to
dmaproc()? Misleading code will mutate into buggy code.
:-)
Now that a few people have cast their eyes over my report+patch, is it
safe to assume that the problem is real and not specific to my systems?
Also, does anyone understand why screwing up a DMA transfer results in
the trashing of inodes? Even better, how come this hasn't bitten many
more people? Surely there are lots of people out there with disks and
CDs on the same IDE cable...
Neil
(PS: I have reproduced the problem on two systems so far.)
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
next prev parent reply other threads:[~2002-05-05 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 15:49 Bartlomiej Zolnierkiewicz
2002-05-05 15:04 ` Martin Dalecki
2002-05-05 20:44 ` Neil Conway [this message]
2002-05-06 0:23 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 12:15 Neil Conway
2002-05-04 22:58 ` Andre Hedrick
2002-05-05 2:10 ` Neil Conway
2002-05-05 0:22 ` Mike Fedyk
2002-05-05 0:47 ` Andre Hedrick
2002-05-05 1:54 ` Neil Conway
2002-05-05 7:36 ` Mike Fedyk
2002-05-05 9:44 ` Neil Conway
2002-05-03 20:39 Neil Conway
2002-05-03 20:36 Neil Conway
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=20020505204431.74013.qmail@web21501.mail.yahoo.com \
--to=nconway_kernel@yahoo.co.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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 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®