From: Karl Mehltretter <kmehltretter@gmail.com>
To: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Marco Elver <elver@google.com>,
Bradley Morgan <include@grrlz.net>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kcov: report the first spurious PC in the interrupt selftest
Date: Sat, 12 Sep 2026 11:28:51 +0200 [thread overview]
Message-ID: <aqUa5t19bDfcGkqP@gmail.com> (raw)
In-Reply-To: <20260724192122.73080-1-kmehltretter@gmail.com>
On Fri, Jul 24, 2026 at 09:21:22PM +0100, Karl Mehltretter wrote:
> Changes in v2:
> - Use kcov_start() and kcov_stop() instead of open-coding their logic.
> - Add decanonicalize_ip() next to canonicalize_ip() and use it when
> reporting the recorded PC.
> - Retest under QEMU on arm64, mips64le, and x86_64.
>
> This patch improves the failure diagnostics.
Friendly ping. Bradley has given his Reviewed-by for this v2.
Thanks,
Karl
prev parent reply other threads:[~2026-09-12 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 19:21 Karl Mehltretter
2026-07-24 19:27 ` Bradley Morgan
2026-09-12 9:28 ` Karl Mehltretter [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=aqUa5t19bDfcGkqP@gmail.com \
--to=kmehltretter@gmail.com \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=include@grrlz.net \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.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®