From: Mike Kravetz <mike.kravetz@oracle.com>
To: zhangyiru <zhangyiru3@huawei.com>, akpm@linux-foundation.org
Cc: hughd@google.com, linux-mm@kvack.org, liusirui@huawei.com,
liuzixian4@huawei.com, mhocko@suse.com, wuxu.wu@huawei.com
Subject: Re: [PATCH v8] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB
Date: Wed, 3 Nov 2021 10:19:36 -0700 [thread overview]
Message-ID: <d14533d8-eb49-9ac0-2f46-a1c452e82f0e@oracle.com> (raw)
In-Reply-To: <20211103105857.25041-1-zhangyiru3@huawei.com>
On 11/3/21 3:58 AM, zhangyiru wrote:
> commit 21a3c273f88c9cbbaf7e ("mm, hugetlb: add thread name and pid to
> SHM_HUGETLB mlock rlimit warning") marked this as deprecated in 2012,
> but it is not deleted yet.
>
> Mike says he still see that message in log files on occasion,
> so maybe we should preserve this warning.
>
> Also remove hugetlbfs related user_shm_unlock in ipc/shm.c and remove
> the user_shm_unlock after out.
>
> Signed-off-by: zhangyiru <zhangyiru3@huawei.com>
> ---
> Changelog:
> v8: modify !CONFIG_HUGETLBFS version of hugetlb_file_setup()
> v7: modify ucounts definition and remove the user_shm_unlock after out
> v6: fix errors in v5 and remove hugetlbfs related user_shm_unlock in
> ipc/shm.c
> v5: delete ucounts variable, and function calls that use ucounts in
> additon
> v4: modify context information of obsolete
> v3: modify warning message to obsolete
> v2: preserve warning message
> v1: remove mlock ulimit for SHM_HUGETLB
> ---
> fs/hugetlbfs/inode.c | 23 ++++++++---------------
> include/linux/hugetlb.h | 6 ++----
> ipc/shm.c | 8 +-------
> mm/memfd.c | 4 +---
> mm/mmap.c | 3 +--
> 5 files changed, 13 insertions(+), 31 deletions(-)
Thanks,
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
Andrew, the version you previously added to your tree (v4 I believe) has
an issue as reported by Hugh and should be replaced with this version.
Sorry!
--
Mike Kravetz
next prev parent reply other threads:[~2021-11-03 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 9:43 [PATCH v4] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB zhangyiru
2021-10-11 21:39 ` Mike Kravetz
2021-11-01 7:01 ` Hugh Dickins
2021-11-01 19:44 ` [PATCH v5] " zhangyiru
2021-11-01 21:09 ` [PATCH v6] " zhangyiru
2021-11-01 23:05 ` Mike Kravetz
2021-11-02 15:40 ` [PATCH v7] " zhangyiru
2021-11-02 19:46 ` Mike Kravetz
2021-11-03 10:58 ` [PATCH v8] " zhangyiru
2021-11-03 17:19 ` Mike Kravetz [this message]
2021-11-01 21:39 ` [PATCH v4] " Mike Kravetz
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=d14533d8-eb49-9ac0-2f46-a1c452e82f0e@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=liusirui@huawei.com \
--cc=liuzixian4@huawei.com \
--cc=mhocko@suse.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).