[<prev] [next>] [day] [month] [year] [list]
Message-ID:
<SJ2PR01MB83456E99684DBBAAEAD7F9288E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
Date: Mon, 19 May 2025 12:05:55 +0000
From: Bharat Agrawal <bharat.agrawal@...ys.com>
To: Greg KH <gregkh@...uxfoundation.org>
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>,
"legion@...nel.org" <legion@...nel.org>
Subject: Re: mlock ulimits for SHM_HUGETLB
Thanks Greg for the response. RHEL has not been very helpful. I'm not looking to ask for patches because of the old versions.
These messages appear in production runs, raising concerns about possible failures. Thus, the question is: Can they be ignored safely?
Best,
Bharat
________________________________________
From: Greg KH <gregkh@...uxfoundation.org>
Sent: Monday, May 19, 2025 05:02 PM
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
[External Sender]
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