netdev - Re: [PATCH V4 net-next] neigh: new unresolved queue limits

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:	Wed, 09 Nov 2011 16:21:37 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH V4 net-next] neigh: new unresolved queue limits

From: David Miller <davem@...emloft.net>
Date: Wed, 09 Nov 2011 16:16:44 -0500 (EST)

> From: Eric Dumazet <eric.dumazet@...il.com>
> Date: Wed, 09 Nov 2011 12:14:09 +0100
> 
>> unres_qlen is the number of frames we are able to queue per unresolved
>> neighbour. Its default value (3) was never changed and is responsible
>> for strange drops, especially if IP fragments are used, or multiple
>> sessions start in parallel. Even a single tcp flow can hit this limit.
>  ...
> 
> Ok, I've applied this, let's see what happens :-)

Early answer, build fails.

Please test build this patch with DECNET enabled and resubmit.  The
decnet neigh layer still refers to the removed ->queue_len member.

Thanks.
--
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