linux-kernel - nfs accesses of FAT fs folders causes deadlock on lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <x2gd4f60c3c1005032259p8be864bcucff91618016a0eb@mail.gmail.com>
Date:	Mon, 3 May 2010 22:59:42 -0700
From:	Fredrick Prashanth John Berchmans <fredrickprashanth@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	fredrickprashanth@...il.com
Subject: nfs accesses of FAT fs folders causes deadlock on lock_super

Hi,

A FAT fs folder was shared using nfs. Accessing it over nfs causes
deadlock on lock_super since
it is acquired by both __fat_readdir and vfat_lookup in the following
call chain.

Call chain
#lock_super <----causes deadlock
#vfat_lookup
#__lookup_hash
#lookup_one_len
#compose_entry_fh
#encode_entry
#nfs3svc_encode_entry_plus
#__fat_readdir <---does lock_super
#fat_readdir
#vfs_readdir
#nfsd_readdir
#nfsd3_proc_readdirplus
#nfsd_dispatch
#svc_process
#nfsd


Is lock_super needed in the vfat_lookup?
Can it be removed?

The box was running kernel version 2.6.27.10.
But I think the FAT code has not changed much.

Thanks,
Fredrick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/