From: Sohil Mehta <sohil.mehta@intel.com>
To: Hou Tao <houtao@huaweicloud.com>, <x86@kernel.org>,
<bpf@vger.kernel.org>
Cc: 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>, <linux-kernel@vger.kernel.org>,
xingwei lee <xrivendell7@gmail.com>,
"Jann Horn" <jannh@google.com>,
Yonghong Song <yonghong.song@linux.dev>, <houtao1@huawei.com>
Subject: Re: [PATCH bpf v2 1/3] x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h
Date: Mon, 29 Jan 2024 15:56:29 -0800 [thread overview]
Message-ID: <76af5d2e-7598-42b4-9ed9-8fec25ece057@intel.com> (raw)
In-Reply-To: <20240126115423.3943360-2-houtao@huaweicloud.com>
On 1/26/2024 3:54 AM, Hou Tao wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Moving is_vsyscall_vaddr() into asm/vsyscall.h to make it available for
s/Moving/Move
> copy_from_kernel_nofault_allowed() in arch/x86/mm/maccess.c.
>
> Signed-off-by: Hou Tao <houtao1@huawei.com>
> ---
> arch/x86/include/asm/vsyscall.h | 10 ++++++++++
> arch/x86/mm/fault.c | 9 ---------
> 2 files changed, 10 insertions(+), 9 deletions(-)
>
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
next prev parent reply other threads:[~2024-01-29 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 11:54 [PATCH bpf v2 0/3] Fix the read of vsyscall page through bpf Hou Tao
2024-01-26 11:54 ` [PATCH bpf v2 1/3] x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h Hou Tao
2024-01-29 23:56 ` Sohil Mehta [this message]
2024-01-30 4:20 ` Hou Tao
2024-01-26 11:54 ` [PATCH bpf v2 2/3] x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault() Hou Tao
2024-01-29 23:50 ` Sohil Mehta
2024-01-30 4:18 ` Hou Tao
2024-01-26 11:54 ` [PATCH bpf v2 3/3] selftest/bpf: Test the read of vsyscall page under x86-64 Hou Tao
2024-01-26 19:36 ` Yonghong Song
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=76af5d2e-7598-42b4-9ed9-8fec25ece057@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xrivendell7@gmail.com \
--cc=yonghong.song@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).