From: "Li,Rongqing" <lirongqing@baidu.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
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: 答复: [外部邮件] Re: [PATCH][v2] x86/process: Return early if TIF_IO_BITMAP is set but no IO bitmap is assigned
Date: Sat, 13 Jun 2026 03:01:00 +0000 [thread overview]
Message-ID: <9d33a8bd946546509523572941dd9339@baidu.com> (raw)
In-Reply-To: <154f6291-c308-4a7a-8aab-286af04f6adf@intel.com>
> On 6/11/2026 10:49 PM, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > Outside the IOPL emulation path, the IO bitmap is always expected to
> > be allocated when TIF_IO_BITMAP is set. The paranoid WARN_ON_ONCE()
> > handles the case where the flag and the pointer got out of sync.
> > In this rare scenario, return early instead of continuing and
> > dereferencing a NULL pointer.
> >
> > [Sohil Mehta: rephrased commit message]
> >
>
> Never add handler comments for others. Such comments are only expected
> to be added when someone who is handling your patch modifies it but keeps
> the original authorship. You shouldn't add handler comments when you are
> changing the patch as an author yourself.
>
Ok, I will remove it in next version
[Li,Rongqing]
next prev parent reply other threads:[~2026-06-13 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 5:49 lirongqing
2026-06-12 14:34 ` Sohil Mehta
2026-06-13 3:01 ` Li,Rongqing [this message]
2026-06-13 6:59 ` 答复: [外部邮件] " Sohil Mehta
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=9d33a8bd946546509523572941dd9339@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=sohil.mehta@intel.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®