From: Peter Zijlstra <peterz@infradead.org>
To: syzbot <syzbot+7692cea7450c97fa2a0a@syzkaller.appspotmail.com>
Cc: acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, andrii@kernel.org,
ast@kernel.org, bpf@vger.kernel.org, cobranza@ingcoecuador.com,
daniel@iogearbox.net, eranian@google.com,
john.fastabend@gmail.com, jolsa@redhat.com, kafai@fb.com,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, mingo@kernel.org, mingo@redhat.com,
namhyung@kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, torvalds@linux-foundation.org,
vincent.weaver@maine.edu, yhs@fb.com
Subject: Re: [syzbot] INFO: task hung in perf_event_free_task
Date: Wed, 21 Apr 2021 11:29:38 +0200 [thread overview]
Message-ID: <YH/wggx86Ph1bwPi@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <000000000000dfe1bc05c063d0fa@google.com>
On Tue, Apr 20, 2021 at 02:10:22AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 7af08140 Revert "gcov: clang: fix clang-11+ build"
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15416871d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c0a6882014fd3d45
> dashboard link: https://syzkaller.appspot.com/bug?extid=7692cea7450c97fa2a0a
> compiler: Debian clang version 11.0.1-2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145c9ffed00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12de31ded00000
When I build that C file and run it, it completes. AFAICT that's not the
expected outcome given we're looking for a hung-task scenario. Hmm?
next prev parent reply other threads:[~2021-04-21 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 19:18 syzbot
2019-07-30 18:44 ` syzbot
2021-04-20 9:10 ` [syzbot] " syzbot
2021-04-21 9:29 ` Peter Zijlstra [this message]
2021-04-21 12:26 ` Dmitry Vyukov
2021-04-21 12:35 ` Dmitry Vyukov
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=YH/wggx86Ph1bwPi@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cobranza@ingcoecuador.com \
--cc=daniel@iogearbox.net \
--cc=eranian@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+7692cea7450c97fa2a0a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
--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
Powered by JetHome