netdev - Re: [PATCH net] sctp: remove temporary variable confirm from sctp_packet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 19 Mar 2017 00:26:50 +0800
From:   Xin Long <lucien.xin@...il.com>
To:     Julian Anastasov <ja@....bg>
Cc:     network dev <netdev@...r.kernel.org>, linux-sctp@...r.kernel.org,
        davem <davem@...emloft.net>,
        Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
        Neil Horman <nhorman@...driver.com>,
        Vlad Yasevich <vyasevich@...il.com>
Subject: Re: [PATCH net] sctp: remove temporary variable confirm from sctp_packet_transmit

On Sat, Mar 18, 2017 at 7:48 PM, Julian Anastasov <ja@....bg> wrote:
>
>         Hello,
>
> On Sat, 18 Mar 2017, Xin Long wrote:
>
>> Commit c86a773c7802 ("sctp: add dst_pending_confirm flag") introduced
>> a temporary variable "confirm" in sctp_packet_transmit.
>>
>> But it broke the rule that longer lines should be above shorter ones.
>> Besides, this variable is not necessary, so this patch is to just
>> remove it and use tp->dst_pending_confirm directly.
>>
>> Fixes: c86a773c7802 ("sctp: add dst_pending_confirm flag")
>> Signed-off-by: Xin Long <lucien.xin@...il.com>
>> ---
>>  net/sctp/output.c | 7 +++----
>>  1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/net/sctp/output.c b/net/sctp/output.c
>> index 71ce6b9..1224421 100644
>> --- a/net/sctp/output.c
>> +++ b/net/sctp/output.c
>> @@ -546,7 +546,6 @@ int sctp_packet_transmit(struct sctp_packet *packet, gfp_t gfp)
>>       struct sctp_association *asoc = tp->asoc;
>>       struct sctp_chunk *chunk, *tmp;
>>       int pkt_count, gso = 0;
>> -     int confirm;
>>       struct dst_entry *dst;
>>       struct sk_buff *head;
>>       struct sctphdr *sh;
>> @@ -625,13 +624,13 @@ int sctp_packet_transmit(struct sctp_packet *packet, gfp_t gfp)
>>                       asoc->peer.last_sent_to = tp;
>>       }
>>       head->ignore_df = packet->ipfragok;
>> -     confirm = tp->dst_pending_confirm;
>> -     if (confirm)
>> +     if (tp->dst_pending_confirm)
>>               skb_set_dst_pending_confirm(head, 1);
>>       /* neighbour should be confirmed on successful transmission or
>>        * positive error
>>        */
>> -     if (tp->af_specific->sctp_xmit(head, tp) >= 0 && confirm)
>> +     if (tp->af_specific->sctp_xmit(head, tp) >= 0 &&
>> +         tp->dst_pending_confirm)
>>               tp->dst_pending_confirm = 0;
>>
>>  out:
>> --
>
>         I played safe here, I was not sure if currently
> or some day in the future the SCTP stack can allow another
> thread to set tp->dst_pending_confirm concurrently with the
> sending. My idea was only when skb was used to confirm
> neighbour only then to clear the indication. I guess, your
> patch is ok because we should be locking the socket
> everywhere.
Yeps, It's safe, as all the codes for dst_pending_confirm are
under the sock lock protection.

>
> Regards
>
> --
> Julian Anastasov <ja@....bg>