From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org, yjwei@cn.fujitsu.com
Subject: Re: [PATCH net-next 5/5] sctp: Add validity check for SCTP_PARTIAL_DELIVERY_POINT socket option
Date: Thu, 25 Dec 2008 16:59:14 -0800 (PST) [thread overview]
Message-ID: <20081225.165914.95302523.davem@davemloft.net> (raw)
In-Reply-To: <1229737672-28328-7-git-send-email-vladislav.yasevich@hp.com>
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Fri, 19 Dec 2008 20:47:52 -0500
> The latest ietf socket extensions API draft said:
>
> 8.1.21. Set or Get the SCTP Partial Delivery Point
>
> Note also that the call will fail if the user attempts to set
> this value larger than the socket receive buffer size.
>
> This patch add this validity check for SCTP_PARTIAL_DELIVERY_POINT
> socket option.
>
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Also applied, thanks.
prev parent reply other threads:[~2008-12-26 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 1:47 [PATCH net-next 0/5]: SCTP updates Vlad Yasevich
2008-12-20 1:47 ` Vlad Yasevich
2008-12-20 1:47 ` [PATCH net-next 1/5] sctp: Bring SCTP_MAXSEG socket option into ietf API extension compliance Vlad Yasevich
2008-12-26 0:56 ` David Miller
2008-12-26 17:04 ` Vlad Yasevich
2008-12-26 19:15 ` David Miller
2008-12-20 1:47 ` [PATCH net-next 2/5] sctp: Fix a typo in socket.c Vlad Yasevich
2008-12-26 0:57 ` David Miller
2008-12-20 1:47 ` [PATCH net-next 3/5] sctp: Implement socket option SCTP_GET_ASSOC_NUMBER Vlad Yasevich
2008-12-26 0:57 ` David Miller
2008-12-20 1:47 ` [PATCH net-next 4/5] sctp: Avoid memory overflow while FWD-TSN chunk is received with bad stream ID Vlad Yasevich
2008-12-26 0:58 ` David Miller
2008-12-20 1:47 ` [PATCH net-next 5/5] sctp: Add validity check for SCTP_PARTIAL_DELIVERY_POINT socket option Vlad Yasevich
2008-12-26 0:59 ` David Miller [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=20081225.165914.95302523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
--cc=yjwei@cn.fujitsu.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).