linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: akpm@linux-foundation.org, wli@movementarian.org,
	linux-mm@kvack.org, shai@scalex86.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] mm: Reintroduce and deprecate rlimit based access for SHM_HUGETLB
Date: Mon, 23 Feb 2009 11:21:56 +0000	[thread overview]
Message-ID: <20090223112156.GB6740@csn.ul.ie> (raw)
In-Reply-To: <20090221015748.GB32674@localdomain>

On Fri, Feb 20, 2009 at 05:57:48PM -0800, Ravikiran G Thirumalai wrote:
> Allow non root users with sufficient mlock rlimits to be able to allocate
> hugetlb backed shm for now.  Deprecate this though.  This is being
> deprecated because the mlock based rlimit checks for SHM_HUGETLB
> is not consistent with mmap based huge page allocations.
> 
> Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>
> Cc: Mel Gorman <mel@csn.ul.ie>
> Cc: Wli <wli@movementarian.org>
> 
> Index: linux-2.6-tip/fs/hugetlbfs/inode.c
> ===================================================================
> --- linux-2.6-tip.orig/fs/hugetlbfs/inode.c	2009-02-10 13:30:05.000000000 -0800
> +++ linux-2.6-tip/fs/hugetlbfs/inode.c	2009-02-11 21:58:23.000000000 -0800
> @@ -948,6 +948,7 @@ static int can_do_hugetlb_shm(void)
>  struct file *hugetlb_file_setup(const char *name, size_t size)
>  {
>  	int error = -ENOMEM;
> +	int unlock_shm = 0;
>  	struct file *file;
>  	struct inode *inode;
>  	struct dentry *dentry, *root;
> @@ -957,8 +958,14 @@ struct file *hugetlb_file_setup(const ch
>  	if (!hugetlbfs_vfsmount)
>  		return ERR_PTR(-ENOENT);
>  
> -	if (!can_do_hugetlb_shm())
> -		return ERR_PTR(-EPERM);
> +	if (!can_do_hugetlb_shm()) {
> +		if (user_shm_lock(size, user)) {
> +			unlock_shm = 1;
> +			WARN_ONCE(1,
> +			  "Using mlock ulimits for SHM_HUGETLB deprecated\n");
> +		} else
> +			return ERR_PTR(-EPERM);
> +	}
>  

Seems to do what is promised by the patch and basic tests worked out for
me. I think the behaviour has changed slightly in that we are getting EPERM
now where we might have seen ENOMEM before but that should be ok.

>  	root = hugetlbfs_vfsmount->mnt_root;
>  	quick_string.name = name;
> @@ -997,6 +1004,8 @@ out_inode:
>  out_dentry:
>  	dput(dentry);
>  out_shm_unlock:
> +	if (unlock_shm)
> +		user_shm_unlock(size, user);
>  	return ERR_PTR(error);
>  }
>  
> Index: linux-2.6-tip/Documentation/feature-removal-schedule.txt
> ===================================================================
> --- linux-2.6-tip.orig/Documentation/feature-removal-schedule.txt	2009-02-09 16:45:47.000000000 -0800
> +++ linux-2.6-tip/Documentation/feature-removal-schedule.txt	2009-02-11 21:35:28.000000000 -0800
> @@ -335,3 +335,14 @@ Why:	In 2.6.18 the Secmark concept was i
>  	Secmark, it is time to deprecate the older mechanism and start the
>  	process of removing the old code.
>  Who:	Paul Moore <paul.moore@hp.com>
> +---------------------------
> +
> +What:	Ability for non root users to shm_get hugetlb pages based on mlock
> +	resource limits
> +When:	2.6.31
> +Why:	Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or
> +	have CAP_IPC_LOCK to be able to allocate shm segments backed by
> +	huge pages.  The mlock based rlimit check to allow shm hugetlb is
> +	inconsistent with mmap based allocations.  Hence it is being
> +	deprecated.
> +Who:	Ravikiran Thirumalai <kiran@scalex86.org>
> 

Reviewed-by: Mel Gorman <mel@csn.ul.ie>

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-02-23 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21  1:54 [patch 1/2] mm: Fix SHM_HUGETLB to work with users in hugetlb_shm_group Ravikiran G Thirumalai
2009-02-21  1:57 ` [patch 2/2] mm: Reintroduce and deprecate rlimit based access for SHM_HUGETLB Ravikiran G Thirumalai
2009-02-23 11:21   ` Mel Gorman [this message]
2009-02-23 11:04 ` [patch 1/2] mm: Fix SHM_HUGETLB to work with users in hugetlb_shm_group Mel Gorman
2009-02-23 19:21   ` Ravikiran G Thirumalai

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=20090223112156.GB6740@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shai@scalex86.org \
    --cc=wli@movementarian.org \
    /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