From: Greg KH <gregkh@linuxfoundation.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, prarit@redhat.com,
x86@kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6.6 RESEND 2/2] x86/irq: Plug vector setup race
Date: Fri, 22 Aug 2025 11:48:56 +0200 [thread overview]
Message-ID: <2025082249-gigolo-limeade-b44e@gregkh> (raw)
In-Reply-To: <9fa1c126-00f1-95db-93a0-cee52a70062e@huawei.com>
On Fri, Aug 22, 2025 at 05:25:56PM +0800, Jinjie Ruan wrote:
>
>
> On 2025/8/22 16:57, Greg KH wrote:
> > On Fri, Aug 22, 2025 at 03:38:25AM +0000, Jinjie Ruan wrote:
> >> From: Thomas Gleixner <tglx@linutronix.de>
> >>
> >> commit ce0b5eedcb753697d43f61dd2e27d68eb5d3150f upstream.
> >>
>
> [...]
>
> >>
> >> /*
> >> @@ -273,7 +308,9 @@ DEFINE_IDTENTRY_IRQ(common_interrupt)
> >> /* entry code tells RCU that we're not quiescent. Check it. */
> >> RCU_LOCKDEP_WARN(!rcu_is_watching(), "IRQ failed to wake up RCU");
> >>
> >> - call_irq_handler(vector, regs);
> >> + if (unlikely(!call_irq_handler(vector, regs)))
> >> + apic_eoi();
> >> +
> >
> > This chunk does not look correct. The original commit did not have
> > this, so why add it here? Where did it come from?
> >
> > The original patch said:
> > - if (unlikely(call_irq_handler(vector, regs)))
> > + if (unlikely(!call_irq_handler(vector, regs)))
> >
> > And was not an if statement.
> >
> > So did you forget to backport something else here? Why is this not
> > identical to what the original was?
>
> The if statement is introduced in commit 1b03d82ba15e ("x86/irq: Install
> posted MSI notification handler") which is a patch in patch set
> https://lore.kernel.org/all/20240423174114.526704-1-jacob.jun.pan@linux.intel.com/,
> but it seems to be a performance optimization patch set, and this patch
> includes additional modifications. The context conflict is merely a
> simple refactoring, but the cost of the entire round of this patch set
> is too high.
Why is it "too high"? We almost NEVER want to deviate from what is in
mainline, as every time wo do that it adds the potential for bugs AND it
increases our maintance burden (i.e. later patches will not apply.)
For a kernel that has to live as long as this one does, we need to try
to stick to what is in mainline as close as possible. Otherwise it
becomes unworkable.
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-22 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 3:38 [PATCH v6.6 RESEND 0/2] x86/irq: Plug vector setup race Jinjie Ruan
2025-08-22 3:38 ` [PATCH v6.6 RESEND 1/2] x86/irq: Factor out handler invocation from common_interrupt() Jinjie Ruan
2025-08-22 3:38 ` [PATCH v6.6 RESEND 2/2] x86/irq: Plug vector setup race Jinjie Ruan
2025-08-22 8:57 ` Greg KH
2025-08-22 9:25 ` Jinjie Ruan
2025-08-22 9:48 ` Greg KH [this message]
2025-08-22 9:50 ` Greg KH
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=2025082249-gigolo-limeade-b44e@gregkh \
--to=gregkh@linuxfoundation.org \
--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=prarit@redhat.com \
--cc=ruanjinjie@huawei.com \
--cc=stable@vger.kernel.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