linux-kernel - Re: [PATCH] Increase default MLOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <CFTL5A99FTIY.38WS1HS59BT2D@taiga>
Date:   Fri, 19 Nov 2021 08:41:58 +0100
From:   "Drew DeVault" <sir@...wn.com>
To:     "Andrew Morton" <akpm@...ux-foundation.org>,
        "Jens Axboe" <axboe@...nel.dk>
Cc:     "Johannes Weiner" <hannes@...xchg.org>,
        "Ammar Faizi" <ammarfaizi2@...weeb.org>,
        <linux-kernel@...r.kernel.org>, <linux-api@...r.kernel.org>,
        "io_uring Mailing List" <io-uring@...r.kernel.org>,
        "Pavel Begunkov" <asml.silence@...il.com>, <linux-mm@...ck.org>
Subject: Re: [PATCH] Increase default MLOCK_LIMIT to 8 MiB

On Thu Nov 18, 2021 at 10:58 PM CET, Andrew Morton wrote:
> Nobody's aiming for perfection. We're discussing aiming for "better".
>
> What we should have done on day one was to set the default MLOCK_LIMIT
> to zero bytes. Then everyone would have infrastructure to tune it from
> userspace and we wouldn't ever have this discussion.

Setting aside perfection or not, what you're aiming for is about 1000×
more work. I'm not prepared to do that work. I'm not going to paint this
same bikeshed 100 times for each Linux distro we have to convince to
adopt a more sophisticated solution.