From: Sasha Levin <levinsasha928@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: guro@fb.com, Sasha Levin <alexander.levin@microsoft.com>,
dairinin@gmail.com,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
riel@surriel.com, hannes <hannes@cmpxchg.org>,
vdavydov.dev@gmail.com, shakeelb@google.com,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-mm <linux-mm@kvack.org>,
sashal@kernel.org
Subject: Re: Memory management issue in 4.18.15
Date: Thu, 25 Oct 2018 07:26:02 -0400 [thread overview]
Message-ID: <CA+1xoqe-Q-vZ1TjyvRNfycnzr-Q3OWQa3WnWOgOvskWi9CC7cw@mail.gmail.com> (raw)
In-Reply-To: <20181022170146.GI18839@dhcp22.suse.cz>
On Mon, Oct 22, 2018 at 1:01 PM Michal Hocko <mhocko@kernel.org> wrote:
>
> On Mon 22-10-18 15:08:22, Roman Gushchin wrote:
> [...]
> > RE backporting: I'm slightly surprised that only one patch of the memcg
> > reclaim fix series has been backported. Either all or none makes much more
> > sense to me.
>
> Yeah, I think this is AUTOSEL trying to be clever again. I though it has
> been agreed that MM is quite good at marking patches for stable and so
> it was not considered by the machinery. Sasha?
I've talked about it briefly with Andrew, and he suggested that I'll
send him the list of AUTOSEL commits separately to avoid the noise, so
we'll try that and see what happens.
--
Thanks.
Sasha
next prev parent reply other threads:[~2018-10-25 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADa=ObrwYaoNFn0x06mvv5W1F9oVccT5qjGM8qFBGNPoNuMUNw@mail.gmail.com>
2018-10-20 15:37 ` Randy Dunlap
2018-10-20 17:41 ` Roman Gushchin
2018-10-22 8:33 ` Michal Hocko
2018-10-22 15:08 ` Roman Gushchin
2018-10-22 17:01 ` Michal Hocko
2018-10-25 11:26 ` Sasha Levin [this message]
2018-10-22 17:35 ` Roman Gushchin
2018-10-22 23:44 ` Roman Gushchin
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=CA+1xoqe-Q-vZ1TjyvRNfycnzr-Q3OWQa3WnWOgOvskWi9CC7cw@mail.gmail.com \
--to=levinsasha928@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@microsoft.com \
--cc=dairinin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=riel@surriel.com \
--cc=sashal@kernel.org \
--cc=shakeelb@google.com \
--cc=vdavydov.dev@gmail.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