[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190423175326.GC19031@bombadil.infradead.org>
Date: Tue, 23 Apr 2019 10:53:26 -0700
From: Matthew Wilcox <willy@...radead.org>
To: syzbot <syzbot+35a50f1f6dfd5a0d7378@...kaller.appspotmail.com>
Cc: akpm@...ux-foundation.org, aneesh.kumar@...ux.ibm.com,
dave.jiang@...el.com, hughd@...gle.com, jglisse@...hat.com,
jrdr.linux@...il.com, kirill.shutemov@...ux.intel.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, mhocko@...e.com,
rientjes@...gle.com, syzkaller-bugs@...glegroups.com,
vbabka@...e.cz
Subject: Re: WARNING: locking bug in split_huge_page_to_list
On Tue, Apr 23, 2019 at 09:13:06AM -0700, syzbot wrote:
> DEBUG_LOCKS_WARN_ON(class_idx > MAX_LOCKDEP_KEYS)
> WARNING: CPU: 0 PID: 1553 at kernel/locking/lockdep.c:3673
> __lock_acquire+0x1887/0x3fb0 kernel/locking/lockdep.c:3673
> down_write+0x38/0x90 kernel/locking/rwsem.c:70
> anon_vma_lock_write include/linux/rmap.h:120 [inline]
All anon_vmas share the same lockdep map, so I think this is just a
victim of someone else who's taken all the lockdep classes.
Powered by blists - more mailing lists