From: liubo <liubo2009@cn.fujitsu.com>
To: David Sterba <dsterba@suse.cz>
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/1] btrfs: add missing spin_unlock to a rare exit path
Date: Thu, 21 Apr 2011 09:02:32 +0800 [thread overview]
Message-ID: <4DAF8228.2080402@cn.fujitsu.com> (raw)
In-Reply-To: <1303302855-23093-1-git-send-email-dsterba@suse.cz>
Good catch!
thanks,
liubo
On 04/20/2011 08:34 PM, David Sterba wrote:
> Signed-off-by: David Sterba <dsterba@suse.cz>
> ---
> fs/btrfs/disk-io.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 5e5d07c..25e4b8f 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2825,6 +2825,7 @@ static int btrfs_destroy_delayed_refs(struct btrfs_transaction *trans,
>
> spin_lock(&delayed_refs->lock);
> if (delayed_refs->num_entries == 0) {
> + spin_unlock(&delayed_refs->lock);
> printk(KERN_INFO "delayed_refs has NO entry\n");
> return ret;
> }
prev parent reply other threads:[~2011-04-21 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 12:34 [PATCH 1/1] btrfs: add missing spin_unlock to a rare exit path David Sterba
2011-04-21 1:02 ` liubo [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=4DAF8228.2080402@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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 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).