[...]
> The lockdep appears one time in the logs... I tried several...
>
>      # LC_ALL=C TEST_OVERLAYFS=1 ./run.sh truncate.test
>
> ...and see the only lockdep.
>
> Sorry, I cannot say which of the test-no (is that what you mean by
> operation?) is causing the lockdep.
>
> Truncate-test results attached.
>

I have rebooted my machine and re-run truncate.test again.

     # LC_ALL=C TEST_OVERLAYFS=1 ./run.sh truncate.test

So, the lockdep appears with the first operation...

***
*** TEST_OVERLAYFS=1 TERMSLASH=0 ./run.sh truncate.test
***
TEST129: Prepare comparison
16+0 records in
16+0 records out
TEST100: Truncate to 0
 - fs_op truncate /mnt/a/foo100 0
1st FS-OP: XXX
[   91.551101]  [<ffffffff811dbeb5>] ? path_init+0x545/0x6a0
[   91.551104]  [<ffffffff810bc700>] ? mark_held_locks+0x90/0x90
[   91.551107]  [<ffffffff811dd0ab>] path_openat+0xbb/0x680
[   91.551111]  [<ffffffff811de6fa>] do_filp_open+0x3a/0x90
[   91.551115]  [<ffffffff8173a287>] ? _raw_spin_unlock+0x27/0x40
[   91.551118]  [<ffffffff811ec5b7>] ? __alloc_fd+0xa7/0x130
[   91.551121]  [<ffffffff811cc288>] do_sys_open+0x128/0x220
[   91.551125]  [<ffffffff81022805>] ? syscall_trace_enter+0x145/0x260
[   91.551128]  [<ffffffff811cc39e>] SyS_open+0x1e/0x20
[   91.551132]  [<ffffffff81744258>] tracesys+0xe1/0xe6
TEST101: Truncate to 1
...

The full log is attached.

- Sedat -