From: Steve Lord <lord@sgi.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Steve Lord <lord@sgi.com>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Bounce buffer deadlock
Date: Sat, 30 Jun 2001 12:34:22 -0500 [thread overview]
Message-ID: <200106301734.f5UHYML03030@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Marcelo Tosatti <marcelo@conectiva.com.br> of "Sat, 30 Jun 2001 12:30:48 -0300." <Pine.LNX.4.21.0106301229280.3227-100000@freak.distro.conectiva>
>
>
> On Fri, 29 Jun 2001, Steve Lord wrote:
>
> >
> > Has anyone else seen a hang like this:
> >
> > bdflush()
> > flush_dirty_buffers()
> > ll_rw_block()
> > submit_bh(buffer X)
> > generic_make_request()
> > __make_request()
> > create_bounce()
> > alloc_bounce_page()
> > alloc_page()
> > try_to_free_pages()
> > do_try_to_free_pages()
> > page_launder()
> > try_to_free_buffers( , 2) -- i.e. wait for buffers
> > sync_page_buffers()
> > __wait_on_buffer(buffer X)
> >
> > Where the buffer head X going in the top of the stack is the same as the on
> e
> > we wait on at the bottom.
> >
> > There still seems to be nothing to prevent the try to free buffers from
> > blocking on a buffer like this. Setting a flag on the buffer around the
> > create_bounce call, and skipping it in the try_to_free_buffers path would
> > be one approach to avoiding this.
>
> Yes there is a bug: Linus is going to put a new fix soon.
>
> > I hit this in 2.4.6-pre6, and I don't see anything in the ac series to prot
> ect
> > against it.
>
> Thats because the -ac series does not contain the __GFP_BUFFER/__GFP_IO
> moditications which are in the -ac series.
It looks to me as if all memory allocations of type GFP_BUFFER which happen
in generic_make_request downwards can hit the same type of deadlock, so
bounce buffers, the request functions of the raid and lvm paths can all
end up in try_to_free_buffers on a buffer they themselves hold the lock on.
If the fix is to avoid page_launder in these cases then the number of
occurrences when an alloc_pages fails will go up. I was attempting to
come up with a way of making try_to_free_buffers fail on buffers which
are being processed in the generic_make_request path by marking them,
the problem is there is no single place to reset the state of a buffer so
that try_to_free_buffers will wait for it. Doing it after the end of the
loop in generic_make_request is race prone to say the least.
Steve
next prev parent reply other threads:[~2001-06-30 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 20:33 Steve Lord
2001-06-29 20:42 ` Alan Cox
2001-06-30 15:30 ` Marcelo Tosatti
2001-06-30 15:46 ` Marcelo Tosatti
2001-06-30 17:32 ` Linus Torvalds
2001-06-30 17:34 ` Steve Lord [this message]
2001-06-30 16:07 ` Marcelo Tosatti
2001-06-30 18:07 ` Steve Lord
2001-06-30 18:29 ` Marcelo Tosatti
2001-06-30 17:39 ` Linus Torvalds
2001-06-30 17:48 ` Steve Lord
2001-06-30 17:50 ` Linus Torvalds
2001-06-30 18:23 ` Steve Lord
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=200106301734.f5UHYML03030@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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®