From: Greg KH <gregkh@linuxfoundation.org>
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>,
"liuzixian4@huawei.com" <liuzixian4@huawei.com>,
"mhocko@suse.com" <mhocko@suse.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>,
"legion@kernel.org" <legion@kernel.org>
Subject: Re: mlock ulimits for SHM_HUGETLB
Date: Mon, 19 May 2025 14:32:10 +0200 [thread overview]
Message-ID: <2025051946-ransack-number-e5e7@gregkh> (raw)
In-Reply-To: <SJ2PR01MB834507D46F44F65980FE09668E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
On Mon, May 19, 2025 at 12:04:58PM +0000, Bharat Agrawal wrote:
> 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?
Again, you are paying them for support for this, please use them, there
is nothing that the community can do to help out here, sorry.
greg k-h
next prev parent reply other threads:[~2025-05-19 12:32 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 [this message]
[not found] ` <SJ2PR01MB83451550F3A9C1636C9E50618E9CA@SJ2PR01MB8345.prod.exchangelabs.com>
2025-05-19 12:42 ` Bharat Agrawal
2025-05-19 14:02 ` Michal Hocko
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=2025051946-ransack-number-e5e7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bharat.agrawal@ansys.com \
--cc=hughd@google.com \
--cc=legion@kernel.org \
--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=mhocko@suse.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).