From: Eryu Guan <guan@eryu.me>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/233,270: unlimit the max locked memory size for io_uring
Date: Mon, 8 Feb 2021 00:31:07 +0800 [thread overview]
Message-ID: <20210207163107.GI2350@desktop> (raw)
In-Reply-To: <20210127072143.247849-1-zlang@redhat.com>
On Wed, Jan 27, 2021 at 03:21:43PM +0800, Zorro Lang wrote:
> The ltp/fsstress always fails on io_uring_queue_init() by returnning
> ENOMEM. Due to io_uring accounts memory it needs under the rlimit
> memlocked option, which can be quite low on some setups, especially
> on 64K pagesize machine. root isn't under this restriction, but
> regular users are. So only g/233 and g/270 which use $qa_user to run
> fsstress are failed.
>
> To avoid this failure, set max locked memory to unlimited before doing
> fsstress, then restore it after test done.
I'm wondering if we could just set 'ulimit -l unlimited' in check? so
all tests inherits the unlimited mlock setting. For root, this doesn't
change anything, but command runs by regular user could get unlimited
lockable memory. And new tests won't have to worry about running
fsstress/fsx as $qa_user.
Thanks,
Eryu
prev parent reply other threads:[~2021-02-07 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 7:21 [PATCH] generic/233,270: unlimit the max locked memory size for io_uring Zorro Lang
2021-01-27 23:43 ` Darrick J. Wong
2021-01-28 3:02 ` Zorro Lang
2021-01-31 15:24 ` Eryu Guan
[not found] ` <20210131163412.GZ14354@localhost.localdomain>
2021-02-07 16:23 ` Eryu Guan
2021-02-07 16:31 ` Eryu Guan [this message]
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=20210207163107.GI2350@desktop \
--to=guan@eryu.me \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.com \
/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