From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 463FBC433FE for ; Wed, 24 Nov 2021 15:34:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241314AbhKXPhU (ORCPT ); Wed, 24 Nov 2021 10:37:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35080 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241279AbhKXPhU (ORCPT ); Wed, 24 Nov 2021 10:37:20 -0500 Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C3044C061714 for ; Wed, 24 Nov 2021 07:34:10 -0800 (PST) Received: by mail-qv1-xf2a.google.com with SMTP id g9so101034qvd.2 for ; Wed, 24 Nov 2021 07:34:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=jewS1/U+Uwx2MsMSvVTsbDbxDhtWEO2xK/fTTXK8uck=; b=WzvFRKZ061/KNaexoESH+Gbb4RgMMBXdqHhbtVDCJUWaGKS0bnX4c6P4VO4hkjahGS /3zHBhDb+rJ4bQfUU/5o0p7g5Oq4oHvasOY5UeFTNeegJ14CkGmQ0rO3rB12VPpaJpFR gChu8p5mtj04YG1x5v/Js2Wxkzh4Wbj7B3fohbz2UoOYCEyU/TDOBZLuXavFMULGkfTJ GjZzuFZNy3a1tQgtuifVOgbMoqA9TPXpZeM+Et1sowb/lyMJrVJ9CxBCNCSSNl79GP0A zTttDgOQkS2aqHt73ydZLqX6ZPRNdxo6YgMiQtSBwlqc06vXom0vpQ6CnRifIvQ6aw7l EeRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=jewS1/U+Uwx2MsMSvVTsbDbxDhtWEO2xK/fTTXK8uck=; b=H/Twp4ZnFBpevxoT2YoNuKTP6o0kJxKH+yd41eXXYWGLQcGXi7WEiiohfSww7/fUB2 nxFFojElMWU9vkKScjBkwjePPGCKMUSBE4WTI+i79/UeOgOlVnny+pzD3lnHXhorzrXy OpMAcMmKGzOGYh7i/ZGoqCPhmlQ4MOFW8aphfT/eNsss4I507jpK/L/rS9El+EyRTPFl 2Z9qzgU1iX9qXN+MG6FIYeozBjd3/SKzXkyFMqh06TsJc7NnMQ5XIo/mXvXWKBWXjt/j T3U3utnkbpSlogQkNl18XW9SpTeE3oku6UKpvjqSOP8wOxJ7If/bFhfOAZ4kECrm+mYU ZaOQ== X-Gm-Message-State: AOAM531kn290BGzSTPZfaTkVlUwGtADzPnXrSeuW8xwFSW8BQII6cPaZ 1HVXwOb/uMFCjNTq7fyCiWHOEg== X-Google-Smtp-Source: ABdhPJxZDhSiT7D5AMdmLtkaSczYkt5IgUp2uFeWHEYmNkWlb9JcYltzAKN/FqypiDM3IlbZxasu5A== X-Received: by 2002:ad4:5dea:: with SMTP id jn10mr8349179qvb.17.1637768049952; Wed, 24 Nov 2021 07:34:09 -0800 (PST) Received: from ziepe.ca (hlfxns017vw-142-162-113-129.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.113.129]) by smtp.gmail.com with ESMTPSA id l22sm42040qtj.68.2021.11.24.07.34.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Nov 2021 07:34:06 -0800 (PST) Received: from jgg by mlx with local (Exim 4.94) (envelope-from ) id 1mpuHd-0013L9-Or; Wed, 24 Nov 2021 11:34:05 -0400 Date: Wed, 24 Nov 2021 11:34:05 -0400 From: Jason Gunthorpe To: David Hildenbrand Cc: Vlastimil Babka , Jens Axboe , Andrew Dona-Couch , Andrew Morton , Drew DeVault , Ammar Faizi , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, io_uring Mailing List , Pavel Begunkov , linux-mm@kvack.org Subject: Re: [PATCH] Increase default MLOCK_LIMIT to 8 MiB Message-ID: <20211124153405.GJ5112@ziepe.ca> References: <20211123170056.GC5112@ziepe.ca> <20211123235953.GF5112@ziepe.ca> <2adca04f-92e1-5f99-6094-5fac66a22a77@redhat.com> <20211124132353.GG5112@ziepe.ca> <20211124132842.GH5112@ziepe.ca> <20211124134812.GI5112@ziepe.ca> <2cdbebb9-4c57-7839-71ab-166cae168c74@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2cdbebb9-4c57-7839-71ab-166cae168c74@redhat.com> Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Wed, Nov 24, 2021 at 03:14:00PM +0100, David Hildenbrand wrote: > I'm not aware of any where you can fragment 50% of all pageblocks in the > system as an unprivileged user essentially consuming almost no memory > and essentially staying inside well-defined memlock limits. But sure if > there are "many" people will be able to come up with at least one > comparable thing. I'll be happy to learn. If the concern is that THP's can be DOS'd then any avenue that renders the system out of THPs is a DOS attack vector. Including all the normal workloads that people run and already complain that THPs get exhausted. A hostile userspace can only quicken this process. > My position that FOLL_LONGTERM for unprivileged users is a strong no-go > stands as it is. As this basically excludes long standing pre-existing things like RDMA, XDP, io_uring, and more I don't think this can be the general answer for mm, sorry. Sure, lets stop now since I don't think we can agree. Jason