Re: Possible io_uring bug in PA-RISC kernel 6.1.46

[Sam James <sam@gentoo.org>]

<Vidra.Jonas@seznam.cz> writes:

> Hello,
>
> on my C8000 workstation, I'm getting libuv aborts connected to io_uring
> usage. I'm not sure whether this is a libuv bug or a kernel one, but
> since libuv is pretty well tested on other archs, it's probably a
> PA-RISC issue. I've encountered the problem in kernel versions 6.1.41
> and 6.1.46. 6.1.4 seemed fine, but I updated other system packages in
> the meantime, so I can't be sure.
>
> The issue is that a call to
> `io_uring_enter(fd, 2, 2, IORING_ENTER_GETEVENTS)`
> returns 0, and libuv reacts to that by aborting, probably on this line:
> https://github.com/libuv/libuv/blob/65dc822d6c20a9130fa100c7b46d751f8cf4d233/src/unix/linux.c#L1252
> (I'm saying probably, because gdb seems to be buggy on my machine and I
> don't really trust its output, so I rely on strace instead, but that
> doesn't support backtraces on the PA-RISC.)

* elfutils needs me to finish off the port - I have some old patches
rebased.

* I wasn't aware of libunwind being broken (you mentioned it on IRC)
though.

* Can you file a bug for your gdb issue at
  https://sourceware.org/bugzilla? so far I've tried and I can't
  reproduce any problems with it