From: Xin Long <lucien.xin@gmail.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: network dev <netdev@vger.kernel.org>,
"linux-sctp @ vger . kernel . org" <linux-sctp@vger.kernel.org>,
davem <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Or Cohen <orcohen@paloaltonetworks.com>
Subject: Re: [PATCH net 0/2] sctp: fix the race condition in sctp_destroy_sock in a proper way
Date: Mon, 10 May 2021 15:18:42 -0400 [thread overview]
Message-ID: <CADvbK_fUa9SWZC30Jp2wnJW9Q7ds-pV_+FOVPUaceQh2KbWNzw@mail.gmail.com> (raw)
In-Reply-To: <YJmFKVqZWDRe5Rzn@eldamar.lan>
On Mon, May 10, 2021 at 3:10 PM Salvatore Bonaccorso <carnil@debian.org> wrote:
>
> Hi Xin,
>
> On Mon, May 03, 2021 at 05:11:40AM +0800, Xin Long wrote:
> > The original fix introduced a dead lock, and has to be removed in
> > Patch 1/2, and we will get a proper way to fix it in Patch 2/2.
> >
> > Xin Long (2):
> > Revert "net/sctp: fix race condition in sctp_destroy_sock"
> > sctp: delay auto_asconf init until binding the first addr
> >
> > net/sctp/socket.c | 38 ++++++++++++++++++++++----------------
> > 1 file changed, 22 insertions(+), 16 deletions(-)
>
> The original commit which got reverted in this series, was already
> applied to several stable series, namely all of 4.4.268, 4.9.268,
> 4.14.232, 4.19.189, 5.4.114, 5.10.32, 5.11.16.
>
> Is it planned to do the revert and bugfix in those as well?
Yes. Thanks.
prev parent reply other threads:[~2021-05-10 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 21:11 [PATCH net 0/2] sctp: fix the race condition in sctp_destroy_sock in a proper way Xin Long
2021-05-02 21:11 ` [PATCH net 1/2] Revert "net/sctp: fix race condition in sctp_destroy_sock" Xin Long
2021-05-02 21:11 ` [PATCH net 2/2] sctp: delay auto_asconf init until binding the first addr Xin Long
2021-05-03 20:40 ` [PATCH net 0/2] sctp: fix the race condition in sctp_destroy_sock in a proper way patchwork-bot+netdevbpf
2021-05-10 19:10 ` Salvatore Bonaccorso
2021-05-10 19:18 ` Xin Long [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=CADvbK_fUa9SWZC30Jp2wnJW9Q7ds-pV_+FOVPUaceQh2KbWNzw@mail.gmail.com \
--to=lucien.xin@gmail.com \
--cc=carnil@debian.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=orcohen@paloaltonetworks.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).