From: syzbot <syzbot+5702f46b5b22bdb38b7e@syzkaller.appspotmail.com> To: alex@ghiti.fr, andrii@kernel.org, aou@eecs.berkeley.edu, ast@kernel.org, bjorn@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net, dvyukov@google.com, haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, luke.r.nels@gmail.com, martin.lau@linux.dev, palmer@dabbelt.com, paul.walmsley@sifive.com, sdf@google.com, song@kernel.org, syzkaller-bugs@googlegroups.com, xi.wang@gmail.com, yhs@fb.com Subject: Re: [syzbot] riscv/fixes boot error: WARNING in __apply_to_page_range (2) Date: Tue, 18 Apr 2023 06:15:42 -0700 [thread overview] Message-ID: <000000000000c3f07505f99c1a97@google.com> (raw) In-Reply-To: <000000000000ea7a5c05f051fd00@google.com> This bug is marked as fixed by commit: riscv: Rework kasan population functions But I can't find it in the tested trees[1] for more than 90 days. Is it a correct commit? Please update it by replying: #syz fix: exact-commit-title Until then the bug is still considered open and new crashes with the same signature are ignored. Kernel: Linux Dashboard link: https://syzkaller.appspot.com/bug?extid=5702f46b5b22bdb38b7e --- [1] I expect the commit to be present in: 1. for-kernelci branch of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 2. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git 3. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 4. main branch of git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git The full list of 10 trees can be found at https://syzkaller.appspot.com/upstream/repos
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+5702f46b5b22bdb38b7e@syzkaller.appspotmail.com> To: alex@ghiti.fr, andrii@kernel.org, aou@eecs.berkeley.edu, ast@kernel.org, bjorn@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net, dvyukov@google.com, haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, luke.r.nels@gmail.com, martin.lau@linux.dev, palmer@dabbelt.com, paul.walmsley@sifive.com, sdf@google.com, song@kernel.org, syzkaller-bugs@googlegroups.com, xi.wang@gmail.com, yhs@fb.com Subject: Re: [syzbot] riscv/fixes boot error: WARNING in __apply_to_page_range (2) Date: Tue, 18 Apr 2023 06:15:42 -0700 [thread overview] Message-ID: <000000000000c3f07505f99c1a97@google.com> (raw) In-Reply-To: <000000000000ea7a5c05f051fd00@google.com> This bug is marked as fixed by commit: riscv: Rework kasan population functions But I can't find it in the tested trees[1] for more than 90 days. Is it a correct commit? Please update it by replying: #syz fix: exact-commit-title Until then the bug is still considered open and new crashes with the same signature are ignored. Kernel: Linux Dashboard link: https://syzkaller.appspot.com/bug?extid=5702f46b5b22bdb38b7e --- [1] I expect the commit to be present in: 1. for-kernelci branch of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 2. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git 3. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 4. main branch of git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git The full list of 10 trees can be found at https://syzkaller.appspot.com/upstream/repos _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-04-18 13:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-21 8:03 [syzbot] riscv/fixes boot error: WARNING in __apply_to_page_range (2) syzbot 2022-12-21 8:03 ` syzbot 2022-12-21 12:48 ` Alexandre Ghiti 2022-12-21 12:48 ` Alexandre Ghiti [not found] ` <07f9fa58-097f-f14e-b07a-c94deed898eb@ghiti.fr> 2022-12-21 13:13 ` Dmitry Vyukov 2022-12-21 13:13 ` Dmitry Vyukov 2023-03-21 13:14 ` syzbot 2023-03-21 13:14 ` syzbot 2023-04-04 13:15 ` syzbot 2023-04-04 13:15 ` syzbot 2023-04-18 13:15 ` syzbot [this message] 2023-04-18 13:15 ` 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=000000000000c3f07505f99c1a97@google.com \ --to=syzbot+5702f46b5b22bdb38b7e@syzkaller.appspotmail.com \ --cc=alex@ghiti.fr \ --cc=andrii@kernel.org \ --cc=aou@eecs.berkeley.edu \ --cc=ast@kernel.org \ --cc=bjorn@kernel.org \ --cc=bpf@vger.kernel.org \ --cc=daniel@iogearbox.net \ --cc=dvyukov@google.com \ --cc=haoluo@google.com \ --cc=john.fastabend@gmail.com \ --cc=jolsa@kernel.org \ --cc=kpsingh@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=luke.r.nels@gmail.com \ --cc=martin.lau@linux.dev \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=sdf@google.com \ --cc=song@kernel.org \ --cc=syzkaller-bugs@googlegroups.com \ --cc=xi.wang@gmail.com \ --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: linkBe 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.