From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+c49e17557ddb5725583d@syzkaller.appspotmail.com>
Cc: andrii@kernel.org, ast@kernel.org, boqun.feng@gmail.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
fgheet255t@gmail.com, haoluo@google.com, hawk@kernel.org,
hdanton@sina.com, john.fastabend@gmail.com, jolsa@kernel.org,
kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
longman@redhat.com, martin.lau@linux.dev, mingo@redhat.com,
netdev@vger.kernel.org, peterz@infradead.org,
rostedt@goodmis.org, sdf@google.com, song@kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
will@kernel.org, yhs@fb.com
Subject: Re: [syzbot] [bpf?] [trace?] possible deadlock in bpf_trace_printk
Date: Thu, 23 Mar 2023 08:50:10 +0100 [thread overview]
Message-ID: <CACT4Y+Z1Vm+ci43qnoZiF89mo_R1eQV0Cd9Y_MUNoXD1FytR2A@mail.gmail.com> (raw)
In-Reply-To: <000000000000690cbc05f779cba8@google.com>
On Wed, 22 Mar 2023 at 10:29, syzbot
<syzbot+c49e17557ddb5725583d@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 05b24ff9b2cfabfcfd951daaa915a036ab53c9e1
> Author: Jiri Olsa <jolsa@kernel.org>
> Date: Fri Sep 16 07:19:14 2022 +0000
>
> bpf: Prevent bpf program recursion for raw tracepoint probes
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a653d6c80000
> start commit: a335366bad13 Merge tag 'gpio-fixes-for-v6.0-rc6' of git://..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=9e66520f224211a2
> dashboard link: https://syzkaller.appspot.com/bug?extid=c49e17557ddb5725583d
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e27480880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12737fbf080000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: bpf: Prevent bpf program recursion for raw tracepoint probes
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Looks reasonable:
#syz fix: bpf: Prevent bpf program recursion for raw tracepoint probes
next prev parent reply other threads:[~2023-03-23 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 17:07 [syzbot] possible deadlock in bpf_trace_printk syzbot
2023-03-22 9:29 ` [syzbot] [bpf?] [trace?] " syzbot
2023-03-23 7:50 ` Dmitry Vyukov [this message]
2023-03-23 11:30 ` Jiri Olsa
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=CACT4Y+Z1Vm+ci43qnoZiF89mo_R1eQV0Cd9Y_MUNoXD1FytR2A@mail.gmail.com \
--to=dvyukov@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=fgheet255t@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=hdanton@sina.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+c49e17557ddb5725583d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@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 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.