linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] affs: fix missing unlocks in affs_remove_link
Date: Wed, 21 May 2008 14:38:21 +0200	[thread overview]
Message-ID: <20080521123821.GA23617@lst.de> (raw)
In-Reply-To: <20080509103529.GA7445@lst.de>

ping?

On Fri, May 09, 2008 at 12:35:29PM +0200, Christoph Hellwig wrote:
> In two error cases affs_remove_link doesn't call affs_unlock_dir to
> release the i_hash_lock semaphore.
> 
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Index: linux-2.6/fs/affs/amigaffs.c
> ===================================================================
> --- linux-2.6.orig/fs/affs/amigaffs.c	2008-04-29 17:15:30.000000000 +0200
> +++ linux-2.6/fs/affs/amigaffs.c	2008-04-29 17:16:15.000000000 +0200
> @@ -179,14 +179,18 @@ affs_remove_link(struct dentry *dentry)
>  		affs_lock_dir(dir);
>  		affs_fix_dcache(dentry, link_ino);
>  		retval = affs_remove_hash(dir, link_bh);
> -		if (retval)
> +		if (retval) {
> +			affs_unlock_dir(dir);
>  			goto done;
> +		}
>  		mark_buffer_dirty_inode(link_bh, inode);
>  
>  		memcpy(AFFS_TAIL(sb, bh)->name, AFFS_TAIL(sb, link_bh)->name, 32);
>  		retval = affs_insert_hash(dir, bh);
> -		if (retval)
> +		if (retval) {
> +			affs_unlock_dir(dir);
>  			goto done;
> +		}
>  		mark_buffer_dirty_inode(bh, inode);
>  
>  		affs_unlock_dir(dir);
---end quoted text---

  reply	other threads:[~2008-05-21 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 10:35 [PATCH] affs: fix missing unlocks in affs_remove_link Christoph Hellwig
2008-05-21 12:38 ` Christoph Hellwig [this message]
2008-08-10 23:47   ` Christoph Hellwig
2008-09-08 17:36     ` Christoph Hellwig

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=20080521123821.GA23617@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zippel@linux-m68k.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).