netdev - Re: IPoIB: Fix multicast packet drops before join is complete

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]

Message-ID: <15ddcffd0906110445x25e2b2c5qa8445e0e1b344ef4@mail.gmail.com>
Date:	Thu, 11 Jun 2009 14:45:28 +0300
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	rdreier@...co.com, cl@...ux-foundation.org, netdev@...r.kernel.org,
	yosefe@...taire.com
Subject: Re: IPoIB: Fix multicast packet drops before join is complete

On Wed, Jun 10, 2009 at 3:01 PM, David Miller<davem@...emloft.net> wrote:
> From: Or Gerlitz <or.gerlitz@...il.com>

>> for --unicast-- the same problem [...] will come into play under both Ethernet and IB,
>> so the user is limited by the socket buffer len and the neigh unres_qlen systcl.

> But this generally does not cause problems via ARP, why might that be?
> Because resolution is 1) rare 2) quick.  Both of which do not apply to this IPoIB case.

To be precise, I don't see why ARP resolution is more rare then
joining to a multicast
group on behalf of a sender in IPoIB, they both happen on the first
and if/when the kernel
deletes the neighbour.

> Sure, but that's just pushing the problem around instead of solving it.

Let me think about it more.

Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html