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: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	davem@davemloft.net
Subject: [PATCHv2 net-next 0/5] sctp: clean up __sctp_connect function
Date: Tue, 30 Jul 2019 12:38:18 +0000	[thread overview]
Message-ID: <cover.1564490276.git.lucien.xin@gmail.com> (raw)

This patchset is to factor out some common code for
sctp_sendmsg_new_asoc() and __sctp_connect() into 2
new functioins.

v1->v2:
  - add the patch 1/5 to avoid a slab-out-of-bounds warning.
  - add some code comment for the check change in patch 2/5.
  - remove unused 'addrcnt' as Marcelo noticed in patch 3/5.

Xin Long (5):
  sctp: only copy the available addr data in sctp_transport_init
  sctp: check addr_size with sa_family_t size in
    __sctp_setsockopt_connectx
  sctp: clean up __sctp_connect
  sctp: factor out sctp_connect_new_asoc
  sctp: factor out sctp_connect_add_peer

 net/sctp/socket.c    | 376 ++++++++++++++++++++-------------------------------
 net/sctp/transport.c |   2 +-
 2 files changed, 147 insertions(+), 231 deletions(-)

-- 
2.1.0

WARNING: multiple messages have this Message-ID (diff)
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	davem@davemloft.net
Subject: [PATCHv2 net-next 0/5] sctp: clean up __sctp_connect function
Date: Tue, 30 Jul 2019 20:38:18 +0800	[thread overview]
Message-ID: <cover.1564490276.git.lucien.xin@gmail.com> (raw)

This patchset is to factor out some common code for
sctp_sendmsg_new_asoc() and __sctp_connect() into 2
new functioins.

v1->v2:
  - add the patch 1/5 to avoid a slab-out-of-bounds warning.
  - add some code comment for the check change in patch 2/5.
  - remove unused 'addrcnt' as Marcelo noticed in patch 3/5.

Xin Long (5):
  sctp: only copy the available addr data in sctp_transport_init
  sctp: check addr_size with sa_family_t size in
    __sctp_setsockopt_connectx
  sctp: clean up __sctp_connect
  sctp: factor out sctp_connect_new_asoc
  sctp: factor out sctp_connect_add_peer

 net/sctp/socket.c    | 376 ++++++++++++++++++++-------------------------------
 net/sctp/transport.c |   2 +-
 2 files changed, 147 insertions(+), 231 deletions(-)

-- 
2.1.0


             reply	other threads:[~2019-07-30 12:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 12:38 Xin Long [this message]
2019-07-30 12:38 ` [PATCHv2 net-next 0/5] sctp: clean up __sctp_connect function Xin Long
2019-07-30 12:38 ` [PATCHv2 net-next 1/5] sctp: only copy the available addr data in sctp_transport_init Xin Long
2019-07-30 12:38   ` Xin Long
2019-07-30 12:38   ` [PATCHv2 net-next 2/5] sctp: check addr_size with sa_family_t size in __sctp_setsockopt_connectx Xin Long
2019-07-30 12:38     ` Xin Long
2019-07-30 12:38     ` [PATCHv2 net-next 3/5] sctp: clean up __sctp_connect Xin Long
2019-07-30 12:38       ` Xin Long
2019-07-30 12:38       ` [PATCHv2 net-next 4/5] sctp: factor out sctp_connect_new_asoc Xin Long
2019-07-30 12:38         ` Xin Long
2019-07-30 12:38         ` [PATCHv2 net-next 5/5] sctp: factor out sctp_connect_add_peer Xin Long
2019-07-30 12:38           ` Xin Long
2019-07-30 19:24   ` [PATCHv2 net-next 1/5] sctp: only copy the available addr data in sctp_transport_init Marcelo Ricardo Leitner
2019-07-30 19:24     ` Marcelo Ricardo Leitner
2019-07-30 19:42 ` [PATCHv2 net-next 0/5] sctp: clean up __sctp_connect function Marcelo Ricardo Leitner
2019-07-30 19:42   ` Marcelo Ricardo Leitner
2019-07-30 21:18   ` David Miller
2019-07-30 21:18     ` David Miller

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.1564490276.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --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 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.