Re: [PATCH] generic/233,270: unlimit the max locked memory size for io_uring

Eryu Guan
2021-02-07T16:32:10Z

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