netdev - Re: netlink_route kernel data dump size increased

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: <1440019047.6610.35.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Wed, 19 Aug 2015 14:17:27 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	tej parkash <parkash.tej@...il.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: netlink_route kernel data dump size increased

On Wed, 2015-08-19 at 23:41 +0530, tej parkash wrote:
> All,
> 
> We are running application on Linux Kernel 3.10 to collect network
> interface information using  NETLINK_ROUTE protocol. earlier (kernel
> 2.6.32) we were having 8K buffer allocated to collect all data but
> with new kernel (3.10) we are seeing read socket error, as buffer size
> is not sufficient for all network dump data.
> 
> We want to understand that if the userspace buffer limit increased to
> 16K or we need some other mechanism to collect the data in 8K chuck.
> or Is there any other way application can use NETLINK_ROUTE  protocol,
> so that it will not break the application if data size gets increased
> in future.
> 
> I did some some browsing and found some link but they were not very conclusive.
> http://www.spinics.net/lists/netdev/msg162185.html
> 
> Appreciate for any kind of help or pointers here
> 

This sounds like a bug that might have been fixed later.

User space is not required to switch to 16KB, although it is recommended
to reduce number of syscalls.


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