Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1324543
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() |
| Date | 2016-02-02 20:20 +0100 |
| Message-ID | <qXOEy-7FS-3@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <qWxZ8-7Fv-5@gated-at.bofh.it> <qWHOP-7mY-21@gated-at.bofh.it> <qWPMm-4Ky-3@gated-at.bofh.it> <qX5eq-7ou-17@gated-at.bofh.it> <qX6WS-fk-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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...
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Jesper Dangaard Brouer <brouer@redhat.com> - 2016-01-28 18:50 +0100
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Jesper Dangaard Brouer <brouer@redhat.com> - 2016-01-30 18:50 +0100
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-31 03:20 +0100
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Jesper Dangaard Brouer <brouer@redhat.com> - 2016-01-31 19:50 +0100
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-31 21:40 +0100
Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller() Valdis.Kletnieks@vt.edu - 2016-02-02 20:20 +0100
csiph-web