Messages in this thread | | | Date | Sun, 27 Mar 2016 05:03:44 -0700 | Subject | Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 | From | Linus Torvalds <> |
| |
On Sun, Mar 27, 2016 at 1:57 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote: > > I pulled ext4.git#dev on top of Linux v4.6-rc1... > > ... and did not see the call-trace.
Unless you're using overlayfs or per-file encryption, I'm not seeing that any of that should make any difference (but it's entirely possible I'm missing something).
Was it entirely repeatable before? Maybe it just happened to happen without that update, and then happened to _not_ happen after you rebooted with that 'dev' branch pulled in?
Anyway, I don't think that DEBUG_LOCKS_WARN_ON() in
kernel/locking/lockdep.c:2017 __lock_acquire
would be an ext4 issue, it looks more like an internal lockdep issue.
Adding in the lockdep people, who will set me right.
Linus
| |