From: Nikolay Borisov <nik.borisov@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86/microcode/AMD: Make __verify_patch_size() return bool
Date: Thu, 14 Nov 2024 16:40:50 +0200 [thread overview]
Message-ID: <3cc87528-e7a9-4dc0-800b-bb8f0cf279cd@suse.com> (raw)
In-Reply-To: <20241114142652.GGZzYIrHJUVoE18vp4@fat_crate.local>
On 14.11.24 г. 16:26 ч., Borislav Petkov wrote:
> On Thu, Nov 14, 2024 at 04:13:33PM +0200, Nikolay Borisov wrote:
>>> if (sh_psize != max_size)
>>> return false;
>>
>> Isn't sh_psize < max_size valid here?
>
> * sh_psize < min_t(u32, buf_size, max_size) == max_size -- ditto.
>
> This is still some sort of a mismatch which we'd rather fail.
>
> That max_size should probably be called patch_size or so.
>
> IOW, if the patch size in the header doesn't match the per-family patch size
> => fail.
Right, the important bit here is that max_size is not really max_size
but, as you say, patch_size so for those families it's expected to have
an exact size.
With max_size I perceive it would imply that the current patch can be
_at most_ max_size, but might as well be smaller.
>
next prev parent reply other threads:[~2024-11-14 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:51 [PATCH 0/3] Minor cleanups in AMD microcode loader Nikolay Borisov
2024-10-18 15:51 ` [PATCH 1/3] x86/microcode/AMD: Return bool from find_blobs_in_containers() Nikolay Borisov
2024-11-14 10:16 ` Borislav Petkov
2025-01-01 12:14 ` [tip: x86/microcode] " tip-bot2 for Nikolay Borisov
2024-10-18 15:51 ` [PATCH 2/3] x86/microcode/AMD: Make __verify_patch_size() return bool Nikolay Borisov
2024-11-14 12:58 ` Borislav Petkov
2024-11-14 13:19 ` Nikolay Borisov
2024-11-14 14:01 ` Borislav Petkov
2024-11-14 14:13 ` Nikolay Borisov
2024-11-14 14:26 ` Borislav Petkov
2024-11-14 14:40 ` Nikolay Borisov [this message]
2024-11-14 15:47 ` Borislav Petkov
2024-11-15 16:43 ` Borislav Petkov
2025-01-01 12:14 ` [tip: x86/microcode] " tip-bot2 for Nikolay Borisov
2024-10-18 15:51 ` [PATCH 3/3] x86/microcode/AMD: Remove bogus comment from parse_container() Nikolay Borisov
2025-01-01 12:14 ` [tip: x86/microcode] " tip-bot2 for Nikolay Borisov
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=3cc87528-e7a9-4dc0-800b-bb8f0cf279cd@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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®