From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [PATCH] sctp: fix the sendmsg() flag SCTP_EOF to comply to spec
Date: Thu, 10 Sep 2009 17:35:26 +0000 [thread overview]
Message-ID: <4AA938DE.10100@hp.com> (raw)
In-Reply-To: <4AA87054.3070201@cn.fujitsu.com>
Wei Yongjun wrote:
> It should be possible to send a message and set the SCTP_EOF flag
> at the same time, but we don't support it yet. This patch fix the
> sendmsg() flag SCTP_EOF to comply to spec.
Hi Wei
Good start, but I don't think this will work with implicit connection.
We are going to attempt to associate, queue the DATA, and then issue a
shutdown, which will call sctp_sf_cookie_wait_prm_shutdown() thus never
sending.
Also, we might want to forbid this combination on non-blocking sockets
since we would essentially need to run the whole thing in a separate task.
-vlad
>
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
> ---
> net/sctp/socket.c | 15 ++++++++++-----
> 1 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 89af37a..d48e18c 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -1540,13 +1540,12 @@ SCTP_STATIC int sctp_sendmsg(struct kiocb *iocb, struct sock *sk,
> goto out_nounlock;
> }
>
> - /* If SCTP_EOF is set, no data can be sent. Disallow sending zero
> - * length messages when SCTP_EOF|SCTP_ABORT is not set.
> + /* Disallow sending zero length messages when SCTP_EOF|SCTP_ABORT
> + * is not set.
> * If SCTP_ABORT is set, the message length could be non zero with
> * the msg_iov set to the user abort reason.
> */
> - if (((sinfo_flags & SCTP_EOF) && (msg_len > 0)) ||
> - (!(sinfo_flags & (SCTP_EOF|SCTP_ABORT)) && (msg_len = 0))) {
> + if (!(sinfo_flags & (SCTP_EOF|SCTP_ABORT)) && (msg_len = 0)) {
> err = -EINVAL;
> goto out_nounlock;
> }
> @@ -1603,7 +1602,7 @@ SCTP_STATIC int sctp_sendmsg(struct kiocb *iocb, struct sock *sk,
> goto out_unlock;
> }
>
> - if (sinfo_flags & SCTP_EOF) {
> + if ((sinfo_flags & SCTP_EOF) && msg_len = 0) {
> SCTP_DEBUG_PRINTK("Shutting down association: %p\n",
> asoc);
> sctp_primitive_SHUTDOWN(asoc, NULL);
> @@ -1835,6 +1834,12 @@ SCTP_STATIC int sctp_sendmsg(struct kiocb *iocb, struct sock *sk,
> else
> err = msg_len;
>
> + if (sinfo_flags & SCTP_EOF) {
> + SCTP_DEBUG_PRINTK("Shutting down association: %p\n",
> + asoc);
> + sctp_primitive_SHUTDOWN(asoc, NULL);
> + }
> +
> /* If we are already past ASSOCIATE, the lower
> * layers are responsible for association cleanup.
> */
prev parent reply other threads:[~2009-09-10 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 3:19 [PATCH] sctp: fix the sendmsg() flag SCTP_EOF to comply to spec Wei Yongjun
2009-09-10 17:35 ` Vlad Yasevich [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=4AA938DE.10100@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=linux-sctp@vger.kernel.org \
/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.