From: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
To: Wei Yongjun <yjwei@cn.fujitsu.com>
Cc: vladislav <vladislav.yasevich@hp.com>,
netdev <netdev@vger.kernel.org>,
lksctp-dev <lksctp-developers@lists.sourceforge.net>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] SCTP: Fix Protocol violation when receiving a error length INIT ACK
Date: Tue, 25 Mar 2008 15:10:30 +0800 [thread overview]
Message-ID: <47E8A566.6060405@cn.fujitsu.com> (raw)
In-Reply-To: <47E883B9.5040907@cn.fujitsu.com>
Wei Yongjun wrote:
> Hi Gui:
>
> I looked the source code and found that only in the state *COOKIE_WAIT*
> received INIT-ACK need to do this, not all of the states. The other
> states we should have known the init-tag of peer.
yes, it's the only possibility.
>
> Gui Jianfeng wrote:
>> Wei Yongjun wrote:
>>
>>> NACK.
>>>
>>> If the INIT-ACK chunk is too short to contain the init-tag, get the
>>> init-tag of peer may get a unexpected value.
>>> Such as this:
>>> CHUNK_INIT_ACK
>>> Type = 2
>>> Flags = 0
>>> Length = 4
>>>
>>> So I think the better way is to set T bit of ABORT chunk and used the
>>> own's Tag.
>>>
>>
>> Seems reasonable. Please ignore the previous one, here is a new patch.
>>
>> Signed-off-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
>> ---
>> net/sctp/outqueue.c | 3 +++
>> net/sctp/sm_statefuns.c | 5 +++++
>> 2 files changed, 8 insertions(+), 0 deletions(-)
>>
>> diff --git a/net/sctp/outqueue.c b/net/sctp/outqueue.c
>> index 1bb3c5c..c071446 100644
>> --- a/net/sctp/outqueue.c
>> +++ b/net/sctp/outqueue.c
>> @@ -793,6 +793,9 @@ int sctp_outq_flush(struct sctp_outq *q, int
>> rtx_timeout)
>> break;
>>
>> case SCTP_CID_ABORT:
>> + if (sctp_test_T_bit(chunk)) {
>> + packet->vtag = asoc->c.my_vtag;
>> + }
>> case SCTP_CID_SACK:
>> case SCTP_CID_HEARTBEAT:
>> case SCTP_CID_HEARTBEAT_ACK:
>>
>
>> diff --git a/net/sctp/sm_statefuns.c b/net/sctp/sm_statefuns.c
>> index f2ed647..85e1d63 100644
>> --- a/net/sctp/sm_statefuns.c
>> +++ b/net/sctp/sm_statefuns.c
>> @@ -4144,6 +4144,11 @@ static sctp_disposition_t sctp_sf_abort_violation(
>> goto nomem;
>>
>> if (asoc) {
>> + /* Treat INIT-ACK as a special case. */
>> + if (chunk->chunk_hdr->type == SCTP_CID_INIT_ACK) {
>> + abort->chunk_hdr->flags |= SCTP_CHUNK_FLAG_T;
>> + }
>> +
>> sctp_add_cmd_sf(commands, SCTP_CMD_REPLY, SCTP_CHUNK(abort));
>> SCTP_INC_STATS(SCTP_MIB_OUTCTRLCHUNKS);
>>
>>
> Those code should be move to sctp_make_abort() for
> common using. And may be need check whether we need the T flags.
This rarely happens, so i think it's sufficient to place this block of code here.
Moving it into sctp_make_abort() will waste much cpu time when generating each abort chunk .
>
>
>
>
--
Regards
Gui Jianfeng
next prev parent reply other threads:[~2008-03-25 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 5:39 [PATCH] SCTP: Fix Protocol violation when receiving a error length INIT ACK Gui Jianfeng
2008-03-24 6:32 ` Wei Yongjun
2008-03-25 3:33 ` Gui Jianfeng
2008-03-25 4:46 ` Wei Yongjun
2008-03-25 7:10 ` Gui Jianfeng [this message]
2008-03-25 15:10 ` Vlad Yasevich
2008-03-27 1:40 ` Gui Jianfeng
2008-03-27 19:55 ` Vlad Yasevich
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=47E8A566.6060405@cn.fujitsu.com \
--to=guijianfeng@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--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).