From: schwidefsky@de.ibm.com
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11 ext2 fs corruption
Date: Wed, 29 Nov 2000 13:21:17 +0100 [thread overview]
Message-ID: <C12569A6.00448FBB.00@d12mta07.de.ibm.com> (raw)
>--- 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;
head = &q->queue_head is a simple offset calculation in the request
queue structure. Moving this into the spinlock won't change anything,
since q->queue_head isn't a pointer that can change.
Independent of that I can second the observation that test11 can corrupt
ext2 in memory. I think that this is related to the memory management
problems I see but I can't prove it yet.
blue skies,
Martin
Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com
-
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 reply other threads:[~2000-11-29 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 12:21 schwidefsky [this message]
2000-11-29 12:43 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 12:41 Petr Vandrovec
2000-11-28 21:46 Petr Vandrovec
2000-11-29 0:43 ` Jens Axboe
2000-11-29 1:08 ` Andrea Arcangeli
2000-11-29 1:11 ` Jens Axboe
2000-11-29 1:32 ` Andre Hedrick
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=C12569A6.00448FBB.00@d12mta07.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--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®