All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
	Vidra.Jonas@seznam.cz, linux-parisc@vger.kernel.org
Subject: Re: Possible io_uring bug in PA-RISC kernel 6.1.46
Date: Mon, 28 Aug 2023 02:45:33 +0100	[thread overview]
Message-ID: <875y50gcrz.fsf@gentoo.org> (raw)
In-Reply-To: <f8be4af4-725a-902f-60a5-0f18c198b130@gmx.de>


Helge Deller <deller@gmx.de> writes:

> On 8/27/23 22:35, John David Anglin wrote:
>> On 2023-08-27 7:25 a.m., Vidra.Jonas@seznam.cz wrote:
>>> 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.)
>> I have the attached io_uring patch on 6.1.46.  It's back ported from 6.4.
>>
>> libuv make check was successful on my system.
>
> Did the libuv check failed on 6.1.46 for you?
> I just tried plain 6.1.49 and my machine crashed....
>

I can't test 6.1.x right now, but fwiw, 6.4.12 passes libuv's test suite.

best,
sam

  parent reply	other threads:[~2023-08-28  1:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27 11:25 Possible io_uring bug in PA-RISC kernel 6.1.46 Vidra.Jonas
2023-08-27 15:09 ` Helge Deller
2023-08-27 20:35 ` John David Anglin
2023-08-27 20:41   ` Helge Deller
2023-08-27 21:01     ` John David Anglin
2023-08-27 21:31       ` John David Anglin
2023-08-27 21:41         ` Helge Deller
     [not found]           ` <1wd.NvQz.Gj}B593TXc.1azrF9@seznam.cz>
     [not found]             ` <1xN.NvP9.1{VV8Csbz0.1azrZI@seznam.cz>
2023-09-05 17:12               ` Vidra.Jonas
     [not found]                 ` <1M4b1y-1qfpu42R6s-001mPw@mail.gmx.net>
2023-09-09  6:11                   ` Vidra.Jonas
2023-08-28  1:45     ` Sam James [this message]
2023-08-27 21:23 ` Sam James
2023-08-31 13:38 ` Helge Deller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y50gcrz.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=Vidra.Jonas@seznam.cz \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.