From: syzbot <syzbot+5bdd4953bc58c8fbd6eb@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_iget
Date: Thu, 15 Aug 2024 23:23:02 -0700 [thread overview]
Message-ID: <000000000000d3eb64061fc6fd21@google.com> (raw)
In-Reply-To: <20240816061835.50652-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
./include/linux/buffer_head.h:414:10: error: no member named 'i_state' in 'struct buffer_head'; did you mean 'b_state'?In file included from
./include/linux/buffer_head.h:414:10: error: no member named 'i_state' in 'struct buffer_head'; did you mean 'b_state'?
Tested on:
commit: d07b4328 Merge tag 'for-linus' of git://git.kernel.org..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b
dashboard link: https://syzkaller.appspot.com/bug?extid=5bdd4953bc58c8fbd6eb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12f5e18d980000
next parent reply other threads:[~2024-08-16 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240816061835.50652-1-lizhi.xu@windriver.com>
2024-08-16 6:23 ` syzbot [this message]
[not found] <20251022150431.jNFth%dmantipov@yandex.ru>
2025-10-22 19:35 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_iget syzbot
[not found] <20240816091139.3070635-1-lizhi.xu@windriver.com>
2024-08-16 9:33 ` syzbot
[not found] <20240816080852.2626448-1-lizhi.xu@windriver.com>
2024-08-16 8:23 ` syzbot
[not found] <20240816072319.3047417-1-lizhi.xu@windriver.com>
2024-08-16 7:45 ` syzbot
[not found] <20240816065432.733582-1-lizhi.xu@windriver.com>
2024-08-16 7:16 ` syzbot
[not found] <20240816054904.4016904-1-lizhi.xu@windriver.com>
2024-08-16 6:06 ` syzbot
[not found] <20240816032623.3023693-1-lizhi.xu@windriver.com>
2024-08-16 3:41 ` syzbot
2024-08-15 10:47 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=000000000000d3eb64061fc6fd21@google.com \
--to=syzbot+5bdd4953bc58c8fbd6eb@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox