I doubt it's a kernel bug. valgrind probably just doesn't realize
that getsockopt initialized the variable.
On Fri, Aug 26, 2011 at 05:05:03PM -0700, Ethan Jackson wrote:
> I wonder if it's a bug with the syscall on my system or something? Is
> it possible that getsockopt isn't initializing rcvbu
I wonder if it's a bug with the syscall on my system or something? Is
it possible that getsockopt isn't initializing rcvbuf though it should
be?
Ethan
On Fri, Aug 26, 2011 at 17:03, Ben Pfaff wrote:
> I guess that's really a valgrind bug, but the fix is OK with me.
>
I guess that's really a valgrind bug, but the fix is OK with me.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
---
lib/socket-util.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/socket-util.c b/lib/socket-util.c
index c436724..2d554ac 100644
--- a/lib/socket-util.c
+++ b/lib/socket-util.c
@@ -222,7 +222,7 @@ int
drain_rcvbuf(int fd)
{
socklen_t rcvbuf_len;
-size_
