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
| ||
|
Message-Id: <20170313.171008.1845413549443399902.davem@davemloft.net> Date: Mon, 13 Mar 2017 17:10:08 -0700 (PDT) From: David Miller <davem@...emloft.net> To: johunt@...mai.com Cc: edumazet@...gle.com, arnd@...db.de, soheil@...gle.com, willemb@...gle.com, pabeni@...hat.com, linux-arch@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [RFC PATCH] sock: add SO_RCVQUEUE_SIZE getsockopt From: Josh Hunt <johunt@...mai.com> Date: Mon, 13 Mar 2017 18:34:41 -0500 > In this particular case they really do want to know total # of bytes > in the receive queue, not the data bytes they can consume from an > application pov. The kernel currently only exposes this value through > netlink or /proc/net/udp from what I saw. Can you explain in what way this is useful? The difference between skb->len and skb->truesize is really kernel internal implementation detail, and I'm trying to figure out why this would be useful to an application.
Powered by blists - more mailing lists