All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	 Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H. Peter Anvin" <hpa@zytor.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	 Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>,
	Nikunj A Dadhania <nikunj@amd.com>,
	linux-kernel@vger.kernel.org,  catalin.marinas@arm.com,
	kernel-team@meta.com
Subject: Re: [PATCH] x86/sev: Fix kmemleak false positive for the RMP segment descriptors
Date: Mon, 2 Nov 2026 14:30:39 -0800	[thread overview]
Message-ID: <aukO-_uELcL15JnH@gmail.com> (raw)
In-Reply-To: <036145d8-46b2-4389-afd7-26c897d09ce7@intel.com>

On Mon, Nov 02, 2026 at 12:48:16PM -0800, Dave Hansen wrote:
> On 11/2/26 08:49, Breno Leitao wrote:
> > Register the table with kmemleak, so it is scanned like any other
> > object.
> > 
> > kmemleak_alloc() registers a block of memory with kmemleak, so kmemleak
> > scans it and counts pointers into it, do it with rmp_segment_table.
> 
> Why don't we just kmalloc() the thing?

That would do the work as well, if this is an option.

  reply	other threads:[~2026-11-02 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 16:49 [PATCH] x86/sev: Fix kmemleak false positive for the RMP segment descriptors Breno Leitao
2026-11-02 20:48 ` Dave Hansen
2026-11-02 22:30   ` Breno Leitao [this message]
2026-11-02 22:54     ` Dave Hansen
2026-11-03  9:34       ` Breno Leitao

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=aukO-_uELcL15JnH@gmail.com \
    --to=leitao@debian.org \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=tglx@kernel.org \
    --cc=thomas.lendacky@amd.com \
    --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 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.