From: Jens Axboe <axboe@suse.de>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: "David S. Miller" <davem@redhat.com>,
viro@math.psu.edu, linux-kernel@vger.kernel.org,
tytso@valinux.com
Subject: Re: 2.4.0-test11 ext2 fs corruption
Date: Wed, 29 Nov 2000 01:43:29 +0100 [thread overview]
Message-ID: <20001129014329.C23771@suse.de> (raw)
In-Reply-To: <E2C40AB5D29@vcnet.vc.cvut.cz>
In-Reply-To: <E2C40AB5D29@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Tue, Nov 28, 2000 at 09:46:56PM +0000
On Tue, Nov 28 2000, Petr Vandrovec wrote:
> On 28 Nov 00 at 12:04, David S. Miller wrote:
> >
> > Yes, it is identical copy. But I do not think that hdd can write same
> > data into two places with one command...
> >
> > Petr, did the af_inet.c assertions get triggered on this
> > same machine?
>
> No, ext2fs is at home, and af_inet is at work... At work I'm using
> vmware, at home I do not use it... But kernel sources are same
> (g450 patch for matroxfb, ncpfs supporting device nodes, threaded ipx;
> but neither ncpfs nor ipx is compiled at home).
> Petr Vandrovec
> vandrove@vc.cvut.cz
Petr,
Could you try and reproduce with attached patch? If this would trigger
I would assume fs corruption as well (which doesn't seem to be the
case for you), but it's worth a shot.
--- drivers/block/ll_rw_blk.c~ Wed Nov 29 01:30:22 2000
+++ drivers/block/ll_rw_blk.c Wed Nov 29 01:33:00 2000
@@ -684,7 +684,7 @@
int max_segments = MAX_SEGMENTS;
struct request * req = NULL, *freereq = NULL;
int rw_ahead, max_sectors, el_ret;
- struct list_head *head = &q->queue_head;
+ struct list_head *head;
int latency;
elevator_t *elevator = &q->elevator;
@@ -734,6 +734,7 @@
*/
again:
spin_lock_irq(&io_request_lock);
+ head = &q->queue_head;
/*
* skip first entry, for devices with active queue head
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-29 1:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 21:46 2.4.0-test11 ext2 fs corruption Petr Vandrovec
2000-11-29 0:43 ` Jens Axboe [this message]
2000-11-29 1:08 ` Andrea Arcangeli
2000-11-29 1:11 ` Jens Axboe
2000-11-29 1:32 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 12:41 Petr Vandrovec
2000-11-29 12:21 schwidefsky
2000-11-29 12:43 ` Alexander Viro
2000-11-28 21:10 Petr Vandrovec
2000-11-28 20:04 ` David S. Miller
2000-11-28 20:41 ` Alexander Viro
2000-11-29 16:26 ` Daniel Phillips
2000-11-28 20:32 Petr Vandrovec
2000-11-28 20:02 ` Alexander Viro
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=20001129014329.C23771@suse.de \
--to=axboe@suse.de \
--cc=VANDROVE@vc.cvut.cz \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@valinux.com \
--cc=viro@math.psu.edu \
/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