Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <0000000000000e4cc105ff68937b@google.com> <000000000000166f9e06025c8139@google.com>
In-Reply-To: <000000000000166f9e06025c8139@google.com>
From:   Aleksandr Nogikh <nogikh@google.com>
Date:   Tue, 8 Aug 2023 18:06:20 +0200
Message-ID: <CANp29Y7q49HBoV+_xD1wpztUGDu4ykEFb-2H-d71rZAkY=M67A@mail.gmail.com>
Subject: Re: [syzbot] [modules?] KASAN: invalid-access Read in init_module_from_file
To:     syzbot <syzbot+e3705186451a87fd93b8@syzkaller.appspotmail.com>
Cc:     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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Aug 8, 2023 at 12:09=E2=80=AFAM syzbot
<syzbot+e3705186451a87fd93b8@syzkaller.appspotmail.com> wrote:
>
> 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=3D15c26ba9a8=
0000
> start commit:   a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.k=
e..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=3Df5e1158c5b2f8=
3bb
> dashboard link: https://syzkaller.appspot.com/bug?extid=3De3705186451a87f=
d93b8
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=3D12518548a80=
000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=3D124ccf70a8000=
0
>
> If the result looks correct, please mark the issue as fixed by replying w=
ith:
>
> #syz fix: md/raid10: fix the condition to call bio_end_io_acct()

No, that's unrelated.

Most likely it's due to https://github.com/google/syzkaller/issues/4117
TL;DR: for bugs that only existed for a very short time syzbot is
having problems differentiating between revisions where the bug is not
yet introduced and where it's already fixed.

>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisect=
ion
>