From: Vasant Hegde <vasant.hegde@amd.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
iommu@lists.linux.dev, Joerg Roedel <jroedel@suse.de>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Kees Cook <keescook@chromium.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hardening: x86: drop reference to removed config AMD_IOMMU_V2
Date: Thu, 12 Oct 2023 12:27:57 +0530 [thread overview]
Message-ID: <c90f5226-8a55-9a04-765d-104e54484d6b@amd.com> (raw)
In-Reply-To: <b9f08b19-80e9-4908-89f1-8712bb3b59e8@kadam.mountain>
On 10/12/2023 12:05 PM, Dan Carpenter wrote:
> On Thu, Oct 12, 2023 at 10:45:03AM +0530, Vasant Hegde wrote:
>>
>>
>> On 10/12/2023 10:20 AM, Lukas Bulwahn wrote:
>>> Commit 5a0b11a180a9 ("iommu/amd: Remove iommu_v2 module") removes the
>>> config AMD_IOMMU_V2.
>>>
>>> Remove the reference to this config in the x86 architecture-specific
>>> hardening config fragment as well.
>>>
>>> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>>> ---
>>> Joerg, please pick this patch on top of the commit above. Thanks.
>>>
>>> arch/x86/configs/hardening.config | 1 -
>>
>> Thanks for the fix Lukas. But I don't see this file in upstream linux tree. Am I
>> missing something?
>>
>
> It was added on Aug 24 in linux-next.
Thanks Dan. I can see the patch in linux-next.
Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>
-Vasant
next prev parent reply other threads:[~2023-10-12 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 4:50 Lukas Bulwahn
2023-10-12 5:15 ` Vasant Hegde
2023-10-12 6:35 ` Dan Carpenter
2023-10-12 6:57 ` Vasant Hegde [this message]
2023-10-12 16:10 ` Kees Cook
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=c90f5226-8a55-9a04-765d-104e54484d6b@amd.com \
--to=vasant.hegde@amd.com \
--cc=dan.carpenter@linaro.org \
--cc=gustavoars@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jroedel@suse.de \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=suravee.suthikulpanit@amd.com \
/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®