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/3 v3][RFC] fsfreeze: from uninterruptible to killable
Date: Sat, 13 Apr 2013 12:34:40 +0200 [thread overview]
Message-ID: <516934C0.2080103@gmail.com> (raw)
Hi,
I rebased the work on top of -next and I applied a Jan's comment about __sb_start_write.
I did some basic tests and they are ok.
Open points:
- without change mnt_want_write several paths are still blocking paths;
- page_mkwrite still call blocking variant of __sb_start_write.
Any comments are welcome.
Regards.
Marco Stornelli (3):
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
drivers/block/loop.c | 4 +++-
fs/aio.c | 7 +++++--
fs/coda/file.c | 4 +++-
fs/open.c | 8 ++++++--
fs/read_write.c | 28 +++++++++++++++++-----------
fs/splice.c | 4 +++-
fs/super.c | 24 ++++++++++++++++++------
include/linux/fs.h | 36 ++++++++++++++++++++++++++++++------
8 files changed, 85 insertions(+), 30 deletions(-)
--
1.7.3.4
---
reply other threads:[~2013-04-13 10:41 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=516934C0.2080103@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 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).