From: Jan Kara <jack@suse.cz>
To: Ye Bin <yebin10@huawei.com>
Cc: jack@suse.cz, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ext2: dump current reservation window info before BUG
Date: Mon, 14 Aug 2023 15:08:30 +0200 [thread overview]
Message-ID: <20230814130830.kizeni4hk5vjtqkm@quack3> (raw)
In-Reply-To: <20230811033857.1800578-3-yebin10@huawei.com>
On Fri 11-08-23 11:38:57, Ye Bin wrote:
> There's report BUG in 'ext2_try_to_allocate_with_rsv()', although there's
> now dump of all reservation windows information. But there's unknown which
> window is being processed.So this is not helpful for locating the issue.
> To better analyze the problem, dump the information about reservation window
> that is being processed.
>
> Signed-off-by: Ye Bin <yebin10@huawei.com>
> ---
> fs/ext2/balloc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/fs/ext2/balloc.c b/fs/ext2/balloc.c
> index 039f655febfd..0132b8af546e 100644
> --- a/fs/ext2/balloc.c
> +++ b/fs/ext2/balloc.c
> @@ -1131,6 +1131,11 @@ ext2_try_to_allocate_with_rsv(struct super_block *sb, unsigned int group,
>
> if ((my_rsv->rsv_start > group_last_block) ||
> (my_rsv->rsv_end < group_first_block)) {
> + ext2_error(sb, __func__,
> + "Out of group %u range goal %d fsb[%lu,%lu] rsv[%lu, %lu]",
^^^ "Reservation out of group ...."
> + group, grp_goal, group_first_block,
> + group_last_block, my_rsv->rsv_start,
> + my_rsv->rsv_end);
> rsv_window_dump(&EXT2_SB(sb)->s_rsv_window_root, 1);
> BUG();
> }
And we could just bail with error instead of BUG here when we are already
changing the code...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-08-14 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 3:38 [PATCH 0/2] fix race between setxattr and write back Ye Bin
2023-08-11 3:38 ` [PATCH 1/2] ext2: " Ye Bin
2023-08-14 12:46 ` Jan Kara
2023-08-14 15:42 ` yebin (H)
2023-08-11 3:38 ` [PATCH 2/2] ext2: dump current reservation window info before BUG Ye Bin
2023-08-14 13:08 ` Jan Kara [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=20230814130830.kizeni4hk5vjtqkm@quack3 \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin10@huawei.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
all inboxes | Powered by JetHome®