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, nogikh@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
trix@redhat.com
Subject: Re: [syzbot] [modules?] KASAN: invalid-access Read in init_module_from_file
Date: Mon, 14 Aug 2023 05:08:27 -0700 [thread overview]
Message-ID: <00000000000083735b0602e0eb7d@google.com> (raw)
In-Reply-To: <0000000000000e4cc105ff68937b@google.com>
syzbot suspects this issue was fixed by commit:
commit f1962207150c8b602e980616f04b37ea4e64bb9f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jul 4 13:37:32 2023 +0000
module: fix init_module_from_file() error handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17c80763a80000
start commit: 995b406c7e97 Merge tag 'csky-for-linus-6.5' of https://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3f27fb02fc20d955
dashboard link: https://syzkaller.appspot.com/bug?extid=e3705186451a87fd93b8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12219fbf280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1278c8a4a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: module: fix init_module_from_file() error handling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-08-14 12:09 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
2023-08-08 16:06 ` Aleksandr Nogikh
2023-08-14 12:08 ` syzbot [this message]
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=00000000000083735b0602e0eb7d@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=nogikh@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).