[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0810051901190.31780@hs20-bc2-1.build.redhat.com>
Date: Sun, 5 Oct 2008 19:02:57 -0400 (EDT)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Arjan van de Ven <arjan@...radead.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, agk@...hat.com, mbroz@...hat.com,
chris@...chsys.com
Subject: Re: [PATCH 2/3] Fix fsync livelock
On Sun, 5 Oct 2008, Arjan van de Ven wrote:
> On Sun, 5 Oct 2008 18:14:50 -0400 (EDT)
> Mikulas Patocka <mpatocka@...hat.com> wrote:
>
> > Fix starvation in memory management.
> >
> > The bug happens when one process is doing sequential buffered writes
> > to a block device (or file) and another process is attempting to
> > execute sync(), fsync() or direct-IO on that device (or file). This
> > syncing process will wait indefinitelly, until the first writing
> > process finishes.
> >
> > For example, run these two commands:
> > dd if=/dev/zero of=/dev/sda1 bs=65536 &
> > dd if=/dev/sda1 of=/dev/null bs=4096 count=1 iflag=direct
> >
> > The bug is caused by sequential walking of address space in
> > write_cache_pages and wait_on_page_writeback_range: if some other
> > process is constantly making dirty and writeback pages while these
> > functions run, the functions will wait on every new page, resulting in
> > indefinite wait.
>
> are you sure?
> isn't the right fix to just walk the file pages only once?
It walks the pages only once --- and waits on each on them. But because
new pages are contantly appearing under it, that "walk only once" becomes
infinite loop (well, finite, until the whole disk is written).
Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists