LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Andrei Vagin <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>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Linux Memory Management List <linux-mm@kvack.org>,
mgorman@techsingularity.net, Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.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 20:49:54 +0300 [thread overview]
Message-ID: <CAHp75Vf868eQuZUsmx=D62chUzBeYqdL0BxuOJ1qS17QdT-obw@mail.gmail.com> (raw)
In-Reply-To: <22c34b1b-15d9-6a28-d7f2-697bac42bde2@oracle.com>
On Fri, May 4, 2018 at 7:03 PM, Pavel Tatashin
<pasha.tatashin@oracle.com> wrote:
> Thank you, I will try to figure out what is happening.
+1 is here.
The last message I have seen on the console are:
[ 4.690972] Non-volatile memory driver v1.3
[ 4.703360] Linux agpgart interface v0.103
[ 4.710282] loop: module loaded
Bisection points to this very patch.
I would suggest to revert ASAP and you may still continue
investigating on your side.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-05-04 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 20:26 [PATCH v2] " 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
2018-05-04 16:01 ` Andrei Vagin
2018-05-04 16:03 ` Pavel Tatashin
2018-05-04 17:49 ` Andy Shevchenko [this message]
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='CAHp75Vf868eQuZUsmx=D62chUzBeYqdL0BxuOJ1qS17QdT-obw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--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=rostedt@goodmis.org \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--subject='Re: [v2] mm: access to uninitialized struct page' \
/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
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).