From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Potapenko <glider@google.com>
Cc: Sanan Hasanov <sanan.hasanov@knights.ucf.edu>,
"mingo@redhat.com" <mingo@redhat.com>,
"will@kernel.org" <will@kernel.org>,
"longman@redhat.com" <longman@redhat.com>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"contact@pgazz.com" <contact@pgazz.com>,
Paul Gazzillo <Paul.Gazzillo@ucf.edu>,
"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>
Subject: Re: Syzkaller found a bug: KASAN: use-after-free Write in put_pmu_ctx
Date: Thu, 22 Dec 2022 21:19:53 +0100 [thread overview]
Message-ID: <Y6S76ZqA/CX8Vx82@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAG_fn=UZcDSqnD6+CezbdaekXqejRKm-W8V6ZHxQ+GGUwb3YdA@mail.gmail.com>
On Thu, Dec 22, 2022 at 07:11:38PM +0100, Alexander Potapenko wrote:
> On Thu, Dec 22, 2022 at 6:40 PM Sanan Hasanov
> <sanan.hasanov@knights.ucf.edu> wrote:
> >
> > Good day, dear maintainers,
>
> Hi Sanan,
>
> > Config file: https://drive.google.com/file/d/1JutR21cgcf28flJVyLqDniNyrExMsSn_/view?usp=sharing
> >
> > Reproducer file: https://drive.google.com/file/d/1X31x8w4ULrtP_YnkD7_RCyW7FlwGewMR/view?usp=sharing
>
> Any chance you can build with debug info enabled (CONFIG_DEBUG_INFO=y)?
> Then you'll be able to generate file:line information for the report
> (probably your syzkaller instance will do that for you, otherwise you
> can always use scripts/decode_stacktrace.sh)
Ok use Google before posting....
https://lkml.kernel.org/r/000000000000a20a2e05f029c577@google.com
prev parent reply other threads:[~2022-12-22 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 17:40 Sanan Hasanov
2022-12-22 18:11 ` Alexander Potapenko
2022-12-22 20:19 ` Peter Zijlstra [this message]
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=Y6S76ZqA/CX8Vx82@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Paul.Gazzillo@ucf.edu \
--cc=boqun.feng@gmail.com \
--cc=contact@pgazz.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=sanan.hasanov@knights.ucf.edu \
--cc=syzkaller@googlegroups.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®