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>
Subject: [PATCH 0/4] fsfreeze: from uninterruptible to killable waiting
Date: Sat, 06 Apr 2013 12:03:00 +0200 [thread overview]
Message-ID: <515FF2D4.2050307@gmail.com> (raw)
Hi all,
with this patch series we try to change the fs freeze behavior in order
to sleep in a killable state instead of sleeping in uninterruptible
state. The patches are *NOT* tested because but a first review is welcome.
The design is simply:
1) Internal fs operations are not changed from fsfreeze point of view,
sb_start_intwrite is not changed;
2) sb_start_write and sb_start_pagefault now return a proper error code
if the process receive SIGKILL and all the functions must manage this
error and return EINTR or VM_FAULT_RETRY.
Marco Stornelli (4):
fsfreeze: add new internal __sb_start_write_wait
fsfreeze: manage kill signal when sb_start_write is called
fsfreeze: manage kill signal when sb_start_pagefault is called
fsfreeze: avoid to return zero in __get_user_pages
fs/btrfs/file.c | 9 +++++++--
fs/btrfs/inode.c | 4 +++-
fs/buffer.c | 4 +++-
fs/cifs/file.c | 4 +++-
fs/ext4/inode.c | 4 +++-
fs/ext4/mmp.c | 3 ++-
fs/ext4/super.c | 4 +++-
fs/f2fs/file.c | 4 +++-
fs/fuse/file.c | 4 +++-
fs/gfs2/file.c | 4 +++-
fs/namespace.c | 8 ++++++--
fs/nilfs2/file.c | 4 +++-
fs/ntfs/file.c | 4 +++-
fs/ocfs2/file.c | 4 +++-
fs/ocfs2/mmap.c | 4 +++-
fs/open.c | 8 ++++++--
fs/splice.c | 4 +++-
fs/super.c | 47 ++++++++++++++++++++++++++++++++++++++++-------
fs/xfs/xfs_file.c | 4 +++-
include/linux/fs.h | 19 ++++++++++++-------
mm/filemap.c | 11 ++++++++---
mm/filemap_xip.c | 4 +++-
mm/memory.c | 2 +-
23 files changed, 127 insertions(+), 40 deletions(-)
--
1.7.3.4
---
next reply other threads:[~2013-04-06 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 10:03 Marco Stornelli [this message]
2013-04-06 15:22 ` [PATCH 0/4] fsfreeze: from uninterruptible to killable waiting Al Viro
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=515FF2D4.2050307@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.