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>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH, RFC] check for frozen filesystems in the mmap path
Date: Wed, 22 Apr 2009 13:49:21 +0900 (JST) [thread overview]
Message-ID: <20090422132451.62A4.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <49EDE319.10701@redhat.com>
> > 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.
>
> Hm, I hadn't thought about this ... On the one hand, ->page_mkwrite can
> already sleep, though a userspace freeze/unfreeze could potentially take
> much much longer. freeze/unfreeze *should* happen very quickly, but
> nothing enforces that.
>
> Do you have any suggestions?
One more comment.
I read ioctl_fsfreeze() and freeze_bdev(), it call __fsync_super().
Oh, I don't think __fsync_suepr is very quick.
So, page-fault have one unique characteristics.
if page-fault return 0 without pte change, page-fault is occur again soon.
then, if you need long time waiting, I think you can use following technique.
unlock mmap_sem
wait long-time
lock mmap_sem
goto out;
it cause page-fault counter increment twice unintesionally.
but no problem. fs-freeze is not freqently event.
Am I missing anything?
next prev parent reply other threads:[~2009-04-22 4:49 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
2009-04-21 15:15 ` Eric Sandeen
2009-04-22 1:35 ` KOSAKI Motohiro
2009-04-22 4:49 ` KOSAKI Motohiro [this message]
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=20090422132451.62A4.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--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®