[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025051914-bounding-outscore-4d50@gregkh>
Date: Mon, 19 May 2025 13:32:52 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Bharat Agrawal <bharat.agrawal@...ys.com>
Cc: "hughd@...gle.com" <hughd@...gle.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"rientjes@...gle.com" <rientjes@...gle.com>,
"zhangyiru3@...wei.com" <zhangyiru3@...wei.com>,
"liuzixian4@...wei.com" <liuzixian4@...wei.com>,
"mhocko@...e.com" <mhocko@...e.com>,
"wuxu.wu@...wei.com" <wuxu.wu@...wei.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: mlock ulimits for SHM_HUGETLB
On Mon, May 19, 2025 at 10:23:33AM +0000, 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?
Why not ask RHEL support, given that you are paying them for that in
order to be using that kernel version, right?
Also note that 4.18.y is VERY old and obsolete and not supported by the
community at all.
Good luck!
greg k-h
Powered by blists - more mailing lists