netdev - Re: Single socket with TX_RING and RX

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] [day] [month] [year] [list]

Message-ID: <loom.20130522T212418-499@post.gmane.org>
Date:	Wed, 22 May 2013 19:36:34 +0000 (UTC)
From:	Ricardo Tubío <rtpardavila@...il.com>
To:	netdev@...r.kernel.org
Subject: Re: Single socket with TX_RING and RX_RING

Paul Chavent <paul.chavent <at> fnac.net> writes:

> 
> Hi.
> 
> As stated before, you should call mmap only once.
> 
> Paul.
> 

Hi Paul,

I think that you must check the return value of the call that you make to
"setsockopt()", especially for the second call. The first one returns 0,
this is, the "setsockopt()" call was executed correctly. However, the second
one returns -16 ("EBUSY" value), this is, the call to "setsockopt()" was not
executed correctly.

So, could you modify your calls to "setsockopt()" and check whether the
return value is 0 (correct execution) or -16 (EBUSY, incorrect execution)?

Best, Cardo.

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