From: Michal Hocko <mhocko@suse.com>
To: Bharat Agrawal <bharat.agrawal@ansys.com>
Cc: "hughd@google.com" <hughd@google.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"rientjes@google.com" <rientjes@google.com>,
"zhangyiru3@huawei.com" <zhangyiru3@huawei.com>,
"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"liuzixian4@huawei.com" <liuzixian4@huawei.com>,
"wuxu.wu@huawei.com" <wuxu.wu@huawei.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: mlock ulimits for SHM_HUGETLB
Date: Mon, 19 May 2025 16:02:51 +0200 [thread overview]
Message-ID: <aCs6C2vKbecx-boy@tiehlicka> (raw)
In-Reply-To: <SJ2PR01MB8345DF192742AC4DB3D2CBB78E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
Hi,
On Mon 19-05-25 10:21:17, Bharat Agrawal wrote:
> Hi all,
>
> Could anyone please help comment on the risks associated with an
> application throwing the "Using mlock ulimits for SHM_HUGETLB is
> deprecated" message on RHEL 8.9 with 4.18.0-513.18.1.el8_9.x86_64
> Linux kernel?
This is not RHEL specific behavior. The current Linus tree has the same
warning which has been added by
: commit 2584e517320bd48dc8d20e38a2621a2dbe58fade
: Author: Ravikiran G Thirumalai <kiran@scalex86.org>
: Date: Tue Mar 31 15:21:26 2009 -0700
:
: mm: reintroduce and deprecate rlimit based access for SHM_HUGETLB
:
: Allow non root users with sufficient mlock rlimits to be able to allocate
: hugetlb backed shm for now. Deprecate this though. This is being
: deprecated because the mlock based rlimit checks for SHM_HUGETLB is not
: consistent with mmap based huge page allocations.
:
: Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>
: Reviewed-by: Mel Gorman <mel@csn.ul.ie>
: Cc: William Lee Irwin III <wli@holomorphy.com>
: Cc: Adam Litke <agl@us.ibm.com>
: Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
: Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
HTH
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2025-05-19 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ2PR01MB8345DF192742AC4DB3D2CBB78E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
2025-05-19 10:23 ` mlock ulimits for SHM_HUGETLB Bharat Agrawal
2025-05-19 11:32 ` Greg KH
[not found] ` <SJ2PR01MB834507D46F44F65980FE09668E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
2025-05-19 12:05 ` Bharat Agrawal
2025-05-19 12:32 ` Greg KH
[not found] ` <SJ2PR01MB83451550F3A9C1636C9E50618E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
2025-05-19 12:42 ` Bharat Agrawal
2025-05-19 14:02 ` Michal Hocko [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=aCs6C2vKbecx-boy@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bharat.agrawal@ansys.com \
--cc=hughd@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuzixian4@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=rientjes@google.com \
--cc=wuxu.wu@huawei.com \
--cc=zhangyiru3@huawei.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;
as well as URLs for NNTP newsgroup(s).