All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Jan Kara <jack@suse.cz>, Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH 0/4] fsfreeze: from uninterruptible to killable
Date: Fri, 26 Apr 2013 10:48:00 +0200	[thread overview]
Message-ID: <517A3F40.1030707@gmail.com> (raw)

Hi,

I re-send the patch series. The first three patches are not changed 
since the last review, but I add a fourth patch to manage the killable 
state in mnt_want_write/mnt_want_write_file. I did some tests and it 
seems ok to me. The hot points were do_last, kern_path_create and 
mq_open. At the moment the path not covered is the page_mkwrite, however 
it could be covered with a future patch. The work made until now is 
sufficient to give the user the possibility to do a "kill -9" in several 
cases.

Marco Stornelli (4):
   fsfreeze: wait in killable state in __sb_start_write
   fsfreeze: added new file_start_write_killable
   fsfreeze: use sb_start_write_killable instead of sb_start_write
   fsfreeze: return EINTR from mnt_want_write and mnt_want_write_file

  drivers/block/loop.c |    4 +++-
  fs/aio.c             |    7 +++++--
  fs/coda/file.c       |    4 +++-
  fs/namei.c           |    6 ++++++
  fs/namespace.c       |    8 ++++++--
  fs/open.c            |    8 ++++++--
  fs/read_write.c      |   28 +++++++++++++++++-----------
  fs/splice.c          |    4 +++-
  fs/super.c           |   24 ++++++++++++++++++------
  include/linux/fs.h   |   36 ++++++++++++++++++++++++++++++------
  ipc/mqueue.c         |    6 +++++-
  11 files changed, 102 insertions(+), 33 deletions(-)

-- 
1.7.3.4
---

                 reply	other threads:[~2013-04-26  8:48 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=517A3F40.1030707@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.