From: syzbot <syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.com>
To: activprithvi@gmail.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_claim_suballoc_bits
Date: Mon, 01 Dec 2025 03:31:03 -0800 [thread overview]
Message-ID: <692d7c77.a70a0220.d98e3.0186.GAE@google.com> (raw)
In-Reply-To: <20251201101938.103998-1-activprithvi@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/ocfs2/suballoc.c:2082:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2116:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2143:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2152:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2215:1: error: function definition is not allowed here
:2289:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2330:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2345:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2364:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2392:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2463:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2479:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2562:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2631:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2640:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2658:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2700:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2715:1: error: function definition is not allowed here
fs/ocfs2/suballoc.c:2736:1: error: function definition is not allowed here
Tested on:
commit: 939f15e6 Merge tag 'turbostat-2025.06.08' of git://git..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=d9ebb51ccc2ec42f
dashboard link: https://syzkaller.appspot.com/bug?extid=96d38c6e1655c1420a72
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=12782512580000
next prev parent reply other threads:[~2025-12-01 11:31 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
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 [this message]
2025-12-01 11:43 ` 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=692d7c77.a70a0220.d98e3.0186.GAE@google.com \
--to=syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.com \
--cc=activprithvi@gmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--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.