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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAM1L+iDUXKSMndnyS+TM3brjxFQU5a0ZRN-SW0JMKLJ+B23OaA@mail.gmail.com>
Date:	Thu, 20 Aug 2015 11:21:01 +0530
From:	tej parkash <parkash.tej@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: netlink_route kernel data dump size increased

On Thu, Aug 20, 2015 at 2:47 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> 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.

Ok, let me see if I could find related fix in later kernels.  If you
have any other pointers here please let me know.

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


Are you saying that we should bring back the fix to 3.10 kernel rather
increasing user space buffer size to 16KB. I assume that would be
right way to handle it. But do we have any issue if we just increase
the buffer size to 16KB (e.g without fix, 16KB may also not be
sufficient sometime, etc)


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