linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	Junxiao Bi <junxiao.bi@oracle.com>
Subject: Re: [PATCH] ext4: use ext4_grp_locked_error in mb_find_extent
Date: Thu, 24 Jun 2021 11:55:01 +0200	[thread overview]
Message-ID: <20210624095501.jkd7iwu5bljw7xao@work> (raw)
In-Reply-To: <20210623232114.34457-1-stephen.s.brennan@oracle.com>

On Wed, Jun 23, 2021 at 04:21:14PM -0700, Stephen Brennan wrote:
> Commit 5d1b1b3f492f ("ext4: fix BUG when calling ext4_error with locked
> block group") introduces ext4_grp_locked_error to handle unlocking a
> group in error cases. Otherwise, there is a possibility of a sleep while
> atomic. However, since 43c73221b3b1 ("ext4: replace BUG_ON with WARN_ON
> in mb_find_extent()"), mb_find_extent() has contained a ext4_error()
> call while a group spinlock is held. Replace this with
> ext4_grp_locked_error.
> 
> Fixes: 43c73221b3b1 ("ext4: replace BUG_ON with WARN_ON in mb_find_extent()")
> Cc: <stable@vger.kernel.org> # 4.14+
> Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
> Reviewed-by: Junxiao Bi <junxiao.bi@oracle.com>

Good catch, looks good to me.

Reviewed-by: Lukas Czerner <lczerner@redhat.com>

Thanks!
-Lukas

> ---
>  fs/ext4/mballoc.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index c2c22c2baac0..089c958aa2c3 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -1909,10 +1909,11 @@ static int mb_find_extent(struct ext4_buddy *e4b, int block,
>  	if (ex->fe_start + ex->fe_len > EXT4_CLUSTERS_PER_GROUP(e4b->bd_sb)) {
>  		/* Should never happen! (but apparently sometimes does?!?) */
>  		WARN_ON(1);
> -		ext4_error(e4b->bd_sb, "corruption or bug in mb_find_extent "
> -			   "block=%d, order=%d needed=%d ex=%u/%d/%d@%u",
> -			   block, order, needed, ex->fe_group, ex->fe_start,
> -			   ex->fe_len, ex->fe_logical);
> +		ext4_grp_locked_error(e4b->bd_sb, e4b->bd_group, 0, 0,
> +			"corruption or bug in mb_find_extent "
> +			"block=%d, order=%d needed=%d ex=%u/%d/%d@%u",
> +			block, order, needed, ex->fe_group, ex->fe_start,
> +			ex->fe_len, ex->fe_logical);
>  		ex->fe_len = 0;
>  		ex->fe_start = 0;
>  		ex->fe_group = 0;
> -- 
> 2.30.2
> 


  reply	other threads:[~2021-06-24  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 23:21 [PATCH] ext4: use ext4_grp_locked_error in mb_find_extent Stephen Brennan
2021-06-24  9:55 ` Lukas Czerner [this message]
2021-07-01 21:14   ` Theodore Ts'o

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=20210624095501.jkd7iwu5bljw7xao@work \
    --to=lczerner@redhat.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=junxiao.bi@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen.s.brennan@oracle.com \
    --cc=tytso@mit.edu \
    /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).