On Sun, Mar 27, 2016 at 1:57 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
