From: Stephen Rothwell <sfr@canb.auug.org.au>
To: kernel test robot <lkp@intel.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Hillf Danton <hdanton@sina.com>, Ingo Molnar <mingo@elte.hu>,
Joel Fernandes <joelaf@google.com>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Roman Gushchin <guro@fb.com>,
Steven Rostedt <rostedt@goodmis.org>, Tejun Heo <tj@kernel.org>,
Thomas Garnier <thgarnie@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [mm/vmalloc.c] 728e0fbf26: kernel_BUG_at_mm/vmalloc.c
Date: Tue, 4 Jun 2019 13:09:02 +1000 [thread overview]
Message-ID: <20190604130902.67475ea1@canb.auug.org.au> (raw)
In-Reply-To: <20190604021356.oqipbgasyaanrt3k@inn2.lkp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
Hi all,
On Tue, 4 Jun 2019 10:13:56 +0800 kernel test robot <lkp@intel.com> wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 728e0fbf263e3ed359c10cb13623390564102881 ("mm/vmalloc.c: get rid of one single unlink_va() when merge")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
This has been widely reported and a fixed version of the patch is
included in today's linux-next.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-04 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 2:13 kernel test robot
2019-06-04 3:09 ` Stephen Rothwell [this message]
2019-06-04 19:32 kernel test robot
2019-06-04 22:52 kernel test robot
2019-06-04 23:54 kernel test robot
2019-06-05 11:18 kernel test robot
2019-06-05 13:50 kernel test robot
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=20190604130902.67475ea1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hdanton@sina.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=mingo@elte.hu \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=willy@infradead.org \
/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
all inboxes | Powered by JetHome®