All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: vineash <vineash30640@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf/x86: Don't WARN when the ext_regs_buf allocation fails
Date: Tue, 13 Oct 2026 08:23:45 +0000	[thread overview]
Message-ID: <sashiko-outbox-169241@kernel.org> (raw)
In-Reply-To: <179187920064.3441876.15687522011658301558@gmail.com>

> reserve_ext_regs_buffers() wraps the per-CPU ext_regs_buf allocation in
> WARN_ON_ONCE(). The allocator already prints a warning with a stack dump
> when a GFP_KERNEL allocation fails, so the WARN only repeats it, which
> Documentation/process/coding-style.rst asks not to do. The failure is
> also handled: the buffers are freed again, the event is still created,
> and events that ask for SIMD or extended register sampling are rejected
> with -ENOMEM in x86_pmu_hw_config() and event_simd_regs_validate().
> 
> syzkaller hit this with fault injection on next-20261002. The trigger
> is a plain hardware cycles event opened while no other x86 PMU event
> exists, with the allocation failed:
> 
>   !per_cpu(ext_regs_buf, cpu)
>   WARNING: arch/x86/events/core.c:441 at reserve_ext_regs_buffers arch/x86/events/core.c:441 [inline]
>   WARNING: arch/x86/events/core.c:441 at x86_reserve_hardware+0x6ff/0x880 arch/x86/events/core.c:458
> [ ... ]
> warning.
> 
> Fixes: b84c96283684 ("perf/x86: Enable XMM register sampling for non-PEBS events")
> Assisted-by: Claude:claude-opus-5-5 syzkaller
> Signed-off-by: vineash <vineash30640@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/179187920064.3441876.15687522011658301558@gmail.com?part=1


      reply	other threads:[~2026-10-13  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  8:13 [PATCH] perf/x86: Don't WARN when the ext_regs_buf allocation fails vineash
2026-10-13  8:23 ` sashiko-bot [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=sashiko-outbox-169241@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vineash30640@gmail.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.