From: Jason Gunthorpe <jgg@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ziyang Xuan <william.xuanziyang@huawei.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: vlan: fix a UAF in vlan_dev_real_dev()
Date: Wed, 3 Nov 2021 13:11:33 -0300 [thread overview]
Message-ID: <20211103161133.GS2744544@nvidia.com> (raw)
In-Reply-To: <20211103084746.2ae1c324@kicinski-fedora-PC1C0HJN>
On Wed, Nov 03, 2021 at 08:47:46AM -0700, Jakub Kicinski wrote:
> On Wed, 3 Nov 2021 10:50:34 -0300 Jason Gunthorpe wrote:
> > (though I can't tell either if there is a possiblecircular dep problem
> > in some oddball case)
>
> Same, luckily we're just starting a new dev cycle and syzbot can have
> at it.
>
> We should probably not let this patch get into stable right away -
> assuming you agree - would you mind nacking the selection if it happens?
> I'm not sure I'll get CCed since it doesn't have my tags.
I will make an effort, sure. It is hard to be confident due to all the
stable selection emails I get :|
Thanks,
Jason
next prev parent reply other threads:[~2021-11-03 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 2:12 [PATCH net v2] net: vlan: fix a UAF in vlan_dev_real_dev() Ziyang Xuan
2021-11-03 13:50 ` Jason Gunthorpe
2021-11-03 15:47 ` Jakub Kicinski
2021-11-03 16:11 ` Jason Gunthorpe [this message]
2021-11-03 14:30 ` patchwork-bot+netdevbpf
2021-11-15 17:04 ` Petr Machata
2021-11-15 17:49 ` Jakub Kicinski
2021-11-16 14:20 ` Petr Machata
2021-11-17 11:50 ` Petr Machata
2021-11-18 1:46 ` Ziyang Xuan (William)
2021-11-18 14:17 ` Jakub Kicinski
2021-11-19 3:29 ` Ziyang Xuan (William)
2021-11-19 10:07 ` Petr Machata
2021-11-23 9:01 ` Ziyang Xuan (William)
2021-11-23 12:35 ` Petr Machata
2021-11-25 11:33 ` Petr Machata
2021-11-26 1:48 ` Ziyang Xuan (William)
2021-11-19 3:04 ` Ziyang Xuan (William)
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=20211103161133.GS2744544@nvidia.com \
--to=jgg@nvidia.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=william.xuanziyang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).