public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Cong Wang <xiyou.wangcong@gmail•com>
Cc: Saeed Mahameed <saeed@kernel•org>,
	netdev@vger•kernel.org, g.nault@alphalink•fr,
	Cong Wang <cong.wang@bytedance•com>,
	syzbot+52866e24647f9a23403f@syzkaller•appspotmail.com,
	syzbot+94cc2a66fc228b23f360@syzkaller•appspotmail.com,
	Tetsuo Handa <penguin-kernel@i-love•sakura.ne.jp>,
	Jakub Sitnicki <jakub@cloudflare•com>,
	Eric Dumazet <edumazet@google•com>
Subject: Re: [Patch net 2/2] l2tp: close all race conditions in l2tp_tunnel_register()
Date: Mon, 9 Jan 2023 17:36:17 -0800	[thread overview]
Message-ID: <20230109173617.40c9eb83@kernel.org> (raw)
In-Reply-To: <Y7nNdx1yDoEEPrwY@pop-os.localdomain>

On Sat, 7 Jan 2023 11:52:23 -0800 Cong Wang wrote:
> But technically patch 1/2 does not fix anything alone, this is why I
> heisitate to add any Fixes tag to it.
> 
> Since this is a patchset, I think maintainers can easily figure out this
> is a whole set.

Yup, afaik prep patches don't need any extra tags if the dependency is
pretty obvious (same series and fix does not apply without the prep).

      reply	other threads:[~2023-01-10  1:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 19:13 [Patch net 0/2] l2tp: fix race conditions in l2tp_tunnel_register() Cong Wang
2023-01-05 19:13 ` [Patch net 1/2] l2tp: convert l2tp_tunnel_list to idr Cong Wang
2023-01-07 18:25   ` Saeed Mahameed
2023-01-07 19:48     ` Cong Wang
2023-01-07 19:48   ` Guillaume Nault
2023-01-09  9:55     ` Tom Parkin
2023-01-10  6:49     ` Cong Wang
2023-01-05 19:13 ` [Patch net 2/2] l2tp: close all race conditions in l2tp_tunnel_register() Cong Wang
2023-01-07 18:41   ` Saeed Mahameed
2023-01-07 19:52     ` Cong Wang
2023-01-10  1:36       ` 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=20230109173617.40c9eb83@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=cong.wang@bytedance$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=g.nault@alphalink$(echo .)fr \
    --cc=jakub@cloudflare$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=penguin-kernel@i-love$(echo .)sakura.ne.jp \
    --cc=saeed@kernel$(echo .)org \
    --cc=syzbot+52866e24647f9a23403f@syzkaller$(echo .)appspotmail.com \
    --cc=syzbot+94cc2a66fc228b23f360@syzkaller$(echo .)appspotmail.com \
    --cc=xiyou.wangcong@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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