From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@osdl.org>
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: Tue, 10 Oct 2006 10:49:31 +0200 [thread overview]
Message-ID: <20061010084931.GB24748@wotan.suse.de> (raw)
In-Reply-To: <20061010014114.75c424f0.akpm@osdl.org>
On Tue, Oct 10, 2006 at 01:41:14AM -0700, Andrew Morton wrote:
> On Tue, 10 Oct 2006 10:18:20 +0200
> Nick Piggin <npiggin@suse.de> wrote:
>
> > > If the buffer's redirtied after discard_buffer() got at it, we've got some
> > > nasty problems in there.
> > >
> > > Are you sure this race can happen? Nobody's allowed to have a page mapped
> > > while it's undergoing truncation (vmtruncate()).
> >
> > Well, not technically. I think it can happen with nonlinear pages now,
>
> How?
It is the pagefault vs invalidate race. It happens with truncate with
nonlinear mappings because they don't have the truncate_count logic.
It can also happen with normal pagecache vs invalidate_inode_pages2.
> > but that is a bug in truncate and I have some patches to fix them.
> >
> > But anyone who has done a get_user_pages, AFAIKS, can later run a
> > set_page_dirty on the pages.
>
> Most (all?) callers are (and should be) using set_page_dirty_lock().
They don't, and I haven't checked but I doubt it is because they
always have the page locked.
> > Nasty problem, but I think we are OK to
> > just ignore the dirty bits in this case, because the truncate might
> > well have happened _after_ the get_user_pages guy set the page dirty
> > anyway.
> >
> > > There might be a problem with the final blocks in the page outside i_size.
> > > iirc what happens here is that the bh outside i_size _is_ marked dirty, but
> > > writepage() will notice that it's outside i_size and will just mark it
> > > clean again without doing IO.
> >
> > Didn't think of that. How does it get to writepage though, if it has
> > lost its mapping?
>
> It was only partially truncated - it's still on the address_space.
Oh OK fine.
--
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>
next prev parent reply other threads:[~2006-10-10 8:49 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
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 [this message]
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=20061010084931.GB24748@wotan.suse.de \
--to=npiggin@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-mm@kvack.org \
--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