From: Andrew Morton <akpm@digeo.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: VM BUG, set_page_dirty() buggy?
Date: Sun, 27 Oct 2002 19:38:11 -0800 [thread overview]
Message-ID: <3DBCB123.5969FCC0@digeo.com> (raw)
In-Reply-To: 20021025094715.GF12628@suse.de
Jens Axboe wrote:
>
> Hi,
>
> I'm seeing what looks like a bug in set_page_dirty() in 2.5.44 (and
> 2.5.44-mm5), pages are being dumped.
It's not set_page_dirty() or direct IO. There's a fairly long-standing
bug in the writeback code which can cause the kernel to never write out
ext2 indirect blocks. Complete bastard of a thing it was, too.
I'll send out the fix shortly.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: VM BUG, set_page_dirty() buggy?
Date: Sun, 27 Oct 2002 19:38:11 -0800 [thread overview]
Message-ID: <3DBCB123.5969FCC0@digeo.com> (raw)
In-Reply-To: 20021025094715.GF12628@suse.de
Jens Axboe wrote:
>
> Hi,
>
> I'm seeing what looks like a bug in set_page_dirty() in 2.5.44 (and
> 2.5.44-mm5), pages are being dumped.
It's not set_page_dirty() or direct IO. There's a fairly long-standing
bug in the writeback code which can cause the kernel to never write out
ext2 indirect blocks. Complete bastard of a thing it was, too.
I'll send out the fix shortly.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-28 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 9:47 VM BUG, set_page_dirty() buggy? Jens Axboe
2002-10-25 9:47 ` Jens Axboe
2002-10-25 9:52 ` Jens Axboe
2002-10-28 3:38 ` Andrew Morton [this message]
2002-10-28 3:38 ` Andrew Morton
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=3DBCB123.5969FCC0@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.