From: syzbot <syzbot+e3705186451a87fd93b8@syzkaller.appspotmail.com>
To: bpf@vger.kernel.org, chris@chrisdown.name, linan122@huawei.com,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
llvm@lists.linux.dev, mcgrof@kernel.org, nathan@kernel.org,
ndesaulniers@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, trix@redhat.com
Subject: Re: [syzbot] [modules?] KASAN: invalid-access Read in init_module_from_file
Date: Mon, 07 Aug 2023 15:09:46 -0700 [thread overview]
Message-ID: <000000000000166f9e06025c8139@google.com> (raw)
In-Reply-To: <0000000000000e4cc105ff68937b@google.com>
syzbot suspects this issue was fixed by commit:
commit 125bfc7cd750e68c99f1d446e2c22abea08c237f
Author: Li Nan <linan122@huawei.com>
Date: Fri Jun 9 09:43:20 2023 +0000
md/raid10: fix the condition to call bio_end_io_acct()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15c26ba9a80000
start commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f5e1158c5b2f83bb
dashboard link: https://syzkaller.appspot.com/bug?extid=e3705186451a87fd93b8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12518548a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124ccf70a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: md/raid10: fix the condition to call bio_end_io_acct()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-07 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 8:18 [syzbot] [modules?] KASAN: invalid-access Read in init_module_from_file syzbot
2023-07-24 19:44 ` Luis Chamberlain
2023-07-24 19:56 ` syzbot
2023-07-24 20:31 ` Luis Chamberlain
2023-07-24 21:18 ` syzbot
2023-08-07 22:09 ` syzbot [this message]
2023-08-08 16:06 ` Aleksandr Nogikh
2023-08-14 12:08 ` 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=000000000000166f9e06025c8139@google.com \
--to=syzbot+e3705186451a87fd93b8@syzkaller.appspotmail.com \
--cc=bpf@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=linan122@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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.