netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lucien xin <lucien.xin@gmail.com>
To: Marcelo Ricardo Leitner <mleitner@redhat.com>
Cc: network dev <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH net] sctp: ASCONF-ACK with Unresolvable Address should be sent
Date: Sat, 25 Jul 2015 13:02:42 +0800	[thread overview]
Message-ID: <CADvbK_eBo5Ut=SsW=Smn9rNe785SuTEpzqC_020bOXiUnjSUcw@mail.gmail.com> (raw)
In-Reply-To: <20150724191113.GO1730@localhost.localdomain>

On Sat, Jul 25, 2015 at 3:11 AM, Marcelo Ricardo Leitner
<mleitner@redhat.com> wrote:
> On Fri, Jul 24, 2015 at 02:56:29PM +0800, Xin Long wrote:
>> RFC 5061:
>>     This is an opaque integer assigned by the sender to identify each
>>     request parameter.  The receiver of the ASCONF Chunk will copy this
>>     32-bit value into the ASCONF Response Correlation ID field of the
>>     ASCONF-ACK response parameter.  The sender of the ASCONF can use this
>>     same value in the ASCONF-ACK to find which request the response is
>>     for.  Note that the receiver MUST NOT change this 32-bit value.
>>
>>     Address Parameter: TLV
>>
>>     This field contains an IPv4 or IPv6 address parameter, as described
>>     in Section 3.3.2.1 of [RFC4960].
>>
>> ASCONF chunk with Error Cause Indication Parameter (Unresolvable Address)
>> should be sent if the Delete IP Address is not part of the association.
>>
>>   Endpoint A                           Endpoint B
>>   (ESTABLISHED)                        (ESTABLISHED)
>>
>>   ASCONF        ----------------->
>>   (Delete IP Address)
>>                 <-----------------      ASCONF-ACK
>>                                         (Unresolvable Address)
>>
>> Signed-off-by: Xin Long <lucien.xin@gmail.com>
>> ---
>>  net/sctp/sm_make_chunk.c | 12 +++++++++++-
>>  1 file changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/sctp/sm_make_chunk.c b/net/sctp/sm_make_chunk.c
>> index 06320c8..88d82ef 100644
>> --- a/net/sctp/sm_make_chunk.c
>> +++ b/net/sctp/sm_make_chunk.c
>> @@ -3090,8 +3090,18 @@ static __be16 sctp_process_asconf_param(struct sctp_association *asoc,
>
> Please let's avoid increasing the indentation level when possible
>
>>                       sctp_assoc_set_primary(asoc, asconf->transport);
>>                       sctp_assoc_del_nonprimary_peers(asoc,
>>                                                       asconf->transport);
> add a return here
>
>> -             } else
>> +             } else {
> and remove this else {}
> and we're good.
>
> sctp code is often too indented, trying to reduce that bit here and
> there.
>
>> +                     /* If the address is not part of the association, the
>> +                      * ASCONF-ACK with Error Cause Indication Parameter
>> +                      * which including cause of Unresolvable Address should
>> +                      * be sent.
>> +                      */
>> +                     peer = sctp_assoc_lookup_paddr(asoc, &addr);
>> +                     if (!peer)
>> +                             return SCTP_ERROR_DNS_FAILED;
>> +
>>                       sctp_assoc_del_peer(asoc, &addr);
>
> Here we can replace this call to sctp_assoc_rm_peer() , because if we
> already have peer, we don't have to search for it again.
>
> Thanks,
> Marcelo
>
>> +             }
>>               break;
>>       case SCTP_PARAM_SET_PRIMARY:
>>               /* ADDIP Section 4.2.4
>> --
>> 2.1.0
>>
>
>

okay, I will repost it

  reply	other threads:[~2015-07-25  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  6:56 [RFC PATCH net] sctp: ASCONF-ACK with Unresolvable Address should be sent Xin Long
2015-07-24 19:11 ` Marcelo Ricardo Leitner
2015-07-25  5:02   ` lucien xin [this message]
2015-07-25  5:08 Xin Long
2015-07-27 13:44 ` Marcelo Ricardo Leitner
2015-08-11  4:34   ` lucien xin
2015-08-11 11:40     ` 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='CADvbK_eBo5Ut=SsW=Smn9rNe785SuTEpzqC_020bOXiUnjSUcw@mail.gmail.com' \
    --to=lucien.xin@gmail.com \
    --cc=mleitner@redhat.com \
    --cc=netdev@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 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).