linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Greg KH <gregkh@suse.de>
Subject: Re: [patch] mm: bug in set_page_dirty_buffers
Date: Mon, 9 Oct 2006 22:01:27 -0700	[thread overview]
Message-ID: <20061009220127.c4721d2d.akpm@osdl.org> (raw)
In-Reply-To: <20061010044745.GA24600@wotan.suse.de>

On Tue, 10 Oct 2006 06:47:45 +0200
Nick Piggin <npiggin@suse.de> wrote:

> On Mon, Oct 09, 2006 at 09:38:06PM -0700, Andrew Morton wrote:
> > On Tue, 10 Oct 2006 06:21:44 +0200
> > Nick Piggin <npiggin@suse.de> wrote:
> > 
> > > On Mon, Oct 09, 2006 at 09:14:04PM -0700, Andrew Morton wrote:
> > > > Can we convert set_page_dirty_balance() to call set_page_dirty_lock()?
> > > 
> > > I think so. You can't in zap_pte_range though because you're under
> > > spinlocks.
> > 
> > There we're screwed.
> > 
> > > Same with try_to_unmap_{one|cluster}, and page_remove_rmap.
> > 
> > There we can trylock all the pages and bale if any fail.
> 
> Hmm, try_to_unmap is OK because the page is already locked. page_remove_rmap
> isn't allowed to fail.

I was talking about try_to_unmap_cluster().

> > > > And make set_page_dirty_lock() return if the page is already dirty?
> > > > 
> > > > > I think there are
> > > > > a whole lot more problems than just the unmapping path, though. Direct
> > > > > IO comes to mind.
> > > > 
> > > > Why?  direct-io locks the pages while invalidating them, and while marking
> > > > them dirty.
> > > 
> > > Uh, mistaken about dio. Point still stands.
> > 
> > But where?  locking the page is the preferred way to solve this stuff. 
> > (Well, locking the buffers might work, but isn't needed, and locking the
> > page covers other stuff)
> 
> AFAIKS, it is just fs/buffer.c that is racy.

Need to review all ->set_page_dirty, ->writepage, ->invalidatepage, ->etc
implementations before we can say that.

> Why can't it use
> mapping->private_lock or the buffer bit spinlock?

block_invalidatepage() wants to do lock_buffer().

It can probably be made to work.  But a sane interface is "when dinking
with page internals, lock the page".

Which leaves us with zap_pte_range().  Perhaps one could reuse
mmu_gather.pages[]: when it's full, drop locks, dirty pages (if needed),
retake locks, resume.

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-10-10  5:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  2:36 Nick Piggin
2006-10-10  3:06 ` Linus Torvalds
2006-10-10  3:19   ` Nick Piggin
2006-10-10  3:20   ` Andrew Morton
2006-10-10  3:34     ` Nick Piggin
2006-10-10  3:50       ` Andrew Morton
2006-10-10  3:58         ` Nick Piggin
2006-10-10  4:14           ` Andrew Morton
2006-10-10  4:21             ` Nick Piggin
2006-10-10  4:38               ` Andrew Morton
2006-10-10  4:47                 ` Nick Piggin
2006-10-10  5:01                   ` Andrew Morton [this message]
2006-10-10  5:22                     ` Nick Piggin
2006-10-10  5:29                       ` Andrew Morton
2006-10-10  5:48                         ` Nick Piggin
2006-10-10  6:08                           ` Andrew Morton
2006-10-10  6:19                             ` Nick Piggin
2006-10-10  6:27                               ` Andrew Morton
2006-10-10  6:39                                 ` Nick Piggin
2006-10-10  6:52                                   ` Nick Piggin
2006-10-10  7:06                                     ` Andrew Morton
2006-10-10  7:21                                       ` Nick Piggin
2006-10-10  8:07                                         ` Andrew Morton
2006-10-10  8:18                                           ` Nick Piggin
2006-10-10  8:41                                             ` Andrew Morton
2006-10-10  8:49                                               ` Nick Piggin
2006-10-10  9:07                                                 ` Andrew Morton
2006-10-10  9:23                                                   ` Nick Piggin
2006-10-10  6:48                       ` Peter Zijlstra
2006-10-10  6:59                         ` Nick Piggin
2006-10-10  7:11                           ` Peter Zijlstra
2006-10-10  7:30                             ` Nick Piggin
2006-10-10  4:11         ` Nick Piggin
2006-10-10  3:37     ` Andrew Morton
2006-10-10  3:42       ` Nick Piggin
2006-10-10  7:42 ` patch mm-bug-in-set_page_dirty_buffers.patch queued to -stable tree gregkh

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=20061009220127.c4721d2d.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=gregkh@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=torvalds@osdl.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