From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, dchinner@redhat.com,
Alex Elder <elder@kernel.org>,
Anton Altaparmakov <anton@tuxera.com>, Ben Myers <bpm@sgi.com>,
Chris Mason <chris.mason@oracle.com>,
cluster-devel@redhat.com, "David S. Miller" <davem@davemloft.net>,
fuse-devel@lists.sourceforge.net,
"J. Bruce Fields" <bfields@fieldses.org>,
Joel Becker <jlbec@evilplan.org>,
KONISHI Ryusuke <konishi.ryusuke@lab.ntt.co.jp>,
linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-nilfs@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
Mark Fasheh <mfasheh@suse.com>,
Miklos Szeredi <miklos@szeredi.hu>,
ocfs2-devel@oss.oracle.com,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Steven Whitehouse <swhiteho@redhat.com>,
"Theodore Ts'o" <tytso@mit.edu>,
xfs@oss.sgi.com
Subject: Re: [PATCH 00/27 v6] Fix filesystem freezing deadlocks
Date: Sat, 9 Jun 2012 07:29:52 +0100 [thread overview]
Message-ID: <20120609062952.GY30000@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1338589841-9568-1-git-send-email-jack@suse.cz>
On Sat, Jun 02, 2012 at 12:30:14AM +0200, Jan Kara wrote:
> Hello,
>
> here is the sixth iteration of my patches to improve filesystem freezing.
> The change since last iteration is that filesystem can be frozen with open but
> unlinked files. After some thinking, I've decided that the best way to handle
> this is to block removal inside ->evict_inode() of each filesystem and use
> fs-internal level of freeze protection for that (usually I've instrumented
> filesystem's transaction system to use freeze protection). Handling
> inside VFS would be less work but the only level of freeze protection that
> has a chance of not causing deadlocks is the one used for page faults and even
> there it's not clear lock ordering would be correct wrt some fs-specific locks.
> I've converted ext2, ext4, btrfs, xfs, nilfs2, ocfs2, gfs2 and also checked
> that ext3, reiserfs, jfs should work as well (they have their internal freeze
> protection mechanisms, possibly they could be replaced by a generic one but
> given these are mostly aging filesystems, it's not a real priority IHMO).
> So finally I'm not aware of any pending issue with this patch set so if you
> have some concern, please speak up!
Could you rebase on top of e.g. -rc2 and repost?
prev parent reply other threads:[~2012-06-09 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 22:30 [PATCH 00/27 v6] Fix filesystem freezing deadlocks Jan Kara
2012-06-01 22:30 ` [PATCH 11/27] btrfs: Push mnt_want_write() outside of i_mutex Jan Kara
2012-06-01 22:30 ` [PATCH 24/27] btrfs: Convert to new freezing mechanism Jan Kara
2012-06-09 6:29 ` Al Viro [this message]
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=20120609062952.GY30000@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=anton@tuxera.com \
--cc=bfields@fieldses.org \
--cc=bpm@sgi.com \
--cc=chris.mason@oracle.com \
--cc=cluster-devel@redhat.com \
--cc=davem@davemloft.net \
--cc=dchinner@redhat.com \
--cc=elder@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mfasheh@suse.com \
--cc=miklos@szeredi.hu \
--cc=ocfs2-devel@oss.oracle.com \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.com \
/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).