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-next>] [day] [month] [year] [list]
Message-ID: <49AF2871.10804@nortel.com>
Date:	Wed, 04 Mar 2009 19:18:41 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	"David S. Miller" <davem@...emloft.net>,
	Linux Network Development list <netdev@...r.kernel.org>
Subject: question on netlink_overrun()

Hi all,

Currently we set netlink_overrun() on the socket in both the unicast and 
broadcast paths.  If I understand things correctly this should result in 
the receiver getting ENOBUFS the next time they try a socket-related 
syscall.

However, in the netlink_dump() code we don't call it--was this an 
oversight or an intentional design decision?

I have a userspace app that would like to know if it ran out of buffer 
space in the receive socket (and hence lost some packets) while dumping 
SA information in xfrm_user_rcv_msg().

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ