linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH 0/2 v2][RFC] fsfreeze: from uninterruptible to killable
Date: Mon, 08 Apr 2013 18:20:51 +0200	[thread overview]
Message-ID: <5162EE63.2010301@gmail.com> (raw)

Hi,

after some comments, I changed the scope of the patch series. As Al
said the call of freezing are too deep in the call chain and to avoid
several headaches it's better to manage an interruption by sigkill only
when the call are enough "near" to the user space.
About the pagefault: actually the return VM_FAULT_RETRY from
page_mkwrite it seems possible but it can create some problem to the callers. Inside
page_mkwrite we should check if the caller has set FAULT_FLAG_ALLOW_RETRY
but this flag is not passed to the page_mkwrite callback, any tips about this point?

Marco Stornelli (2):
  fsfreeze: add new internal __sb_start_write_wait
  fsfreeze: replace sb_start_write with sb_start_write_killable

 fs/btrfs/file.c    |    4 +++-
 fs/cifs/file.c     |    4 +++-
 fs/fuse/file.c     |    4 +++-
 fs/ntfs/file.c     |    4 +++-
 fs/ocfs2/file.c    |    4 +++-
 fs/open.c          |    8 ++++++--
 fs/splice.c        |    4 +++-
 fs/super.c         |   47 ++++++++++++++++++++++++++++++++++++++++-------
 fs/xfs/xfs_file.c  |    4 +++-
 include/linux/fs.h |   23 ++++++++++++++++++-----
 mm/filemap.c       |    4 +++-
 mm/filemap_xip.c   |    4 +++-
 12 files changed, 91 insertions(+), 23 deletions(-)

-- 
1.7.3.4
---


                 reply	other threads:[~2013-04-08 16:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5162EE63.2010301@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).