From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+35a50f1f6dfd5a0d7378@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com,
dave.jiang@intel.com, hughd@google.com, jglisse@redhat.com,
jrdr.linux@gmail.com, kirill.shutemov@linux.intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mhocko@suse.com, rientjes@google.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: WARNING: locking bug in split_huge_page_to_list
Date: Tue, 23 Apr 2019 10:53:26 -0700 [thread overview]
Message-ID: <20190423175326.GC19031@bombadil.infradead.org> (raw)
In-Reply-To: <0000000000003c9bea058734dc28@google.com>
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.
prev parent reply other threads:[~2019-04-23 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 16:13 syzbot
2019-04-23 17:53 ` Matthew Wilcox [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=20190423175326.GC19031@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dave.jiang@intel.com \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=syzbot+35a50f1f6dfd5a0d7378@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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