From: Greg KH <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: cve@kernel.org, jianqi.ren.cn@windriver.com,
stable@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, sashal@kernel.org, jamie.bainbridge@gmail.com,
jdamato@fastly.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y] net: napi: Prevent overflow of napi_defer_hard_irqs
Date: Thu, 12 Dec 2024 16:17:56 +0100 [thread overview]
Message-ID: <2024121246-phrase-dynamite-356d@gregkh> (raw)
In-Reply-To: <20241212065044.09d7b377@kernel.org>
On Thu, Dec 12, 2024 at 06:50:44AM -0800, Jakub Kicinski wrote:
> On Thu, 12 Dec 2024 12:41:08 +0100 Greg KH wrote:
> > On Wed, Dec 11, 2024 at 12:03:04PM +0800, jianqi.ren.cn@windriver.com wrote:
> > > From: Joe Damato <jdamato@fastly.com>
> > >
> > > [ Upstream commit 08062af0a52107a243f7608fd972edb54ca5b7f8 ]
> >
> > You can't ignore the 6.6.y tree :(
> >
> > Dropping from my review queue now.
>
> Is it possible to instead mark CVE-2024-50018 as invalid, please?
> The change is cosmetic.
Now rejected, sorry about that.
greg k-h
next prev parent reply other threads:[~2024-12-12 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 4:03 [PATCH 6.1.y] net: napi: Prevent overflow of napi_defer_hard_irqs jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-12 4:07 ` Jakub Kicinski
2024-12-12 7:06 ` Ren, Jianqi (Jacky) (CN)
2024-12-12 11:41 ` Greg KH
2024-12-12 14:50 ` Jakub Kicinski
2024-12-12 15:17 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 10:10 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
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=2024121246-phrase-dynamite-356d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jamie.bainbridge@gmail.com \
--cc=jdamato@fastly.com \
--cc=jianqi.ren.cn@windriver.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.