From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
davem@davemloft.net
Subject: Re: [PATCH net-next 3/3] sctp: add support for snd flag SCTP_SENDALL process in sendmsg
Date: Tue, 06 Mar 2018 12:22:36 +0000 [thread overview]
Message-ID: <20180306122236.GF27351@localhost.localdomain> (raw)
In-Reply-To: <5abf7d1eafab86acebcfab55f2cf4a081f5b1088.1520253539.git.lucien.xin@gmail.com>
On Mon, Mar 05, 2018 at 08:44:20PM +0800, Xin Long wrote:
> This patch is to add support for snd flag SCTP_SENDALL process
> in sendmsg, as described in section 5.3.4 of RFC6458.
>
> With this flag, you can send the same data to all the asocs of
> this sk once.
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
> ---
> include/uapi/linux/sctp.h | 2 ++
> net/sctp/socket.c | 35 +++++++++++++++++++++++++++++++----
> 2 files changed, 33 insertions(+), 4 deletions(-)
>
> diff --git a/include/uapi/linux/sctp.h b/include/uapi/linux/sctp.h
> index a1bc350..e94b6d2 100644
> --- a/include/uapi/linux/sctp.h
> +++ b/include/uapi/linux/sctp.h
> @@ -284,6 +284,8 @@ enum sctp_sinfo_flags {
> SCTP_ADDR_OVER = (1 << 1), /* Override the primary destination. */
> SCTP_ABORT = (1 << 2), /* Send an ABORT message to the peer. */
> SCTP_SACK_IMMEDIATELY = (1 << 3), /* SACK should be sent without delay. */
> + /* 2 bits here have been used by SCTP_PR_SCTP_MASK */
> + SCTP_SENDALL = (1 << 6),
> SCTP_NOTIFICATION = MSG_NOTIFICATION, /* Next message is not user msg but notification. */
> SCTP_EOF = MSG_FIN, /* Initiate graceful shutdown process. */
> };
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 067b57a..7d3476a 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -1820,6 +1820,10 @@ static int sctp_sendmsg_check_sflags(struct sctp_association *asoc,
> if (sctp_state(asoc, CLOSED) && sctp_style(sk, TCP))
> return -EPIPE;
>
> + if ((sflags & SCTP_SENDALL) && sctp_style(sk, UDP) &&
> + !sctp_state(asoc, ESTABLISHED))
> + return 0;
> +
> if (sflags & SCTP_EOF) {
> pr_debug("%s: shutting down association:%p\n", __func__, asoc);
> sctp_primitive_SHUTDOWN(net, asoc, NULL);
> @@ -2007,6 +2011,29 @@ static int sctp_sendmsg(struct sock *sk, struct msghdr *msg, size_t msg_len)
>
> lock_sock(sk);
>
> + /* SCTP_SENDALL process */
> + if ((sflags & SCTP_SENDALL) && sctp_style(sk, UDP)) {
> + list_for_each_entry(asoc, &ep->asocs, asocs) {
> + err = sctp_sendmsg_check_sflags(asoc, sflags, msg,
> + msg_len);
> + if (err = 0)
> + continue;
> + if (err < 0)
> + goto out_unlock;
> +
> + sctp_sendmsg_update_sinfo(asoc, sinfo, &cmsgs);
> +
> + err = sctp_sendmsg_to_asoc(asoc, msg, msg_len,
> + NULL, sinfo);
> + if (err < 0)
> + goto out_unlock;
> +
> + iov_iter_revert(&msg->msg_iter, err);
> + }
> +
> + goto out_unlock;
> + }
> +
> /* Get and check or create asoc */
> if (daddr) {
> asoc = sctp_endpoint_lookup_assoc(ep, daddr, &transport);
> @@ -7792,8 +7819,8 @@ static int sctp_msghdr_parse(const struct msghdr *msg, struct sctp_cmsgs *cmsgs)
>
> if (cmsgs->srinfo->sinfo_flags &
> ~(SCTP_UNORDERED | SCTP_ADDR_OVER |
> - SCTP_SACK_IMMEDIATELY | SCTP_PR_SCTP_MASK |
> - SCTP_ABORT | SCTP_EOF))
> + SCTP_SACK_IMMEDIATELY | SCTP_SENDALL |
> + SCTP_PR_SCTP_MASK | SCTP_ABORT | SCTP_EOF))
> return -EINVAL;
> break;
>
> @@ -7816,8 +7843,8 @@ static int sctp_msghdr_parse(const struct msghdr *msg, struct sctp_cmsgs *cmsgs)
>
> if (cmsgs->sinfo->snd_flags &
> ~(SCTP_UNORDERED | SCTP_ADDR_OVER |
> - SCTP_SACK_IMMEDIATELY | SCTP_PR_SCTP_MASK |
> - SCTP_ABORT | SCTP_EOF))
> + SCTP_SACK_IMMEDIATELY | SCTP_SENDALL |
> + SCTP_PR_SCTP_MASK | SCTP_ABORT | SCTP_EOF))
> return -EINVAL;
> break;
> case SCTP_PRINFO:
> --
> 2.1.0
>
next prev parent reply other threads:[~2018-03-06 12:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 12:44 [PATCH net-next 0/3] sctp: add support for some msg_control options from RFC6458 Xin Long
2018-03-05 12:44 ` [PATCH net-next 1/3] sctp: add support for PR-SCTP Information for sendmsg Xin Long
2018-03-05 12:44 ` [PATCH net-next 2/3] sctp: add support for SCTP_DSTADDRV4/6 " Xin Long
2018-03-05 12:44 ` [PATCH net-next 3/3] sctp: add support for snd flag SCTP_SENDALL process in sendmsg Xin Long
2018-03-06 12:22 ` Marcelo Ricardo Leitner [this message]
2018-03-05 23:39 ` [PATCH net-next 2/3] sctp: add support for SCTP_DSTADDRV4/6 Information for sendmsg Marcelo Ricardo Leitner
2018-03-06 7:03 ` Xin Long
2018-03-06 12:21 ` Marcelo Ricardo Leitner
2018-03-06 12:22 ` Marcelo Ricardo Leitner
2018-03-06 12:22 ` [PATCH net-next 1/3] sctp: add support for PR-SCTP " Marcelo Ricardo Leitner
2018-03-05 23:52 ` [PATCH net-next 0/3] sctp: add support for some msg_control options from RFC6458 Marcelo Ricardo Leitner
2018-03-07 15:56 ` David Miller
2018-10-21 4:43 ` [PATCH net-next 0/3] sctp: add support for sk_reuseport Xin Long
2018-10-21 4:43 ` [PATCH net-next 1/3] sctp: do reuseport_select_sock in __sctp_rcv_lookup_endpoint Xin Long
2018-10-21 4:43 ` [PATCH net-next 2/3] sctp: add sock_reuseport for the sock in __sctp_hash_endpoint Xin Long
2018-10-21 4:43 ` [PATCH net-next 3/3] sctp: process sk_reuseport in sctp_get_port_local Xin Long
2018-10-22 14:15 ` [PATCH net-next 2/3] sctp: add sock_reuseport for the sock in __sctp_hash_endpoint Marcelo Ricardo Leitner
2018-11-12 9:58 ` Xin Long
2018-10-22 14:17 ` [PATCH net-next 1/3] sctp: do reuseport_select_sock in __sctp_rcv_lookup_endpoint Marcelo Ricardo Leitner
2018-11-12 9:56 ` Xin Long
2018-10-21 6:58 ` [PATCH net-next 0/3] sctp: add support for sk_reuseport Xin Long
2018-10-22 11:40 ` Neil Horman
2018-10-22 14:20 ` Marcelo Ricardo Leitner
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=20180306122236.GF27351@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@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;
as well as URLs for NNTP newsgroup(s).