From: syzbot <syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit
Date: Sun, 23 Mar 2025 18:21:02 -0700 [thread overview]
Message-ID: <67e0b37e.050a0220.a7ebc.0008.GAE@google.com> (raw)
In-Reply-To: <20250324010140.2046646-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/ocfs2/quota_local.c:313:19: error: use of undeclared identifier 'bit'
Tested on:
commit: 586de923 Merge tag 'i2c-for-6.14-rc8' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1d4644c4063c5098
dashboard link: https://syzkaller.appspot.com/bug?extid=7ea0b96c4ddb49fd1a70
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15f7f3b0580000
next parent reply other threads:[~2025-03-24 1:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250324010140.2046646-1-lizhi.xu@windriver.com>
2025-03-24 1:21 ` syzbot [this message]
[not found] <177644287136.3789634.17252147648817406714@talencesecurity.com>
2026-04-17 19:43 ` syzbot
[not found] <20260417101223.2490735-1-tristmd@gmail.com>
2026-04-17 12:37 ` syzbot
[not found] <20250326032012.83642-1-richard120310@gmail.com>
2025-03-26 4:15 ` syzbot
[not found] <20250324013855.2122966-1-lizhi.xu@windriver.com>
2025-03-24 2:23 ` syzbot
2025-03-21 20:52 syzbot
2025-03-22 1:40 ` Edward Adam Davis
2025-03-22 6:02 ` syzbot
2025-03-22 8:41 ` Edward Adam Davis
2025-03-22 9:05 ` syzbot
2025-03-23 2:36 ` Edward Adam Davis
2025-03-23 9:52 ` syzbot
2025-03-23 10:17 ` Edward Adam Davis
2025-03-23 10:43 ` syzbot
2025-03-26 1:23 ` I Hsin Cheng
2025-03-26 1:59 ` syzbot
2025-03-26 2:19 ` I Hsin Cheng
2025-03-26 2:43 ` syzbot
2025-03-26 3:04 ` I Hsin Cheng
2025-03-26 3:58 ` 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=67e0b37e.050a0220.a7ebc.0008.GAE@google.com \
--to=syzbot+7ea0b96c4ddb49fd1a70@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
Powered by JetHome