linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Yisheng Xie <xieyisheng1@huawei.com>,
	akpm@linux-foundation.org, mhocko@suse.com, mingo@kernel.org,
	rientjes@google.com, n-horiguchi@ah.jp.nec.com,
	salls@cs.ucsb.edu
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	tanxiaojun@huawei.com, linux-api@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH RFC v2 1/4] mm/mempolicy: Fix get_nodes() mask miscalculation
Date: Tue, 31 Oct 2017 09:34:54 +0100	[thread overview]
Message-ID: <922a4767-9eed-40aa-c437-6f6fcdcab150@suse.cz> (raw)
In-Reply-To: <1509099265-30868-2-git-send-email-xieyisheng1@huawei.com>

On 10/27/2017 12:14 PM, Yisheng Xie wrote:
> It appears there is a nodemask miscalculation in the get_nodes()
> function in mm/mempolicy.c.  This bug has two effects:
> 
> 1. It is impossible to specify a length 1 nodemask.
> 2. It is impossible to specify a nodemask containing the last node.

This should be more specific, which syscalls are you talking about?
I assume it's set_mempolicy() and mbind() and it's the same issue that
was discussed at https://marc.info/?l=linux-mm&m=150732591909576&w=2 ?

> Brent have submmit a patch before v2.6.12, however, Andi revert his
> changed for ABI problem. I just resent this patch as RFC, for do not
> clear about what's the problem Andi have met.

You should have CC'd Andi. As was discussed in the other thread, this
would make existing programs potentially unsafe, so we can't change it.
Instead it should be documented.

> As manpage of set_mempolicy, If the value of maxnode is zero, the
> nodemask argument is ignored. but we should not ignore the nodemask
> when maxnode is 1.
> 
> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
> ---
>  mm/mempolicy.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index a2af6d5..613e9d0 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -1265,7 +1265,6 @@ static int get_nodes(nodemask_t *nodes, const unsigned long __user *nmask,
>  	unsigned long nlongs;
>  	unsigned long endmask;
>  
> -	--maxnode;
>  	nodes_clear(*nodes);
>  	if (maxnode == 0 || !nmask)
>  		return 0;
> 

--
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:[~2017-10-31  8:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 10:14 [PATCH RFC v2 0/4] some fixes and clean up for mempolicy Yisheng Xie
2017-10-27 10:14 ` [PATCH RFC v2 1/4] mm/mempolicy: Fix get_nodes() mask miscalculation Yisheng Xie
2017-10-31  8:34   ` Vlastimil Babka [this message]
2017-11-01  9:37     ` Yisheng Xie
2017-10-27 10:14 ` [PATCH RFC v2 2/4] mm/mempolicy: remove redundant check in get_nodes Yisheng Xie
2017-10-31  8:55   ` Vlastimil Babka
2017-10-27 10:14 ` [PATCH RFC v2 3/4] mm/mempolicy: fix the check of nodemask from user Yisheng Xie
2017-10-31  9:30   ` Vlastimil Babka
2017-10-31 11:01     ` Yisheng Xie
2017-10-31 11:28       ` Vlastimil Babka
2017-10-27 10:14 ` [PATCH RFC v2 4/4] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages Yisheng Xie
2017-10-31  9:46   ` Vlastimil Babka
2017-11-06  1:31     ` Yisheng Xie
2017-11-06  7:39       ` Vlastimil Babka
2017-11-06 15:29         ` Christopher Lameter
2017-11-07 11:23           ` Yisheng Xie
2017-11-07 14:54             ` Christopher Lameter
2017-11-07 15:05               ` Vlastimil Babka
2017-11-07 15:55                 ` Christopher Lameter
2017-11-08  1:38                   ` Yisheng Xie
2017-11-08 15:02                     ` Christopher Lameter
2017-11-09 10:54                       ` Yisheng Xie
2017-11-09 15:46                         ` Christopher Lameter

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=922a4767-9eed-40aa-c437-6f6fcdcab150@suse.cz \
    --to=vbabka@suse.cz \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rientjes@google.com \
    --cc=salls@cs.ucsb.edu \
    --cc=tanxiaojun@huawei.com \
    --cc=xieyisheng1@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).