io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH] test/file-verify.t: Don't run over mlock limit when run as non-root
Date: Thu, 20 Apr 2023 13:04:43 -0600	[thread overview]
Message-ID: <168201748364.133109.2454297166789207140.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230420185728.4104-1-krisman@suse.de>


On Thu, 20 Apr 2023 14:57:28 -0400, Gabriel Krisman Bertazi wrote:
> test/file-verify tries to get 2MB of pinned memory at once, which is
> higher than the default allowed for non-root users in older
> kernels (64kb before v5.16, nowadays 8mb).  Skip the test for non-root
> users if the registration fails instead of failing the test.
> 
> 

Applied, thanks!

[1/1] test/file-verify.t: Don't run over mlock limit when run as non-root
      commit: b7f85996a5cb290fc2ad7d2f4d7341fc54321016

Best regards,
-- 
Jens Axboe




      reply	other threads:[~2023-04-20 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 18:57 [PATCH] test/file-verify.t: Don't run over mlock limit when run as non-root Gabriel Krisman Bertazi
2023-04-20 19:04 ` Jens Axboe [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=168201748364.133109.2454297166789207140.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).