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: <2bf18f5b-9539-e706-b887-3de330950061@gmail.com>
Date: Mon, 17 Jul 2023 13:34:04 +0100
From: Pavel Begunkov <asml.silence@...il.com>
To: Hangbin Liu <liuhangbin@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: selftest io_uring_zerocopy_tx.sh failed on VM

On 7/17/23 05:11, Hangbin Liu wrote:
> Hi Pavel,
> 
> I tried to run test selftest io_uring_zerocopy_tx.sh on VM, but it failed
> with error like
> 
> + ip netns exec ns-45iLeE2 ./msg_zerocopy -4 -t 2 -C 2 -S 192.168.1.1 -D 192.168.1.2 -r udp
> cpu: unable to pin, may increase variance.
> + ip netns exec ns-45iLeE1 ./io_uring_zerocopy_tx -4 -t 1 -D 192.168.1.2 -m 1 -t 1 -n 32 udp
> ./io_uring_zerocopy_tx: io_uring: queue init: Unknown error -13
> 
> Do you know what's the reason? Should we update the test script to return
> SKIP if io_uring init failed?

I don't recall anything that can fail ring init with EACCES, probably
sth in your system disables io_uring with some syscall filters or so.
I think skipping the trace on EACCES is the right approach. Do you want
to send a patch?
Apart from that, if you're curious you can try to trace what's going on,
ftrace should give an idea.

-- 
Pavel Begunkov

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ