From: Wu Fengguang <fengguang.wu@intel.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] shmem: call set_page_dirty() with locked page
Date: Thu, 16 Jul 2009 10:12:39 +0800 [thread overview]
Message-ID: <20090716021239.GA5944@localhost> (raw)
In-Reply-To: <20090714153250.GA4149@hack>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
On Tue, Jul 14, 2009 at 11:33:08PM +0800, Américo Wang wrote:
> On Tue, Jul 14, 2009 at 05:29:26PM +0800, Wu Fengguang wrote:
> >Here set_page_dirty() can be moved into the page lock.
> >
> >CC: Hugh Dickins <hugh@veritas.com>
> >Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
>
> Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
Thank you.
Andi, please take the attached patch.
Thanks,
Fengguang
[-- Attachment #2: shmem-dirty-inside-page-lock.patch --]
[-- Type: text/x-diff, Size: 2090 bytes --]
shmem: call set_page_dirty() with locked page
The dirtying of page and set_page_dirty() can be moved into the page lock.
- In shmem_write_end(), the page was dirtied while the page lock was held,
but it's being marked dirty just after dropping the page lock.
- In shmem_symlink(), both dirtying and marking can be moved into page lock.
It's valuable for the hwpoison code to know whether one bad page can be dropped
without losing data. It mainly judges by testing the PG_dirty bit after taking
the page lock. So it becomes important that the dirtying of page and the
marking of dirtiness are both done inside the page lock. Which is a common
practice, but sadly not a rule.
The noticeable exceptions are
- mapped pages
- pages with buffer_heads
The above pages could go dirty at any time. Fortunately the hwpoison will
unmap the page and release the buffer_heads beforehand anyway.
Many other types of pages (eg. metadata pages) can also be dirtied at will by
their owners, the hwpoison code cannot do meaningful things to them anyway.
Only the dirtiness of pagecache pages owned by regular files are interested.
Acked-by: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
mm/shmem.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux.orig/mm/shmem.c
+++ linux/mm/shmem.c
@@ -1630,8 +1630,8 @@ shmem_write_end(struct file *file, struc
if (pos + copied > inode->i_size)
i_size_write(inode, pos + copied);
- unlock_page(page);
set_page_dirty(page);
+ unlock_page(page);
page_cache_release(page);
return copied;
@@ -1968,13 +1968,13 @@ static int shmem_symlink(struct inode *d
iput(inode);
return error;
}
- unlock_page(page);
inode->i_mapping->a_ops = &shmem_aops;
inode->i_op = &shmem_symlink_inode_operations;
kaddr = kmap_atomic(page, KM_USER0);
memcpy(kaddr, symname, len);
kunmap_atomic(kaddr, KM_USER0);
set_page_dirty(page);
+ unlock_page(page);
page_cache_release(page);
}
if (dir->i_mode & S_ISGID)
next prev parent reply other threads:[~2009-07-16 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 9:29 [PATCH] shmem: call set_page_dirty() with locked page Wu Fengguang
2009-07-14 15:33 ` Américo Wang
2009-07-16 2:12 ` Wu Fengguang [this message]
2009-07-14 18:24 ` Hugh Dickins
2009-07-15 11:10 ` Wu Fengguang
2009-07-15 11:17 ` Wu Fengguang
2009-07-15 13:18 ` Hugh Dickins
2009-07-15 14:04 ` Wu Fengguang
2009-07-15 14:22 ` Hugh Dickins
2009-07-15 14:28 ` Wu Fengguang
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=20090716021239.GA5944@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).