linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: hch@tuxera.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, jirislaby@gmail.com
Subject: Re: [PATCH] FS: hfsplus, fix lock imbalance
Date: Wed, 27 Oct 2010 13:52:06 +0200	[thread overview]
Message-ID: <20101027115206.GB26030@lst.de> (raw)
In-Reply-To: <1288180275-19941-1-git-send-email-jslaby@suse.cz>

On Wed, Oct 27, 2010 at 01:51:15PM +0200, Jiri Slaby wrote:
> Stanse found that there is mutex_lock in a fail path of
> hfsplus_ioctl_setflags (i.e. double lock + leaving a function in
> locked state). So fix that.

Dan Carpenter already sent the same fix and I applied it.  I'll push it
out to Linus soon.


      reply	other threads:[~2010-10-27 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 11:51 [PATCH] FS: hfsplus, fix lock imbalance Jiri Slaby
2010-10-27 11:52 ` Christoph Hellwig [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=20101027115206.GB26030@lst.de \
    --to=hch@lst.de \
    --cc=hch@tuxera.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@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 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).