From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f193.google.com ([209.85.192.193]:57288 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758457AbdKOV3n (ORCPT ); Wed, 15 Nov 2017 16:29:43 -0500 Received: by mail-pf0-f193.google.com with SMTP id q4so9807240pfg.13 for ; Wed, 15 Nov 2017 13:29:43 -0800 (PST) Date: Wed, 15 Nov 2017 13:29:40 -0800 From: Omar Sandoval To: Josef Bacik Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com, Josef Bacik Subject: Re: [PATCH] btrfs: fix deadlock when writing out space cache Message-ID: <20171115212940.GA28352@vader> References: <1510780852-8862-1-git-send-email-josef@toxicpanda.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1510780852-8862-1-git-send-email-josef@toxicpanda.com> Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Wed, Nov 15, 2017 at 04:20:52PM -0500, Josef Bacik wrote: > From: Josef Bacik > > If we fail to prepare our pages for whatever reason (out of memory in > our case) we need to make sure to drop the block_group->data_rwsem, > otherwise hilarity ensues. > > Signed-off-by: Josef Bacik Reviewed-by: Omar Sandoval > --- > fs/btrfs/free-space-cache.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c > index cdc9f4015ec3..a6c643275210 100644 > --- a/fs/btrfs/free-space-cache.c > +++ b/fs/btrfs/free-space-cache.c > @@ -1263,8 +1263,12 @@ static int __btrfs_write_out_cache(struct btrfs_root *root, struct inode *inode, > > /* Lock all pages first so we can lock the extent safely. */ > ret = io_ctl_prepare_pages(io_ctl, inode, 0); > - if (ret) > + if (ret) { > + if (block_group && > + (block_group->flags & BTRFS_BLOCK_GROUP_DATA)) > + up_write(&block_group->data_rwsem); > goto out; > + } > > lock_extent_bits(&BTRFS_I(inode)->io_tree, 0, i_size_read(inode) - 1, > &cached_state); > -- > 2.7.5 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html