From: Jakub Kicinski <kuba@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: "Denis V. Lunev" <den@virtuozzo.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>
Subject: Re: [PATCH -next] net: neigh: use dev_kfree_skb_irq instead of kfree_skb()
Date: Thu, 18 Aug 2022 19:39:10 -0700 [thread overview]
Message-ID: <20220818193910.50100711@kernel.org> (raw)
In-Reply-To: <6fab4f14-3afd-2576-e539-da37408f6b84@huawei.com>
On Fri, 19 Aug 2022 09:44:29 +0800 Yang Yingliang wrote:
> On 2022/8/19 0:32, Jakub Kicinski wrote:
> > Please put [PATCH net] as the tag for v2, this is a fix, not -next
> > material.
> OK.
> I don't find the commit 66ba215cb513 ("neigh: fix possible DoS due to
> net iface start/stop loop")
I see where the confusion is coming from. It's too fresh to have made
it to Linus. It's part of this pull request:
https://lore.kernel.org/all/20220818195549.1805709-1-kuba@kernel.org/
but Linus has not pulled yet.
I believe if something is in the "pending-fixes" branch of linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h=pending-fixes
you can consider it to be an immediate fix, rather than -next material.
Not sure if that makes sense but that's the best I can do explaining
it...
prev parent reply other threads:[~2022-08-19 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 4:37 [PATCH -next] net: neigh: use dev_kfree_skb_irq instead of kfree_skb() Yang Yingliang
2022-08-18 9:00 ` Denis V. Lunev
2022-08-18 10:47 ` Yang Yingliang
2022-08-18 16:32 ` Jakub Kicinski
2022-08-19 1:44 ` Yang Yingliang
2022-08-19 2:39 ` Jakub Kicinski [this message]
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=20220818193910.50100711@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=den@virtuozzo.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/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.