mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, bp@alien8.de,
	dan.j.williams@intel.com, dave.hansen@linux.intel.com,
	jane.chu@oracle.com, osalvador@suse.de, tglx@linutronix.de
Subject: Re: [PATCH 0/4] Remove problematic include in <asm/set_memory.h>
Date: Tue, 10 Dec 2024 20:57:25 +0100	[thread overview]
Message-ID: <5bec0778-3b70-41bb-b1b3-a7559cf88dd4@redhat.com> (raw)
In-Reply-To: <20241210184610.2080727-1-kevin.brodsky@arm.com>

On 10.12.24 19:46, Kevin Brodsky wrote:
> The need for this series arose from a completely unrelated series [1].
> Long story short, that series causes <linux/mm.h> to include
> <linux/set_memory.h>, which doesn't feel too unreasonable.
> 
> That works fine on arm64 and probably most other architectures, but not
> on x86 [2]: <asm/set_memory.h> itself includes <linux/mm.h>, creating a
> circular dependency.
> 
> set_memory.h doesn't really need <linux/mm.h>, so removing that include
> seems like the right thing to do. That turned out to be a little more
> involved than expected, hence this series:
> 
> * Patch 1-2 ensure that code doesn't rely on <asm/set_memory.h>
>    including <linux/mm.h>. The errors that these patches fix are included
>    at the end of this email.
> 
> * Patch 3 removes an unused function whose declaration relied on
>    <linux/mm.h> being included.
>   
> * Patch 4 actually remove the include.
> 
> I've build-tested this series with x86_64_defconfig and allyesconfig.
> 
> - Kevin
> 
> [1] https://lore.kernel.org/linux-hardening/20241206101110.1646108-1-kevin.brodsky@arm.com/
> [2] https://lore.kernel.org/oe-kbuild-all/202412062006.C23V9ESs-lkp@intel.com/
> 
> Cc: bp@alien8.de
> Cc: dan.j.williams@intel.com
> Cc: dave.hansen@linux.intel.com
> Cc: david@redhat.com
> Cc: jane.chu@oracle.com
> Cc: osalvador@suse.de
> Cc: tglx@linutronix.de
> ---

LGTM

Acked-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb


  parent reply	other threads:[~2024-12-10 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 18:46 Kevin Brodsky
2024-12-10 18:46 ` [PATCH 1/4] x86/smp: Explicitly include <linux/thread_info.h> Kevin Brodsky
2024-12-10 21:36   ` Borislav Petkov
2024-12-11  8:06     ` Kevin Brodsky
2024-12-10 18:46 ` [PATCH 2/4] x86/sev: Explicitly include <linux/mm.h> Kevin Brodsky
2024-12-10 18:46 ` [PATCH 3/4] x86/mm: Remove unused __set_memory_prot() Kevin Brodsky
2024-12-10 18:46 ` [PATCH 4/4] x86/mm: Remove unnecessary include in set_memory.h Kevin Brodsky
2024-12-10 19:57 ` David Hildenbrand [this message]
2024-12-11  5:04 ` [PATCH 0/4] Remove problematic include in <asm/set_memory.h> Christoph Hellwig
2024-12-11  8:14   ` Kevin Brodsky
2024-12-12  5:46     ` Christoph Hellwig

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=5bec0778-3b70-41bb-b1b3-a7559cf88dd4@redhat.com \
    --to=david@redhat.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jane.chu@oracle.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osalvador@suse.de \
    --cc=tglx@linutronix.de \
    --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®