From: Lukas Czerner <lczerner@redhat.com>
To: viro@ZenIV.linux.org.uk
Cc: bfields@fieldses.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Lukas Czerner <lczerner@redhat.com>
Subject: [RFC][PATCH] fs: Prevent syncing frozen file system
Date: Thu, 9 Jul 2015 19:45:45 +0200 [thread overview]
Message-ID: <1436463945-12556-1-git-send-email-lczerner@redhat.com> (raw)
Currently we can end up in a deadlock because of broken
sb_start_write -> s_umount ordering.
The race goes like this:
- write the file
- unlink the file - final_iput will not be calles as file is opened
- freeze the file system
- Now simultaneously close the file and call sync (or syncfs on that
particular file system). Sync will get to wait_sb_inodes() where it will
grab the referece to the inode (__iget()) and later to call iput().
If we manage to close the file and drop the reference in between those
calls sync will attempt to do a iput_final() because the inode is now
unlinked and we're holding the last reference to it. This will
however block on a frozen file system (ext4_delete_inode for
example).
Note that I've not been able to reproduce the issue, I've only seen this
happen once. However with some instrumentation (like msleep() in the
wait_sb_inodes() it can be achieved.
Fix this by properly doing sb_start_write/sb_end_write to prevent us
from fsfreeze.
Note that with this patch syncfs will block on the frozen file system
which is probably ok, but sync will block if any file system happens to
be frozen - not sure if that's a problem, but it's certainly different
from what we've been used to.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
---
fs/super.c | 7 +++++++
fs/sync.c | 8 ++++++++
2 files changed, 15 insertions(+)
diff --git a/fs/super.c b/fs/super.c
index b613723..d337c91 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -514,10 +514,17 @@ void iterate_supers(void (*f)(struct super_block *, void *), void *arg)
sb->s_count++;
spin_unlock(&sb_lock);
+ /*
+ * Whatever we're going to do to the file system we have to
+ * make sure that we'll not end up blocking on frozen file
+ * system.
+ */
+ sb_start_write(sb);
down_read(&sb->s_umount);
if (sb->s_root && (sb->s_flags & MS_BORN))
f(sb, arg);
up_read(&sb->s_umount);
+ sb_end_write(sb);
spin_lock(&sb_lock);
if (p)
diff --git a/fs/sync.c b/fs/sync.c
index fbc98ee..074247f 100644
--- a/fs/sync.c
+++ b/fs/sync.c
@@ -156,9 +156,17 @@ SYSCALL_DEFINE1(syncfs, int, fd)
return -EBADF;
sb = f.file->f_path.dentry->d_sb;
+ /*
+ * If the file system is frozen we can't proceed because we
+ * could potentially block on frozen file system. This would
+ * lead to a deadlock, because we'll be holding s_umount which
+ * has to be taken in order to thaw the file system as well
+ */
+ sb_start_write(sb);
down_read(&sb->s_umount);
ret = sync_filesystem(sb);
up_read(&sb->s_umount);
+ sb_end_write(sb);
fdput(f);
return ret;
--
1.8.3.1
next reply other threads:[~2015-07-09 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 17:45 Lukas Czerner [this message]
2015-07-09 23:40 ` [RFC][PATCH] fs: Prevent syncing frozen file system Dave Chinner
2015-07-10 0:49 ` Dave Chinner
2015-07-10 14:25 ` Jan Kara
2015-07-10 20:42 ` Lukáš Czerner
2015-07-13 8:47 ` Jan Kara
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=1436463945-12556-1-git-send-email-lczerner@redhat.com \
--to=lczerner@redhat.com \
--cc=bfields@fieldses.org \
--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).