linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: zhangyiru <zhangyiru3@huawei.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	wuxu.wu@huawei.com, liusirui@huawei.com, liuzixian4@huawei.com
Subject: Re: [PATCH RESEND v2] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB
Date: Mon, 11 Oct 2021 10:28:22 +0200	[thread overview]
Message-ID: <YWP1pvwEmnUkxnVO@dhcp22.suse.cz> (raw)
In-Reply-To: <fa8937a5-08f1-d561-c047-f21abb817973@oracle.com>

On Fri 08-10-21 14:26:48, Mike Kravetz wrote:
> On 10/8/21 12:57 PM, 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.
> > 
> > Signed-off-by: zhangyiru <zhangyiru3@huawei.com>
> > ---
> > Changelog:
> >  v2: preserve warning message
> >  v1: remove mlock ulimit for SHM_HUGETLB
> > ---
> >  fs/hugetlbfs/inode.c | 5 ++---
> >  1 file changed, 2 insertions(+), 3 deletions(-)
> > 
> > diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> > index cdfb1ae78a3f..877d0ce9526c 100644
> > --- a/fs/hugetlbfs/inode.c
> > +++ b/fs/hugetlbfs/inode.c
> > @@ -1470,10 +1470,9 @@ struct file *hugetlb_file_setup(const char *name, size_t size,
> >  			pr_warn_once("%s (%d): Using mlock ulimits for SHM_HUGETLB is deprecated\n",
> >  				current->comm, current->pid);
> >  			task_unlock(current);
> > -		} else {
> > -			*ucounts = NULL;
> > -			return ERR_PTR(-EPERM);
> >  		}
> > +		*ucounts = NULL;
> > +		return ERR_PTR(-EPERM);
> 
> IIUC, deprecated means that use of the feature is discouraged but
> technically still available.  With this patch, we use the term
> deprecated and also remove the functionality.  Perhaps change the
> warning to be the following?
> 
> pr_warn_once("%s (%d): Using mlock ulimits for SHM_HUGETLB is now obsolete\n",

Agreed. I would even go with an addition "Please report if you have a
usecase for this functionality."

> Leaving the 'deprecated' message and removing the functionality may
> confuse people if their application breaks after this patch.
> -- 
> Mike Kravetz

-- 
Michal Hocko
SUSE Labs


      reply	other threads:[~2021-10-11  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 19:57 [PATCH RESEND v2] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB zhangyiru
2021-10-08 21:26 ` Mike Kravetz
2021-10-11  8:28   ` Michal Hocko [this message]

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=YWP1pvwEmnUkxnVO@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=liusirui@huawei.com \
    --cc=liuzixian4@huawei.com \
    --cc=mike.kravetz@oracle.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).