All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: stable@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	Natanael Copa <ncopa@alpinelinux.org>
Subject: Re: [PATCH 6.6] x86/its: Fix build error for its_static_thunk()
Date: Tue, 20 May 2025 10:48:40 +0200	[thread overview]
Message-ID: <2025052057-prognosis-hush-bf23@gregkh> (raw)
In-Reply-To: <20250519-its-build-fix-6-6-v1-1-225ac41eb447@linux.intel.com>

On Mon, May 19, 2025 at 01:43:42PM -0700, Pawan Gupta wrote:
> Due to a likely merge resolution error of backport commit 772934d9062a
> ("x86/its: FineIBT-paranoid vs ITS"), the function its_static_thunk() was
> placed in the wrong ifdef block, causing a build error when
> CONFIG_MITIGATION_ITS and CONFIG_FINEIBT are both disabled:
> 
>   /linux-6.6/arch/x86/kernel/alternative.c:1452:5: error: redefinition of 'its_static_thunk'
>    1452 | u8 *its_static_thunk(int reg)
>         |     ^~~~~~~~~~~~~~~~
> 
> Fix it by moving its_static_thunk() under CONFIG_MITIGATION_ITS.
> 
> Reported-by: Natanael Copa <ncopa@alpinelinux.org>
> Link: https://lore.kernel.org/all/20250519164717.18738b4e@ncopa-desktop/
> Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> ---
> commit ("x86/its: FineIBT-paranoid vs ITS") was resolved correctly in
> v6.12:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.29&id=7e78061be78b8593df9b0cd0f21b1fee425035de
> 
> Fix is required in v6.6 and v6.1

Thanks for this, now queued up for 6.6.y, but I think 6.1.y is ok, as
this didn't apply there, nor did I get any build reports of problems for
it yet.  So I'll leave that be for now.

greg k-h

  parent reply	other threads:[~2025-05-20  8:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 13:04 [PATCH 6.6 000/113] 6.6.91-rc2 review Greg Kroah-Hartman
2025-05-14 15:34 ` Jon Hunter
2025-05-14 18:34 ` Pavel Machek
2025-05-14 18:59 ` Harshit Mogalapalli
2025-05-14 20:05   ` Greg Kroah-Hartman
2025-05-14 20:33     ` Harshit Mogalapalli
2025-05-14 20:49       ` Guenter Roeck
2025-05-15  5:35         ` Greg Kroah-Hartman
2025-05-15 15:25           ` Pawan Gupta
2025-05-15 15:29             ` Pawan Gupta
2025-05-16  8:03               ` Greg Kroah-Hartman
2025-05-16 20:42                 ` [PATCH 6.1] x86/its: Fix build errors when CONFIG_MODULES=n Pawan Gupta
2025-05-17  6:53                   ` Greg Kroah-Hartman
2025-05-17 13:07                   ` Sasha Levin
2025-05-19 15:27             ` [PATCH 6.6 000/113] 6.6.91-rc2 review Greg Kroah-Hartman
2025-05-19 19:50               ` Pawan Gupta
2025-05-19 20:43                 ` [PATCH 6.6] x86/its: Fix build error for its_static_thunk() Pawan Gupta
2025-05-20  7:52                   ` Sasha Levin
2025-05-20  8:48                   ` Greg Kroah-Hartman [this message]
2025-05-14 20:47     ` [PATCH 6.6 000/113] 6.6.91-rc2 review Guenter Roeck
2025-05-15  5:36       ` Greg Kroah-Hartman
2025-05-15  8:03 ` Mark Brown
2025-05-15  8:10 ` Florian Fainelli
2025-05-15 12:01 ` Naresh Kamboju
2025-05-19 13:49 ` Guenter Roeck

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=2025052057-prognosis-hush-bf23@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=ncopa@alpinelinux.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=stable@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 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.