On 2/20/20 9:17 AM, Jens Axboe wrote: > On 2/20/20 7:19 AM, Glauber Costa wrote: >> Hi there, me again >> >> Kernel is at 043f0b67f2ab8d1af418056bc0cc6f0623d31347 >> >> This test is easier to explain: it essentially issues a connect and a >> shutdown right away. >> >> It currently fails due to no fault of io_uring. But every now and then >> it crashes (you may have to run more than once to get it to crash) >> >> Instructions are similar to my last test. >> Except the test to build is now "tests/unit/connect_test" >> Code is at git@xxxxxxxxxx:glommer/seastar.git branch io-uring-connect-crash >> >> Run it with ./build/release/tests/unit/connect_test -- -c1 >> --reactor-backend=uring >> >> Backtrace attached > > Perfect thanks, I'll take a look! Haven't managed to crash it yet, but every run complains: got to shutdown of 10 with refcnt: 2 Refs being all dropped, calling forget for 10 terminate called after throwing an instance of 'fmt::v6::format_error' what(): argument index out of range unknown location(0): fatal error: in "unixdomain_server": signal: SIGABRT (application abort requested) Not sure if that's causing it not to fail here. -- Jens Axboe
