public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Andres Freund <[email protected]>, Jens Axboe <[email protected]>,
	[email protected]
Subject: Re: io_uring_setup spuriously returning ENOMEM for one user
Date: Thu, 16 Jul 2020 23:12:41 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 16/07/2020 23:05, Andres Freund wrote:
> Hi,
> 
> While testing the error handling of my uring using postgres branch I
> just encountered the situation that io_uring_setup() always fails with
> ENOMEN.
> 
> It only does so for the user I did the testing on and not for other
> users. During the testing a few io_uring using processes were kill -9'd
> and a few core-dumped after abort(). No io_uring using processes are
> still alive.
> 
> As the issue only happens to the one uid I suspect that
> current_user()->locked_mem got corrupted, perhaps after hitting the
> limit for real.

Any chance it's using SQPOLL mode?

> 
> Unfortunately I do not see any way to debug this without restarting. It
> seems the user wide limit isn't exported anywhere? I found
> uids_sysfs_init() while grepping around, but it seems that's just a
> leftover.
> 
> This happened on 07a56bb875afbe39dabbf6ba7b83783d166863db / 5.8rc5 +
> 16. I left the machine running for now, in case there's something that
> can be debugged while running. But I've to restart it in a bit. It took
> a while to hit this issue, unfortunately.
> 

-- 
Pavel Begunkov

  reply	other threads:[~2020-07-16 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 20:05 io_uring_setup spuriously returning ENOMEM for one user Andres Freund
2020-07-16 20:12 ` Pavel Begunkov [this message]
2020-07-16 20:20   ` Andres Freund
2020-07-16 20:31     ` Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox