From: Steven Rostedt <rostedt@goodmis.org>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: avagin@virtuozzo.com, Steven Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, Michal Hocko <mhocko@suse.com>,
Linux Memory Management List <linux-mm@kvack.org>,
mgorman@techsingularity.net, mingo@kernel.org,
peterz@infradead.org, Fengguang Wu <fengguang.wu@intel.com>,
Dennis Zhou <dennisszhou@gmail.com>
Subject: Re: [v2] mm: access to uninitialized struct page
Date: Fri, 4 May 2018 10:50:52 -0400 [thread overview]
Message-ID: <20180504105052.429106ca@gandalf.local.home> (raw)
In-Reply-To: <CAGM2rebLfmWLybzNDPt-HTjZY2brkJ_8Bq37xVG_QDs=G+VuxQ@mail.gmail.com>
On Fri, 04 May 2018 12:47:53 +0000
Pavel Tatashin <pasha.tatashin@oracle.com> wrote:
> Hi Andrei,
>
> Could you please provide me with scripts to reproduce this issue?
>
>
And the config that was used. Just saying that the commit doesn't boot
isn't very useful.
-- Steve
next prev parent reply other threads:[~2018-05-04 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 20:26 [PATCH v2] mm: access to uninitialized struct page Pavel Tatashin
2018-04-30 23:26 ` Andrew Morton
2018-04-30 23:58 ` Steven Rostedt
2018-05-01 0:01 ` Andrew Morton
2018-05-08 14:44 ` Pavel Tatashin
2018-05-04 8:27 ` [v2] " Andrei Vagin
2018-05-04 12:47 ` Pavel Tatashin
2018-05-04 14:50 ` Steven Rostedt [this message]
2018-05-04 16:01 ` Andrei Vagin
2018-05-04 16:03 ` Pavel Tatashin
2018-05-04 17:49 ` Andy Shevchenko
2018-05-05 1:04 ` Fengguang Wu
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=20180504105052.429106ca@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=avagin@virtuozzo.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dennisszhou@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=peterz@infradead.org \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).