linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Ganapatrao Kulkarni <gpkulkarni@gmail.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	linux-mm@kvack.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>
Subject: Re: getting oom/stalls for ltp test cpuset01 with latest/4.9 kernel
Date: Tue, 17 Jan 2017 09:13:09 +0100	[thread overview]
Message-ID: <7c8ed170-ced9-aa6a-25e0-47cdc6d66eb2@suse.cz> (raw)
In-Reply-To: <a374d6b6-c299-b50d-d7e0-f85ac78525aa@suse.cz>

On 01/16/2017 02:22 PM, Vlastimil Babka wrote:
>>>
>>>  no_zone:
>>> --
>>> 2.11.0
>>>
>>
>> this patch did not fix the issue.
>> issue still exists!
> 
> Hmm, that's unfortunate.
> 
>> i did bisect and this test passes in 4.4,4.5 and 4.6
>> test failing since 4.7-rc1
> 
> 4.7 would match the commit I was trying to fix. But I don't see other
> problems now. Could you bisect to a single commit then, to be sure? Thanks.

Ah, nevermind, I can reproduce the issue easily. After some more poking
I now think the bisect would lead to the OOM rework, but it would be a
red herring. Seems like this is an interaction between bind mempolicy
and cpuset and I see several potential bugs in that area. Which also
means there's a non-null nodemask and thus the code in the commit I
originally suspected (replacing NULL nodemask with cpuset's
mems_allowed) doesn't trigger at all here.

Thanks,
Vlastimil

>> thanks
>> Ganapat
>>>
>>>
>>>
> 
> --
> 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>
> 

--
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-01-17  8:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 10:50 Ganapatrao Kulkarni
2017-01-11 11:05 ` Vlastimil Babka
2017-01-11 12:38   ` Vlastimil Babka
2017-01-11 16:22     ` Ganapatrao Kulkarni
2017-01-11 16:46       ` Michal Hocko
2017-01-12 11:10         ` Vlastimil Babka
2017-01-13  4:35           ` Ganapatrao Kulkarni
2017-01-13  9:06             ` Vlastimil Babka
2017-01-13 15:51               ` Michal Hocko
2017-01-16 10:41               ` Ganapatrao Kulkarni
2017-01-16 13:22                 ` Vlastimil Babka
2017-01-17  8:13                   ` Vlastimil Babka [this message]
2017-01-11 16:33   ` Michal Hocko
2017-01-11 16:32 ` Michal Hocko

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=7c8ed170-ced9-aa6a-25e0-47cdc6d66eb2@suse.cz \
    --to=vbabka@suse.cz \
    --cc=gpkulkarni@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.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