From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [PATCH CLEANUP] sctp: fix the comment of sctp_sf_violation_paramlen()
Date: Mon, 17 May 2010 06:14:48 +0000 [thread overview]
Message-ID: <4BF0DED8.40503@cn.fujitsu.com> (raw)
In-Reply-To: <4BF0DD56.70105@cn.fujitsu.com>
于 2010年05月17日 14:08, Shan Wei 写道:
> The comment about sctp_sf_violation_paramlen() is wrong.
>
> Invalid length should be identified as it does not equal actual length
> of a given parameter. The actual length of a given parameter is not including
> the padding part.
>
Not right. If the param length is larger then what is request, we
also treat it as correct. And for unkonw params, we just check
the length larger then the minimal length.
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
> ---
> net/sctp/sm_statefuns.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/sctp/sm_statefuns.c b/net/sctp/sm_statefuns.c
> index edb71e6..8774a6e 100644
> --- a/net/sctp/sm_statefuns.c
> +++ b/net/sctp/sm_statefuns.c
> @@ -4355,8 +4355,8 @@ static sctp_disposition_t sctp_sf_violation_chunklen(
>
> /*
> * Handle a protocol violation when the parameter length is invalid.
> - * "Invalid" length is identified as smaller than the minimal length a
> - * given parameter can be.
> + * "Invalid" length is identified as it does not equal actual length
> + * of a given parameter.
> */
> static sctp_disposition_t sctp_sf_violation_paramlen(
> const struct sctp_endpoint *ep,
>
next prev parent reply other threads:[~2010-05-17 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 6:08 [PATCH CLEANUP] sctp: fix the comment of sctp_sf_violation_paramlen() Shan Wei
2010-05-17 6:14 ` Wei Yongjun [this message]
2010-05-17 7:55 ` Shan Wei
2010-05-17 14:30 ` Vlad Yasevich
2010-05-18 10:08 ` Shan Wei
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=4BF0DED8.40503@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.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.