All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	chenzhen126@huawei.com, caowangbao@huawei.com
Subject: [PATCH net 0/2] sctp: fix a NULL pointer dereference in sctp_sched_dequeue_common
Date: Fri,  4 Nov 2022 17:45:14 -0400	[thread overview]
Message-ID: <cover.1667598261.git.lucien.xin@gmail.com> (raw)

This issue was triggered with SCTP_PR_SCTP_PRIO in sctp,
and caused by not checking and fixing stream->out_curr
after removing a chunk from this stream.

Patch 1 removes an unnecessary check and makes the real
fix easier to add in Patch 2.

Xin Long (2):
  sctp: remove the unnecessary sinfo_stream check in
    sctp_prsctp_prune_unsent
  sctp: clear out_curr if all frag chunks of current msg are pruned

 net/sctp/outqueue.c | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-11-04 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 21:45 Xin Long [this message]
2022-11-04 21:45 ` [PATCH net 1/2] sctp: remove the unnecessary sinfo_stream check in sctp_prsctp_prune_unsent Xin Long
2022-11-04 21:45 ` [PATCH net 2/2] sctp: clear out_curr if all frag chunks of current msg are pruned Xin Long
2022-11-08  4:10 ` [PATCH net 0/2] sctp: fix a NULL pointer dereference in sctp_sched_dequeue_common patchwork-bot+netdevbpf

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=cover.1667598261.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=caowangbao@huawei.com \
    --cc=chenzhen126@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pabeni@redhat.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.