reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jeff Mahoney <jeffm@jeffreymahoney.com>
Cc: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>,
	Thomas Siedentopf <thomas.siedentopf@novell.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] reiserfs: Fix locking BUG during mount failure
Date: Mon, 29 Mar 2010 21:52:34 +0200	[thread overview]
Message-ID: <20100329195232.GI5101@nowhere> (raw)
In-Reply-To: <4BB0FBA7.5080703@jeffreymahoney.com>

On Mon, Mar 29, 2010 at 03:12:39PM -0400, Jeff Mahoney wrote:
>  Commit 8ebc423238341b52912c7295b045a32477b33f09 (reiserfs: kill-the-BKL)
>  introduced a bug in the mount failure case.
> 
>  The error label releases the lock before calling journal_release_error,
>  but it requires that the lock be held. do_journal_release unlocks and
>  retakes it. When it releases it without it held, we trigger a BUG().
> 
>  The error_alloc label skips the unlock since the lock isn't held yet 
>  but none of the other conditions that are clean up exist yet either.
> 
>  This patch returns immediately after the kzalloc failure and moves
>  the reiserfs_write_unlock after the journal_release_error call.
> 
>  This was reported in https://bugzilla.novell.com/show_bug.cgi?id=591807
> 
> Reported-by:  Thomas Siedentopf <thomas.siedentopf@novell.com>
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>


I've applied it. Thanks a lot!



> ---
>  fs/reiserfs/super.c |   10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> --- a/fs/reiserfs/super.c
> +++ b/fs/reiserfs/super.c
> @@ -1618,10 +1618,8 @@ static int reiserfs_fill_super(struct su
>  	save_mount_options(s, data);
>  
>  	sbi = kzalloc(sizeof(struct reiserfs_sb_info), GFP_KERNEL);
> -	if (!sbi) {
> -		errval = -ENOMEM;
> -		goto error_alloc;
> -	}
> +	if (!sbi)
> +		return -ENOMEM;
>  	s->s_fs_info = sbi;
>  	/* Set default values for options: non-aggressive tails, RO on errors */
>  	REISERFS_SB(s)->s_mount_opt |= (1 << REISERFS_SMALLTAIL);
> @@ -1881,12 +1879,12 @@ static int reiserfs_fill_super(struct su
>  	return (0);
>  
>  error:
> -	reiserfs_write_unlock(s);
> -error_alloc:
>  	if (jinit_done) {	/* kill the commit thread, free journal ram */
>  		journal_release_error(NULL, s);
>  	}
>  
> +	reiserfs_write_unlock(s);
> +
>  	reiserfs_free_bitmap_cache(s);
>  	if (SB_BUFFER_WITH_SB(s))
>  		brelse(SB_BUFFER_WITH_SB(s));


      reply	other threads:[~2010-03-29 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 19:12 [PATCH] reiserfs: Fix locking BUG during mount failure Jeff Mahoney
2010-03-29 19:52 ` Frederic Weisbecker [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=20100329195232.GI5101@nowhere \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeffm@jeffreymahoney.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=thomas.siedentopf@novell.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).