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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54D9EC2D0CD for ; Mon, 19 May 2025 11:33:00 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6F5876B00C8; Mon, 19 May 2025 07:32:58 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 6A4136B00CF; Mon, 19 May 2025 07:32:58 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5455C6B00D0; Mon, 19 May 2025 07:32:58 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 3225B6B00C8 for ; Mon, 19 May 2025 07:32:58 -0400 (EDT) Received: from smtpin22.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id A1617121DCB for ; Mon, 19 May 2025 11:32:58 +0000 (UTC) X-FDA: 83459445636.22.41FE19A Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf19.hostedemail.com (Postfix) with ESMTP id BFD411A0010 for ; Mon, 19 May 2025 11:32:56 +0000 (UTC) Authentication-Results: imf19.hostedemail.com; dkim=pass header.d=linuxfoundation.org header.s=korg header.b=Gq6O6PKY; dmarc=pass (policy=none) header.from=linuxfoundation.org; spf=pass (imf19.hostedemail.com: domain of gregkh@linuxfoundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1747654377; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=SvlqHkZNGLneZqb7S0dNG1vXakx784N/G/uNvx2jtM4=; b=ey5J6wkpz3TMD8TykEYfFLxenVUOcQDB5z6SwYlu1r2H2bxO4/6gGAC2ijmkDJVPe8NG7B bdXOH6qMnEkyYDQ19p/6jVIYG9/DmfplR+idEbD4cteuuoxbYylnMVpzA9Bx1uKnBe5Mia rXJSoy57cWiHfR54HI3qF69zq7jBEkU= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1747654377; a=rsa-sha256; cv=none; b=w2y072YGlShg8JXkG6bWitwTu9qOpDClFwoYIzYxVbKJA4SOo5o/3r1SIEZVCeVqcC7Ulf 3O6RULWHATBnb4a1rQ+jZqSB545ivkC44k1Mz/Jxd9bzDa9+5fi4MxgmXWbwMhVwfaUUZv MlUB1MRVBhsRvsDQMoww3b1Y9bxjXYo= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=pass header.d=linuxfoundation.org header.s=korg header.b=Gq6O6PKY; dmarc=pass (policy=none) header.from=linuxfoundation.org; spf=pass (imf19.hostedemail.com: domain of gregkh@linuxfoundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 6FFCE5C40BC; Mon, 19 May 2025 11:30:38 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02B44C4CEE4; Mon, 19 May 2025 11:32:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1747654375; bh=aQ5zhyux3hMftcqOWcrOoFPGZ5RyMdC2sTKMO2fu8ic=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Gq6O6PKYeAQcvV6EUmG+lkZZxnpfKbKLHxF8IJWIhFf8W1MUuxAYq2hkSXISmF6TS yNfSO+CjwWMx9hMXwvqst1dmrjBO4R3ToInAwlhkmOJiB/vGpJV7Q+t3eWWJ8dzdyc UTnUrapKRdE77dQN35hB/HieWx59bi7zLV+5JWZo= Date: Mon, 19 May 2025 13:32:52 +0200 From: Greg KH To: Bharat Agrawal Cc: "hughd@google.com" , "akpm@linux-foundation.org" , "rientjes@google.com" , "zhangyiru3@huawei.com" , "liuzixian4@huawei.com" , "mhocko@suse.com" , "wuxu.wu@huawei.com" , "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-api@vger.kernel.org" , "linux-mm@kvack.org" Subject: Re: mlock ulimits for SHM_HUGETLB Message-ID: <2025051914-bounding-outscore-4d50@gregkh> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Stat-Signature: kgy33weoby1ts67izzsfhy3yc4k5w8dh X-Rspam-User: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: BFD411A0010 X-HE-Tag: 1747654376-897998 X-HE-Meta: U2FsdGVkX1+RdMG3nokFLqCKhq+eWF+hBNd+PpWq9MXa0wVNfk5MXZ0hETcerKyF+220c5pjYyhG7eOlxo2UXtvE6+znYOz8/owqD+7mfTk8AMIN/ClMW2iK0ZoRTerFRYiuYsXJy8qcwxyuqOe80txIEaxZ9+ivd0cHJy0Dmyz8bsMpMoubv+Y1yBgdhD9iiCcuU9EdjFsdNRSPXlGFjG2XsZWVXhp6ZmlR+oAPPdWPh2hmBKH94V7/gPWcmH52AHzLo+jRT9QB+DjYBcwB1h/mB143kEPXERyi0n5cY4r5rQ08kStFMOcEO611iMZXHThGRpEUiUQCsQdSy7xgAeJz2cZr45e7fqN321d1KDiG4GZ9hKq8DvwU67MC7pJ8DdwnewNqkGTvTf2xCXNm3sXM+gEuF9QwUysUTPAhuPw7HGGiKYAK9rdVCJwjpaPxGHYrmopZP13kM5uE8vpcGac4PObvzdgyFIzuctejAHPCGe7U9QojJsQ1BKQcsQ7nPNhwillKuWA9eqI3YT7VXw3nspGeKsv3WjA90poKhWtfFX5QCr5K3ilecusd1/5gtVh2rmD2RvJhANPUSiGRKCaGrhH123XqCaxuMWizPqEyl3S+vtawEIdnCrIW+BQVUv29VPRp6Jtkqsl0b4XWUeD5An25w0TCH0llW30lD6f++D/74gZp991RUeri5xlMQ20YF/J7UMHRslT6925gIXEKUQQY/idUjfeBYqD7HB+ob+4ENgTwUiLI1REiVzdqHTxH89ouFflti9t6EK82dMS6g9/vubaWcFJ0nuUj1j5rSMztGQWG2TjMGrOkDm2G5yFnWOzRTDoBiOi/Kj6p0P7TKYmani8FpjbCO+TWTlcWFzzIPNMmP+EzGNgUj20IpS6C8wdtFeTHA8itAEHKfhMEYGBkETdR6wZqgyCCyU3OC/w6wdvRSe/56UrdpsZTPL842W20n+dwzNIVinf nYhrPxhD q78cZ4RgusrWtuWssiWidx1G16fJF4V0nb8cahGyknBorKpXsEqJbzBcgCVM6IvKmH4g8rjxmeSxzfzS7GFZUuWTSEOPuxtxH2u4UUQ+CXyb5qQbtF/IxSitiZVXA89Ttx9Y0t4fZvZxOL/8Lhb7Tdcz3+TmS25J4toKfoYWfBu2SwtWU5MYDyiwhXjwfYkBkjq+7GmDV6aVCS3+8U1dX2SQzIcU6Jmnbg1HarHQE00yZnfNg25SleUWah5Q6oY2/DRMCuhclvUzs/+op++5XeDbd+S0ZJOqaWP7e674fzg4YJB88J3+6PsD0RAnxQ3SOgl29Cr4wpQW78SoZ1oXzz92cP2uGzxn4TFTlegH8ifw3wnY5/buHPQR+DJPON9bifnuk0YZNBuUE6m78NC8bYQwJZ2+KHrCugKpdLl8LEmWwu+uxI1qWtvDgbA== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: 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