From: "Chen, Yu C" <yu.c.chen@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Chen Yu <yu.chen.surf@foxmail.com>,
"Govindarajulu, Hariganesh" <hariganesh.govindarajulu@intel.com>
Subject: Re: [PATCH] ACPI: pfr_update: Fix the driver update version check
Date: Tue, 22 Jul 2025 23:27:38 +0800 [thread overview]
Message-ID: <b3c72614-3d96-486a-90f7-dc1f817ab700@intel.com> (raw)
In-Reply-To: <CAJZ5v0hskeS3fKU3OPow=i8Nh4NojsUrJJrW=oNJAb7tP9P6=g@mail.gmail.com>
Hi Rafael,
thank you for taking a look,
On 7/22/2025 11:03 PM, Rafael J. Wysocki wrote:
> On Tue, Jul 22, 2025 at 4:39 PM Chen Yu <yu.c.chen@intel.com> wrote:
>>
>> The security-version-number check should be used rather
>> than the runtime version check for driver update. Otherwise
>> the firmware update would fail when the update binary
>> has a lower number of the runtime version than the
>> current one.
>>
>> Reported-by: "Govindarajulu, Hariganesh" <hariganesh.govindarajulu@intel.com>
>> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>
> A Fixes: tag, please?
>
OK,
Fixes: commit 0db89fa243e5 ("ACPI: Introduce Platform Firmware Runtime
Update device driver")
> Also, this is unlikely to get into 6.17-rc1, but I can make it into
> 6.17-rc2 if it is urgent enough, so how urgent is it?
>
It is not urgent because the internal tree has merged this patch and did
not block
the testing. However, considering that this might prevent users from
rolling back
versions in the production environment, fixing it earlier might be helpful.
thanks,
Chenyu
>> ---
>> drivers/acpi/pfr_update.c | 2 +-
>> include/uapi/linux/pfrut.h | 1 +
>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/pfr_update.c b/drivers/acpi/pfr_update.c
>> index 031d1ba81b86..08b9b2bc2d97 100644
>> --- a/drivers/acpi/pfr_update.c
>> +++ b/drivers/acpi/pfr_update.c
>> @@ -310,7 +310,7 @@ static bool applicable_image(const void *data, struct pfru_update_cap_info *cap,
>> if (type == PFRU_CODE_INJECT_TYPE)
>> return payload_hdr->rt_ver >= cap->code_rt_version;
>>
>> - return payload_hdr->rt_ver >= cap->drv_rt_version;
>> + return payload_hdr->svn_ver >= cap->drv_svn;
>> }
>>
>> static void print_update_debug_info(struct pfru_updated_result *result,
>> diff --git a/include/uapi/linux/pfrut.h b/include/uapi/linux/pfrut.h
>> index 42fa15f8310d..b77d5c210c26 100644
>> --- a/include/uapi/linux/pfrut.h
>> +++ b/include/uapi/linux/pfrut.h
>> @@ -89,6 +89,7 @@ struct pfru_payload_hdr {
>> __u32 hw_ver;
>> __u32 rt_ver;
>> __u8 platform_id[16];
>> + __u32 svn_ver;
>> };
>>
>> enum pfru_dsm_status {
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2025-07-22 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:32 [PATCH] ACPI: pfr_update: Fix the driver update version check Chen Yu
2025-07-22 15:03 ` Rafael J. Wysocki
2025-07-22 15:27 ` Chen, Yu C [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=b3c72614-3d96-486a-90f7-dc1f817ab700@intel.com \
--to=yu.c.chen@intel.com \
--cc=hariganesh.govindarajulu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yu.chen.surf@foxmail.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