From: Valdis.Kletnieks@vt.edu
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
wfg@linux.intel.com, Christoph Lameter <cl@linux.com>,
Tejun Heo <tj@kernel.org>, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()
Date: Tue, 02 Feb 2016 14:12:43 -0500 [thread overview]
Message-ID: <21792.1454440363@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20160201073422.6dd72721@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Mon, 01 Feb 2016 07:34:22 +1100, Stephen Rothwell said:
> Hi Jesper,
> > [PATCH] mm: temporary fix for SLAB in linux-next
> >
> > From: Jesper Dangaard Brouer <brouer@redhat.com>
> >
> > This is only for linux-next, until AKPM pickup fixes two patches:
> > base url: http://ozlabs.org/~akpm/mmots/broken-out/
> > [1] mm-fault-inject-take-over-bootstrap-kmem_cache-check.patch
> > [2] slab-use-slab_pre_alloc_hook-in-slab-allocator-shared-with-slub.patch
> Applied to linux-next today.
Confirming that next-2016201 doesn't throw the warning on my laptop, thanks...
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2016-02-02 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 14:52 kernel test robot
2016-01-28 17:47 ` Jesper Dangaard Brouer
2016-01-30 7:09 ` Valdis.Kletnieks
2016-01-30 17:46 ` Jesper Dangaard Brouer
2016-01-31 2:15 ` Stephen Rothwell
2016-01-31 18:40 ` Jesper Dangaard Brouer
2016-01-31 20:34 ` Stephen Rothwell
2016-02-02 19:12 ` Valdis.Kletnieks [this message]
2016-03-01 18:33 ` Andrew Morton
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=21792.1454440363@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=fengguang.wu@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=wfg@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