From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Prithvi Tambewagh <activprithvi@gmail.com>,
jlbec@evilplan.org, mark@fasheh.com
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: Syzbot test for v2 for fs: ocfs2: fix kernel BUG in ocfs2_find_victim_chain
Date: Mon, 1 Dec 2025 15:40:36 +0800 [thread overview]
Message-ID: <46be391e-da73-4eee-a30b-e404653a76c2@linux.alibaba.com> (raw)
In-Reply-To: <20251201073538.47128-1-activprithvi@gmail.com>
On 2025/12/1 15:35, Prithvi Tambewagh wrote:
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 939f15e640f193616691d3bcde0089760e75b0d3
>
> Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
> ---
> fs/ocfs2/suballoc.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/fs/ocfs2/suballoc.c b/fs/ocfs2/suballoc.c
> index 6ac4dcd54588..f4e4ef08e0f9 100644
> --- a/fs/ocfs2/suballoc.c
> +++ b/fs/ocfs2/suballoc.c
> @@ -1992,6 +1992,13 @@ static int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *ac,
> }
>
> cl = (struct ocfs2_chain_list *) &fe->id2.i_chain;
> + if (!le16_to_cpu(cl->cl_next_free_rec) ||
> + le16_to_cpu(cl->cl_next_free_rec) > le16_to_cpu(cl->cl_count)) {
^
Prefer to align here.
BTW, the prefix for patch title can be "ocfs2: " only.
Joseph
> + status = ocfs2_error(ac->ac_inode->i_sb,
> + "Chain allocator dinode %llu has 0 chains\n",
> + (unsigned long long)le64_to_cpu(fe->i_blkno));
> + goto bail;
> + }
>
> victim = ocfs2_find_victim_chain(cl);
> ac->ac_chain = victim;
>
> base-commit: 939f15e640f193616691d3bcde0089760e75b0d3
next prev parent reply other threads:[~2025-12-01 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 8:11 [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
2025-11-29 19:05 ` Syzbot test for fs: ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-11-29 19:05 ` syzbot
2025-11-29 19:13 ` Prithvi Tambewagh
2025-11-29 19:38 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
2025-12-01 7:35 ` Syzbot test for v2 for fs: ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-12-01 7:36 ` syzbot
2025-12-01 7:40 ` Joseph Qi [this message]
2025-12-01 7:37 ` Prithvi Tambewagh
2025-12-01 8:48 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
2025-12-01 10:19 ` Syzbot test for v3: ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-12-01 11:31 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
2025-12-01 11:43 ` Syzbot test for v3: ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-12-01 12:05 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
2025-12-01 12:17 ` Syzbot testing for v3: ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-12-01 12:43 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits syzbot
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=46be391e-da73-4eee-a30b-e404653a76c2@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=activprithvi@gmail.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.