From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Argangeli <andrea@kernel.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Oleg Nesterov <oleg@redhat.com>,
Wenwei Tao <wenwei.tww@alibaba-inc.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mm, oom: fix oom_reaper fallouts
Date: Tue, 15 Aug 2017 14:29:16 +0200 [thread overview]
Message-ID: <20170815122915.GF29067@dhcp22.suse.cz> (raw)
In-Reply-To: <20170807113839.16695-1-mhocko@kernel.org>
On Mon 07-08-17 13:38:37, Michal Hocko wrote:
> Hi,
> there are two issues this patch series attempts to fix. First one is
> something that has been broken since MMF_UNSTABLE flag introduction
> and I guess we should backport it stable trees (patch 1). The other
> issue has been brought up by Wenwei Tao and Tetsuo Handa has created
> a test case to trigger it very reliably. I am not yet sure this is a
> stable material because the test case is rather artificial. If there is
> a demand for the stable backport I will prepare it, of course, though.
>
> I hope I've done the second patch correctly but I would definitely
> appreciate some more eyes on it. Hence CCing Andrea and Kirill. My
> previous attempt with some more context was posted here
> http://lkml.kernel.org/r/20170803135902.31977-1-mhocko@kernel.org
>
> My testing didn't show anything unusual with these two applied on top of
> the mmotm tree.
unless anybody object can we have this merged? Whether to push this to
the stable tree is still questionable because it requires a rather
artificial workload to trigger the issue but if others think it would be
better to have it backported I will prepare backports for all relevant
stable trees.
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2017-08-15 12:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 11:38 Michal Hocko
2017-08-07 11:38 ` [PATCH 1/2] mm: fix double mmap_sem unlock on MMF_UNSTABLE enforced SIGBUS Michal Hocko
2017-08-15 0:49 ` David Rientjes
2017-08-07 11:38 ` [PATCH 2/2] mm, oom: fix potential data corruption when oom_reaper races with writer Michal Hocko
2017-08-08 17:48 ` Andrea Arcangeli
2017-08-08 23:35 ` Tetsuo Handa
2017-08-09 18:36 ` Andrea Arcangeli
2017-08-10 8:21 ` Michal Hocko
2017-08-10 13:33 ` Michal Hocko
2017-08-11 2:28 ` Tetsuo Handa
2017-08-11 7:09 ` Michal Hocko
2017-08-11 7:54 ` Tetsuo Handa
2017-08-11 10:22 ` Andrea Arcangeli
2017-08-11 10:42 ` Andrea Arcangeli
2017-08-11 11:53 ` Tetsuo Handa
2017-08-11 12:08 ` Michal Hocko
2017-08-11 15:46 ` Tetsuo Handa
2017-08-14 13:59 ` Michal Hocko
2017-08-14 22:51 ` Tetsuo Handa
2017-08-15 6:55 ` Michal Hocko
2017-08-15 8:41 ` Michal Hocko
2017-08-15 10:06 ` Tetsuo Handa
2017-08-15 12:26 ` Michal Hocko
2017-08-15 12:58 ` Tetsuo Handa
2017-08-17 13:58 ` Michal Hocko
2017-08-15 5:30 ` Tetsuo Handa
2017-08-07 13:28 ` [PATCH 0/2] mm, oom: fix oom_reaper fallouts Tetsuo Handa
2017-08-07 14:04 ` Michal Hocko
2017-08-07 15:23 ` Tetsuo Handa
2017-08-15 12:29 ` 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=20170815122915.GF29067@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrea@kernel.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=wenwei.tww@alibaba-inc.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