netdev - Re: [PATCH] igmp: Make igmp group member RFC 3376 compliant

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20161107.201345.1974283028907025304.davem@davemloft.net>
Date:   Mon, 07 Nov 2016 20:13:45 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     mtesar@...hat.com
Cc:     kuznet@....inr.ac.ru, jmorris@...ei.org, kaber@...sh.net,
        netdev@...r.kernel.org
Subject: Re: [PATCH] igmp: Make igmp group member RFC 3376 compliant

From: Michal Tesar <mtesar@...hat.com>
Date: Thu, 3 Nov 2016 10:38:34 +0100

>  2. If the received Query is a General Query, the interface timer is
>     used to schedule a response to the General Query after the
>     selected delay.  Any previously pending response to a General
>     Query is canceled.
> --8<--
> 
> Currently the timer is rearmed with new random expiration time for
> every incoming query regardless of possibly already pending report.
> Which is not aligned with the above RFE.

I don't read it that way.  #2 says if this is a general query then any
pending response to a general query is cancelled.  And that's
effectively what the code is doing right now.