From: Michal Hocko <mhocko@kernel.org>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Shaohua Li <shli@kernel.org>, 0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [md] 8caa6068fa: kernel BUG at mm/slub.c:3656!
Date: Tue, 3 May 2016 09:29:10 +0200 [thread overview]
Message-ID: <20160503072910.GC28039@dhcp22.suse.cz> (raw)
In-Reply-To: <87pot4gd5s.fsf@yhuang-dev.intel.com>
On Tue 03-05-16 09:09:51, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> https://github.com/0day-ci/linux Michal-Hocko/tree-wide-get-rid-of-__GFP_REPEAT-for-order-0-allocations-part-I/20160428-212857
> commit 8caa6068fa57b7187daedbfa9507d5ba4f962a41 ("md: simplify free_params for kmalloc vs vmalloc fallback")
This patch has been dropped from my series. Thanks for the test, anyway!
Mike has pointed out exactly this kind of crash [1]
[1] http://lkml.kernel.org/r/20160428153730.GA14570@redhat.com
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2016-05-03 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 1:09 kernel test robot
2016-05-03 7:29 ` Michal Hocko [this message]
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=20160503072910.GC28039@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mpatocka@redhat.com \
--cc=shli@kernel.org \
--cc=ying.huang@linux.intel.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
Powered by JetHome