From: syzbot <syzbot+59af7bf76d795311da8c@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, haoluo@google.com,
hawk@kernel.org, john.fastabend@gmail.com, jolsa@kernel.org,
keescook@chromium.org, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
martin.lau@linux.dev, nathan@kernel.org, ndesaulniers@google.com,
netdev@vger.kernel.org, sdf@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
v4bel@theori.io, yhs@fb.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Write in copy_verifier_state
Date: Mon, 06 Feb 2023 12:31:17 -0800 [thread overview]
Message-ID: <000000000000ce7ebf05f40de992@google.com> (raw)
In-Reply-To: <000000000000269f9a05f02be9d8@google.com>
syzbot suspects this issue was fixed by commit:
commit 45435d8da71f9f3e6860e6e6ea9667b6ec17ec64
Author: Kees Cook <keescook@chromium.org>
Date: Fri Dec 23 18:28:44 2022 +0000
bpf: Always use maximal size for copy_array()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14c62f23480000
start commit: 041fae9c105a Merge tag 'f2fs-for-6.2-rc1' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e2f3d9d232a3cac5
dashboard link: https://syzkaller.appspot.com/bug?extid=59af7bf76d795311da8c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1650d477880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1305f993880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: Always use maximal size for copy_array()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-02-06 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:37 [syzbot] KASAN: slab-out-of-bounds Write in copy_verifier_state syzbot
2022-12-20 19:53 ` sdf
2022-12-20 19:53 ` syzbot
2022-12-20 19:57 ` sdf
2022-12-20 20:30 ` syzbot
2023-02-06 20:31 ` syzbot [this message]
2023-02-07 10:27 ` Aleksandr Nogikh
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=000000000000ce7ebf05f40de992@google.com \
--to=syzbot+59af7bf76d795311da8c@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=v4bel@theori.io \
--cc=yhs@fb.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.