mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Lord <lord@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Bounce buffer deadlock
Date: Fri, 29 Jun 2001 15:33:52 -0500	[thread overview]
Message-ID: <200106292033.f5TKXqw03584@jen.americas.sgi.com> (raw)


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 one
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.

I hit this in 2.4.6-pre6, and I don't see anything in the ac series to protect
against it.

Steve



             reply	other threads:[~2001-06-29 20:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 20:33 Steve Lord [this message]
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
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=200106292033.f5TKXqw03584@jen.americas.sgi.com \
    --to=lord@sgi.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®