From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, marcelo.leitner@gmail.com,
nhorman@tuxdriver.com
Subject: Re: [PATCH net] sctp: check asoc strreset_chunk in sctp_generate_reconf_event
Date: Sat, 23 Apr 2022 21:40:10 +0000 [thread overview]
Message-ID: <165075001054.4343.8485395307076127833.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3000f8b12920ae81b84dceead6dcc90bb00c0403.1650487961.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 20 Apr 2022 16:52:41 -0400 you wrote:
> A null pointer reference issue can be triggered when the response of a
> stream reconf request arrives after the timer is triggered, such as:
>
> send Incoming SSN Reset Request --->
> CPU0:
> reconf timer is triggered,
> go to the handler code before hold sk lock
> <--- reply with Outgoing SSN Reset Request
> CPU1:
> process Outgoing SSN Reset Request,
> and set asoc->strreset_chunk to NULL
> CPU0:
> continue the handler code, hold sk lock,
> and try to hold asoc->strreset_chunk, crash!
>
> [...]
Here is the summary with links:
- [net] sctp: check asoc strreset_chunk in sctp_generate_reconf_event
https://git.kernel.org/netdev/net/c/165e3e17fe8f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-23 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 20:52 [PATCH net] sctp: check asoc strreset_chunk in sctp_generate_reconf_event Xin Long
2022-04-21 10:18 ` David Miller
2022-04-21 15:04 ` Xin Long
2022-04-23 13:18 ` Marcelo Ricardo Leitner
2022-04-23 21:40 ` patchwork-bot+netdevbpf [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=165075001054.4343.8485395307076127833.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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