The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chad Aldreda <ca@modelmiser.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>, Chen Yu <yu.c.chen@intel.com>,
	Shuangpeng Bai <shuangpeng.kernel@gmail.com>,
	linux-acpi@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ACPI: pfr_telemetry: keep the state until the last file is closed
Date: Mon, 16 Nov 2026 20:09:43 +0000	[thread overview]
Message-ID: <20261116200935.2464922-2-ca@modelmiser.com> (raw)
In-Reply-To: <CAJZ5v0jTHbr2KD3PXMdcOCs+QUrGrjGGuxOH7cbOe4kEF77d-A@mail.gmail.com>

On Fri, 13 Nov 2026, Rafael J. Wysocki wrote:
> Applied as 7.5 material, thanks!

Thanks. Two small things in the applied commits, in case they are
still easy to change:

1. Shuangpeng Bai reported the pfr_telemetry use-after-free in June. I
   posted the tags on v1, but v2 did not carry them, so e788ea48810f
   has none:

Reported-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
Closes: https://lore.kernel.org/all/178144969601.60470.3508974301899957212@gmail.com/

2. The message of dacb7cef6f32 ("ACPI: pfr_update: keep the state until
   the last file is closed") also contains my notes from below the ---
   line and the diffstat. Two sentences there no longer match the
   commit: "kzalloc() rather than kzalloc_obj() ... for the stable
   trees" (the code uses kzalloc_obj()), and "No lock is added. A call
   that passed the removed check can run during the unbind ..." (fixed
   by c0ab3714e87a). Deleting everything after your second [ rjw: ]
   line up to the patch.msgid.link Link: tag would drop them.

If neither is worth a rebase, no problem.

Chad

This reply was drafted with an AI assistant (Claude Opus 5.5).


      reply	other threads:[~2026-11-16 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 14:44 [PATCH v2] ACPI: pfr_telemetry: keep the state until the last file is closed Chad Aldreda
2026-11-13 17:58 ` Rafael J. Wysocki (Intel)
2026-11-16 20:09   ` Chad Aldreda [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=20261116200935.2464922-2-ca@modelmiser.com \
    --to=ca@modelmiser.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=shuangpeng.kernel@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=yu.c.chen@intel.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