From: syzbot <syzbot+4da3ff23081bafe74fc2@syzkaller.appspotmail.com>
To: andrii.nakryiko@gmail.com, ast@kernel.org, bcrl@kvack.org,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
hawk@kernel.org, jakub.kicinski@netronome.com,
john.fastabend@gmail.com, kafai@fb.com, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
viro@zeniv.linux.org.uk, xdp-newbies@vger.kernel.org, yhs@fb.com
Subject: Re: WARNING in __mark_chain_precision
Date: Mon, 08 Jul 2019 21:08:00 -0700 [thread overview]
Message-ID: <000000000000d676f2058d37b4a9@google.com> (raw)
In-Reply-To: <CAEf4BzZfqnFZRbDVo1-=Vph=NpOm1g=wGuV_O5Cniuxj9f9CsQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+4da3ff23081bafe74fc2@syzkaller.appspotmail.com
Tested on:
commit: b9321614 bpf: fix precision bit propagation for BPF_ST ins..
git tree: https://github.com/anakryiko/linux bpf-fix-precise-bpf_st
kernel config: https://syzkaller.appspot.com/x/.config?x=6bb3e6e7997c14f9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-07-09 4:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:27 WARNING in __mark_chain_precision syzbot
2019-07-09 3:49 ` Andrii Nakryiko
2019-07-09 4:08 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-19 7:50 Hao Sun
2022-12-19 19:13 ` sdf
2022-12-21 0:30 ` Andrii Nakryiko
2022-12-28 5:23 ` Yonghong Song
2022-12-29 22:16 ` Andrii Nakryiko
2022-12-30 9:44 ` Hao Sun
2023-01-01 19:19 ` Yonghong Song
2023-01-02 9:42 ` Hao Sun
2023-01-03 18:27 ` Alexei Starovoitov
2023-01-04 5:47 ` Yonghong Song
2023-01-04 8:52 ` Hao Sun
2023-01-04 16:51 ` Yonghong Song
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=000000000000d676f2058d37b4a9@google.com \
--to=syzbot+4da3ff23081bafe74fc2@syzkaller.appspotmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bcrl@kvack.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xdp-newbies@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox