public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Conway <nconway_kernel@yahoo.co.uk>,
	Andrew Morton <akpm@zip.com.au>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH, IDE corruption, 2.4.18
Date: Sun, 5 May 2002 17:23:05 -0700	[thread overview]
Message-ID: <20020506002305.GI2392@matchmail.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0205051741140.23671-100000@mion.elka.pw.edu.pl> <20020505204431.74013.qmail@web21501.mail.yahoo.com>

On Sun, May 05, 2002 at 09:44:31PM +0100, Neil Conway wrote:
>  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.)

That seems to be a seperate problem with the block layer and locked buffers
or pages (don't remember which).

I think a patch was submitted and integrated sometime in 2.4.19-pre.  Andrew
Morton would know more.

Mike

  reply	other threads:[~2002-05-06  0:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 15:49 PATCH, IDE corruption, 2.4.18 Bartlomiej Zolnierkiewicz
2002-05-05 15:04 ` Martin Dalecki
2002-05-05 20:44 ` Neil Conway
2002-05-06  0:23   ` Mike Fedyk [this message]
  -- 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=20020506002305.GI2392@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nconway_kernel@yahoo.co.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