netdev - Re: [pve-devel] bridge vlan range, kernel 4.1 : "message truncated" warning when too much vlans defined

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] [day] [month] [year] [list]

Message-ID: <55F21A2B.6070205@cumulusnetworks.com>
Date:	Thu, 10 Sep 2015 17:02:51 -0700
From:	roopa <roopa@...ulusnetworks.com>
To:	David Miller <davem@...emloft.net>
CC:	aderumier@...so.com, ronen.arad@...el.com, netdev@...r.kernel.org,
	rami.rosen@...el.com
Subject: Re: [pve-devel] bridge vlan range, kernel 4.1 : "message truncated"
 warning when too much vlans defined

On 9/10/15, 3:58 PM, David Miller wrote:
> From: roopa <roopa@...ulusnetworks.com>
> Date: Thu, 10 Sep 2015 15:26:30 -0700
>
>> On 9/9/15, 11:40 PM, Alexandre DERUMIER wrote:
>>> Hi,
>>>
>>> This still not fixed in iproute 4.2.
>>>
>>> Is they any plan to increase the rtnl_dump_filter buffer size soon ?
>> Instead of increasing the default size, it would be nicer if this was
>> configurable for iproute2 (I haven't looked yet).
> I would definitely prefer this be done in a run-time manner of some
> sort, and then other libraries can use iproute2's logic as a reference
> for how to deal with this reliably, properly, and in a %100
> future-proof manner.
>
> Something of the "if request X fails, double the buffer size" variety.
agreed. This would be ideal. libnl already handles it this way.
We have to move iproute2 recv buffer to dynamic allocation and also 
realloc on MSG_TRUNC.

I can get to it one of these days unless somebody beats me to it.

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