From: Peter Zijlstra <peterz@infradead.org>
To: stefani@seibold.net
Cc: linux-mm@kvack.org, Hugh Dickins <hugh@veritas.com>,
Jaya Kumar <jayakumar.lkml@gmail.com>
Subject: Re: vm_ops.page_mkwrite() fails with vmalloc on 2.6.23
Date: Mon, 22 Oct 2007 19:20:56 +0200 [thread overview]
Message-ID: <1193073656.27435.188.camel@twins> (raw)
In-Reply-To: <1193073477.27435.186.camel@twins>
On Mon, 2007-10-22 at 19:17 +0200, Peter Zijlstra wrote:
> On Mon, 2007-10-22 at 16:45 +0200, Stefani Seibold wrote:
> > Hi,
> >
> > i have a problem with vmalloc() and vm_ops.page_mkwrite().
> >
> > ReadOnly access works, but on a write access the VM will
> > endless invoke the vm_ops.page_mkwrite() handler.
> >
> > I tracked down the problem to the
> > struct page.mapping pointer,
> > which is NULL.
>
> Where?
>
> would this happen to be in set_page_dirty_balance(, .page_mkwrite=1) ?
>
> I indeed over-looked the fb_defio driver when I grepped the tree for
> ->page_mkwrite() usage :-/
>
> The proper fix is to revert this set_page_dirty_balance() hack and make
> the filesystem ->page_mkwrite() implementations call
> balance_dirty_pages_ratelimited()
Hmm, that should all work out when page->mapping is NULL.
/me goes look again..
Aaah, the truncate fixlet, yes that will mess one up..
/me goes ponder what to do about that..
--
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:[~2007-10-22 17:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 14:45 vm_ops.page_mkwrite() fails with vmalloc on 2.6.23 Stefani Seibold
2007-10-22 16:37 ` Hugh Dickins
2007-10-22 17:03 ` Jaya Kumar
2007-10-22 17:17 ` Peter Zijlstra
2007-10-22 17:20 ` Peter Zijlstra [this message]
[not found] <1193064057.16541.1.camel@matrix>
2007-10-29 7:40 ` Andrew Morton
2007-10-29 8:17 ` Jaya Kumar
2007-10-29 10:11 ` Peter Zijlstra
2007-10-29 12:35 ` Peter Zijlstra
2007-10-29 14:28 ` Nick Piggin
2007-10-29 17:01 ` Peter Zijlstra
2007-10-29 17:51 ` Jaya Kumar
2007-10-29 18:17 ` Peter Zijlstra
2007-10-29 22:16 ` Peter Zijlstra
2007-10-30 1:22 ` Jaya Kumar
2007-10-30 9:56 ` Peter Zijlstra
2007-10-30 10:49 ` Stefani Seibold
2007-10-30 12:39 ` Hugh Dickins
2007-10-30 13:12 ` Peter Zijlstra
2007-10-30 13:16 ` Jaya Kumar
2007-10-30 13:25 ` Peter Zijlstra
2007-10-30 15:47 ` Hugh Dickins
2007-10-30 15:51 ` Peter Zijlstra
2007-11-01 8:02 ` Jaya Kumar
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=1193073656.27435.188.camel@twins \
--to=peterz@infradead.org \
--cc=hugh@veritas.com \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-mm@kvack.org \
--cc=stefani@seibold.net \
/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;
as well as URLs for NNTP newsgroup(s).