From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Shakeel Butt <shakeelb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
stable@kernel.orglinux-mm@kvack.orglinux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mm, oom: fix use-after-free in oom_kill_process
Date: Wed, 23 Jan 2019 22:57:46 +0000 [thread overview]
Message-ID: <20190123225747.8715120856@mail.kernel.org> (raw)
In-Reply-To: <20190121215850.221745-1-shakeelb@google.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 6b0c81b3be11 mm, oom: reduce dependency on tasklist_lock.
The bot has tested the following trees: v4.20.3, v4.19.16, v4.14.94, v4.9.151, v4.4.171, v3.18.132.
v4.20.3: Build OK!
v4.19.16: Build OK!
v4.14.94: Failed to apply! Possible dependencies:
5989ad7b5ede ("mm, oom: refactor oom_kill_process()")
v4.9.151: Build OK!
v4.4.171: Build OK!
v3.18.132: Build OK!
How should we proceed with this patch?
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Shakeel Butt <shakeelb@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>,
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: stable@kernel.org
Cc: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mm, oom: fix use-after-free in oom_kill_process
Date: Wed, 23 Jan 2019 22:57:46 +0000 [thread overview]
Message-ID: <20190123225747.8715120856@mail.kernel.org> (raw)
Message-ID: <20190123225746.DWVZuAQLmJ4oJWIT4RgybPOEd0E2UBXwSZop9Q5kg6E@z> (raw)
In-Reply-To: <20190121215850.221745-1-shakeelb@google.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 6b0c81b3be11 mm, oom: reduce dependency on tasklist_lock.
The bot has tested the following trees: v4.20.3, v4.19.16, v4.14.94, v4.9.151, v4.4.171, v3.18.132.
v4.20.3: Build OK!
v4.19.16: Build OK!
v4.14.94: Failed to apply! Possible dependencies:
5989ad7b5ede ("mm, oom: refactor oom_kill_process()")
v4.9.151: Build OK!
v4.4.171: Build OK!
v3.18.132: Build OK!
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-23 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 21:58 [PATCH v3 1/2] mm, oom: fix use-after-free in oom_kill_process Shakeel Butt
2019-01-21 21:58 ` [PATCH v3 2/2] mm, oom: remove 'prefer children over parent' heuristic Shakeel Butt
2019-01-21 21:58 ` Shakeel Butt
2019-01-22 2:41 ` Shakeel Butt
2019-01-22 8:52 ` Michal Hocko
2019-01-23 22:57 ` Sasha Levin [this message]
2019-01-23 22:57 ` [PATCH v3 1/2] mm, oom: fix use-after-free in oom_kill_process Sasha Levin
2019-01-23 23:14 ` Shakeel Butt
2019-01-23 23:35 ` Tetsuo Handa
2019-01-24 8:13 ` Greg KH
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=20190123225747.8715120856@mail.kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=stable@kernel.orglinux-mm \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.