From: Dave Hansen <dave.hansen@intel.com>
To: Balbir Singh <balbirs@nvidia.com>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
apopple@nvidia.com, jhubbard@nvidia.com, jgg@nvidia.com,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Kees Cook <kees@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2] x86/kaslr: Revisit entropy when CONFIG_PCI_P2PDMA is enabled
Date: Thu, 6 Feb 2025 16:27:04 -0800 [thread overview]
Message-ID: <76d970d7-e183-4c7b-addd-3b00fa39f9b6@intel.com> (raw)
In-Reply-To: <20250206234234.1912585-1-balbirs@nvidia.com>
On 2/6/25 15:42, Balbir Singh wrote:
> Fix this by not shrinking the size of direct map when CONFIG_PCI_P2PDMA
> is enabled. This reduces the total available entropy, but it's
> better than the current work around of having to disable KASLR
> completely.
Is the size of these P2PDMA mappings known up front? Or do you just need
them to be as large as possible?
next prev parent reply other threads:[~2025-02-07 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 23:42 [PATCH v2] x86/kaslr: Revisit entropy when CONFIG_PCI_P2PDMA is enabled Balbir Singh
2025-02-07 0:27 ` Dave Hansen [this message]
2025-02-07 1:39 ` Balbir Singh
2025-02-07 1:00 ` Kees Cook
2025-02-19 1:11 ` Balbir Singh
2025-02-21 22:43 ` Bjorn Helgaas
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=76d970d7-e183-4c7b-addd-3b00fa39f9b6@intel.com \
--to=dave.hansen@intel.com \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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