From: Cong Wang <xiyou.wangcong@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, dave.hansen@intel.com,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>,
vbabka@suse.cz
Subject: Re: [PATCH] mm,page_alloc: Serialize warn_alloc() if schedulable.
Date: Mon, 5 Jun 2017 11:15:19 -0700 [thread overview]
Message-ID: <CAM_iQpWV_bir4=66o-rpDrEYVt1Ufq3-zi+bG0QQGjTc1V8B=A@mail.gmail.com> (raw)
In-Reply-To: <20170605053701.GA9773@dhcp22.suse.cz>
On Sun, Jun 4, 2017 at 10:37 PM, Michal Hocko <mhocko@suse.com> wrote:
> Running a distribution kernel is at risk that obscure bugs (like this
> one) will be asked to be reproduced on the vanilla kernel. I work to
> support a distribution kernel as well and I can tell you that I always
> do my best reproducing or at least pinpointing the issue before
> reporting it upstream. People working on the upstream kernel are quite
> busy and _demanding_ a support for something that should come from their
> vendor is a bit to much.
I understand that. As I already explained, our kernel has _zero_ code that
is not in upstream, it is just 4.9.23 plus some non-mm backports from latest.
So my question is, is there any fix you believe that is relevant in linux-next
but not in 4.9.23? We definitely can try to backport it too. I have checked
the changelog since 4.9 and don't find anything obviously relevant.
Meanwhile, I will try to run this LTP test repeatly to see if there is any luck.
Thanks.
--
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>
next prev parent reply other threads:[~2017-06-05 18:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 11:43 Tetsuo Handa
2017-06-01 11:59 ` Michal Hocko
2017-06-01 13:11 ` Tetsuo Handa
2017-06-01 13:28 ` Michal Hocko
2017-06-01 22:10 ` Andrew Morton
2017-06-02 7:18 ` Michal Hocko
2017-06-02 11:13 ` Tetsuo Handa
2017-06-02 12:15 ` Michal Hocko
2017-06-02 17:13 ` Tetsuo Handa
2017-06-02 21:57 ` Cong Wang
2017-06-04 8:58 ` Tetsuo Handa
2017-06-04 15:05 ` Michal Hocko
2017-06-04 21:43 ` Tetsuo Handa
2017-06-05 5:37 ` Michal Hocko
2017-06-05 18:15 ` Cong Wang [this message]
2017-06-06 9:17 ` Michal Hocko
2017-06-05 18:25 ` Cong Wang
2017-06-22 10:35 ` Tetsuo Handa
2017-06-22 22:53 ` Cong Wang
2017-06-02 16:59 ` Cong Wang
2017-06-02 19:59 ` Andrew Morton
2017-06-03 2:57 ` Tetsuo Handa
2017-06-03 7:32 ` Michal Hocko
2017-06-03 8:36 ` Tetsuo Handa
2017-06-05 7:10 ` Sergey Senozhatsky
2017-06-05 9:36 ` Sergey Senozhatsky
2017-06-05 15:02 ` Tetsuo Handa
2017-06-03 13:21 ` Tetsuo Handa
2017-07-08 4:59 ` Tetsuo Handa
2017-07-10 13:21 ` Michal Hocko
2017-07-10 13:54 ` Tetsuo Handa
2017-07-10 14:14 ` Michal Hocko
2017-07-11 13:10 ` Tetsuo Handa
2017-07-11 13:49 ` Michal Hocko
2017-07-11 14:58 ` Petr Mladek
2017-07-11 22:06 ` Tetsuo Handa
2017-07-12 8:54 ` Michal Hocko
2017-07-12 12:23 ` Tetsuo Handa
2017-07-12 12:41 ` Michal Hocko
2017-07-14 12:30 ` Tetsuo Handa
2017-07-14 12:48 ` Michal Hocko
2017-08-09 6:14 ` Tetsuo Handa
2017-08-09 13:01 ` Tetsuo Handa
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='CAM_iQpWV_bir4=66o-rpDrEYVt1Ufq3-zi+bG0QQGjTc1V8B=A@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=vbabka@suse.cz \
/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