From: "Li,Rongqing" <lirongqing@baidu.com>
To: 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" <x86@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH] x86/process: Return early on NULL iobm in native_tss_update_io_bitmap()
Date: Wed, 10 Jun 2026 12:40:01 +0000 [thread overview]
Message-ID: <ee2420cc9a734413814796cd0080da8c@baidu.com> (raw)
In-Reply-To: <20260601053715.2233-1-lirongqing@baidu.com>
> From: Li RongQing <lirongqing@baidu.com>
>
> When 'iobm' is NULL, native_tss_update_io_bitmap() clears the thread flag
> and invalidates the TSS bitmap, but falls through to subsequent code that
> dereferences 'iobm'.
>
> Add a missing return statement to prevent a potential kernel NULL pointer
> dereference panic.
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> arch/x86/kernel/process.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c index
> 4c718f8..d5cd217 100644
> --- a/arch/x86/kernel/process.c
> +++ b/arch/x86/kernel/process.c
> @@ -486,6 +486,7 @@ void native_tss_update_io_bitmap(void)
> if (WARN_ON_ONCE(!iobm)) {
> clear_thread_flag(TIF_IO_BITMAP);
> native_tss_invalidate_io_bitmap();
> + return;
> }
>
Ping
[Li,Rongqing]
> /*
> --
> 2.9.4
next prev parent reply other threads:[~2026-06-10 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 5:37 lirongqing
2026-06-10 12:40 ` Li,Rongqing [this message]
2026-06-12 2:19 ` Sohil Mehta
2026-06-12 3:11 ` 答复: [外部邮件] " Li,Rongqing
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=ee2420cc9a734413814796cd0080da8c@baidu.com \
--to=lirongqing@baidu.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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®