From: syzbot <syzbot+19e0be39cc25dfcb0858@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, nirbhay.lkd@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] WARNING: ODEBUG bug in gfs2_fill_super
Date: Thu, 23 Oct 2025 06:24:04 -0700 [thread overview]
Message-ID: <68fa2c74.050a0220.346f24.007c.GAE@google.com> (raw)
In-Reply-To: <CABGqKE2GOzKZYcFnd3uVq7qWvNVqaavKQNy35PYebnKjMh+sXw@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/jfs/jfs_incore.h:86:13: error: type name does not allow function specifier to be specified
fs/jfs/jfs_incore.h:86:20: error: expected member name or ';' after declaration specifiers
fs/jfs/inode.c:55:35: error: expected identifier
Tested on:
commit: efb26a23 Add linux-next specific files for 20251023
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=cc275090905d8fd7
dashboard link: https://syzkaller.appspot.com/bug?extid=19e0be39cc25dfcb0858
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=112e2e7c580000
next parent reply other threads:[~2025-10-23 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABGqKE2GOzKZYcFnd3uVq7qWvNVqaavKQNy35PYebnKjMh+sXw@mail.gmail.com>
2025-10-23 13:24 ` syzbot [this message]
[not found] <CAHc6FU7UNitFFzcLOJKU=NRyX1AN0CBX0vo4mUnFWWdDaatn7Q@mail.gmail.com>
2025-11-16 18:58 ` [syzbot] [gfs2?] WARNING: ODEBUG bug in gfs2_fill_super syzbot
[not found] <CABGqKE0V6YyycVUXMkOK8vQGKeuF1Nq5ddu_RbiTaCBmpxtsQQ@mail.gmail.com>
2025-10-23 19:30 ` syzbot
[not found] <CAHc6FU6i+9iRYc4h5M8B1sABGQMf3ViwyhBoVVyzR9ptD9Zztw@mail.gmail.com>
2025-10-23 0:03 ` syzbot
[not found] <CABGqKE0_8PVTO6HUtCRduxpGK5p_iTFUYrErTfdvZAP6bugT8g@mail.gmail.com>
2025-10-22 5:00 ` syzbot
2025-10-20 21:07 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=68fa2c74.050a0220.346f24.007c.GAE@google.com \
--to=syzbot+19e0be39cc25dfcb0858@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nirbhay.lkd@gmail.com \
--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.