From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, RFC] check for frozen filesystems in the mmap path
Date: Tue, 21 Apr 2009 14:11:45 +0900 (JST) [thread overview]
Message-ID: <20090421140045.F125.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <49E7C323.9040805@redhat.com>
> Index: linux-2.6/mm/memory.c
> ===================================================================
> --- linux-2.6.orig/mm/memory.c
> +++ linux-2.6/mm/memory.c
> @@ -1944,6 +1944,7 @@ static int do_wp_page(struct mm_struct *
> * read-only shared pages can get COWed by
> * get_user_pages(.write=1, .force=1).
> */
> + vfs_check_frozen(old_page->mapping->host->i_sb, SB_FREEZE_WRITE);
> if (vma->vm_ops && vma->vm_ops->page_mkwrite) {
> struct vm_fault vmf;
> int tmp;
it seems strage.
1. it seems to have a race
CPU0 CPU1
----------------------------------------------------
do_wp_page
vfs_check_frozen
ioctl_fsfreeze
freeze_bdev
__fsync_super
process touch mem
vfs_check_frozen only wait to unfreeze, but not prevent new
new freeze request starting.
2. this logic kill multi thread application.
this logic mean mmap_sem grabbing until unfreeze.
it mean othrer thread in the same process can't page-fault although
it don't touch frozen-sb.
it seems strange.
next prev parent reply other threads:[~2009-04-21 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 23:45 Eric Sandeen
2009-04-20 14:55 ` Rik van Riel
2009-04-21 5:11 ` KOSAKI Motohiro [this message]
2009-04-21 15:15 ` Eric Sandeen
2009-04-22 1:35 ` KOSAKI Motohiro
2009-04-22 4:49 ` KOSAKI Motohiro
2009-04-22 5:01 ` Eric Sandeen
2009-04-22 5:29 ` KOSAKI Motohiro
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=20090421140045.F125.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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
all inboxes | Powered by JetHome®