On Sat, Apr 30, 2016 at 10:43:34AM -0400, Jeff Layton wrote: > Not exactly, but the test seems to have deadlocked without the last > patch in play. Here's the ls command: > > [jlayton@rawhide ~]$ cat /proc/1425/stack > [<ffffffffa03d6eec>] nfs_block_sillyrename+0x5c/0xa0 [nfs] > [<ffffffffa03c8ef8>] nfs_readdir+0xf8/0x620 [nfs] > [<ffffffff812232bb>] iterate_dir+0x16b/0x1a0 > [<ffffffff812236e8>] SyS_getdents+0x88/0x100 > [<ffffffff81003cb2>] do_syscall_64+0x62/0x110 > [<ffffffff8174ae21>] return_from_SYSCALL_64+0x0/0x6a > [<ffffffffffffffff>] 0xffffffffffffffff > > ...and here is the nfsidem command: > > [jlayton@rawhide ~]$ cat /proc/1295/stack > [<ffffffff813953b7>] call_rwsem_down_write_failed+0x17/0x30 > [<ffffffff8121f65b>] filename_create+0x6b/0x150 > [<ffffffff812204e4>] SyS_mkdir+0x44/0xe0 > [<ffffffff81003cb2>] do_syscall_64+0x62/0x110 > [<ffffffff8174ae21>] return_from_SYSCALL_64+0x0/0x6a > [<ffffffffffffffff>] 0xffffffffffffffff > > > I'll have to take off here in a bit so I won't be able to help much > until later, but all I was doing was running the cthon special tests > like so: > > $ ./server -p /export -s -N 100 tlielax > > That makes a directory called "rawhide.test" (since the client's > hostname is "rawhide") and runs its tests in there. Then I ran this in > a different shell: > > $ while true; do ls -l /mnt/tlielax/rawhide.test ; done > > Probably I should run this on a stock kernel just to see if there are > preexisting problems... FWIW, I could reproduce that (and I really wonder WTF is going on - looks like nfs_async_unlink_release() getting lost somehow), but not the memory corruption with the last commit... What .config are you using? -- 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
