From: syzbot <syzbot+77026564530dbc29b854@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] UBSAN: array-index-out-of-bounds in ocfs2_block_group_fill
Date: Tue, 28 Oct 2025 11:34:01 -0700 [thread overview]
Message-ID: <69010c99.050a0220.32483.01d3.GAE@google.com> (raw)
In-Reply-To: <20251028181936.web8g%dmantipov@yandex.ru>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/ocfs2/ocfs2_fs.h:474:40: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:489:40: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:502:43: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:646:26: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:659:16: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:807:37: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:943:43: error: expected ';' at end of declaration list
fs/ocfs2/ocfs2_fs.h:1030:39: error: expected ';' at end of declaration list
Tested on:
commit: d3d0b4e2 Linux 5.10.245
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.10.y
kernel config: https://syzkaller.appspot.com/x/.config?x=99cb6b007a8889ef
dashboard link: https://syzkaller.appspot.com/bug?extid=77026564530dbc29b854
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=15cc432f980000
next parent reply other threads:[~2025-10-28 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251028181936.web8g%dmantipov@yandex.ru>
2025-10-28 18:34 ` syzbot [this message]
[not found] <20251029062741.W5kof%dmantipov@yandex.ru>
2025-10-29 8:28 ` [syzbot] [ocfs2?] UBSAN: array-index-out-of-bounds in ocfs2_block_group_fill syzbot
[not found] <20251029062547.hO0d8%dmantipov@yandex.ru>
2025-10-29 8:05 ` syzbot
[not found] <20251029062152.Ai6wl%dmantipov@yandex.ru>
2025-10-29 7:43 ` syzbot
[not found] <20251028182253.F7MbO%dmantipov@yandex.ru>
2025-10-28 19:24 ` syzbot
[not found] <20251028182101.6rEOg%dmantipov@yandex.ru>
2025-10-28 18:52 ` syzbot
[not found] <20251028104119.eKN8w%dmantipov@yandex.ru>
2025-10-28 10:56 ` syzbot
[not found] <20251028104158.qdBzD%dmantipov@yandex.ru>
2025-10-28 10:56 ` syzbot
[not found] <20251028104005.R1CUs%dmantipov@yandex.ru>
2025-10-28 10:54 ` syzbot
[not found] <20251028070157.yQX9a%dmantipov@yandex.ru>
2025-10-28 7:49 ` syzbot
[not found] <20251024071531.TCWyW%dmantipov@yandex.ru>
2025-10-24 10:49 ` syzbot
[not found] <20251024071520.ZEdh5%dmantipov@yandex.ru>
2025-10-24 10:07 ` syzbot
[not found] <20251024071153.WcJfz%dmantipov@yandex.ru>
2025-10-24 8:31 ` syzbot
[not found] <20251022121312.jibxD%dmantipov@yandex.ru>
2025-10-22 12:46 ` syzbot
[not found] <28b06392-394e-4c77-a4db-5174cb605834@yandex.ru>
2025-10-17 11:26 ` syzbot
[not found] <20251015064502.30763-1-kartikey406@gmail.com>
2025-10-15 7:12 ` syzbot
[not found] <d8a13302-3be4-4ad7-a1f0-263bb9dc1ba4@yandex.ru>
2025-10-15 6:21 ` syzbot
[not found] <20251015044637.4721-1-kartikey406@gmail.com>
2025-10-15 5:15 ` syzbot
2025-10-15 2:12 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=69010c99.050a0220.32483.01d3.GAE@google.com \
--to=syzbot+77026564530dbc29b854@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--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.