On 2/15/23 12:00?PM, Jens Axboe wrote: > accept.t: setsockopt(fd, SOL_SOCKET, SO_REUSEADDR, &val, sizeof(val)); > fails here, no idea why. I'm wrong on this one, it's actually opening a socket with O_NONBLOCK that fails with EINVAL, and then we pass -1 to the above. I saw something on boot on O_NONBLOCK being the wrong value (I think from systemd), so maybe another case of userspace and the kernel not agreeing on what values flags/errno has? In any case, with the silly syzbot mmap stuff fixed up, I'm not seeing anything odd. A few tests will time out as they simply run too slowly emulated for me, but apart from that, seems fine. This is running with Helge's patch, though not sure if that is required running emulated. -- Jens Axboe
