linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m2id4f60c3c1005040705v2e46547axad496769d4d4dbe8@mail.gmail.com>
Date:	Tue, 4 May 2010 07:05:34 -0700
From:	Fredrick Prashanth John Berchmans <fredrickprashanth@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: nfs accesses of FAT fs folders causes deadlock on lock_super

On Tue, May 4, 2010 at 3:32 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, May 03, 2010 at 10:59:42PM -0700, Fredrick Prashanth John Berchmans wrote:
>> The box was running kernel version 2.6.27.10.
>> But I think the FAT code has not changed much.
>
> But the nfsd code has and now doesn't call lookup from the filldir
> callback anymore.
>
>

Ah..I just noticed the changes in the nfsd code.

But in 2.6.27.10, can it be fixed by removing the lock_super in the
vfat_lookup.?
Because I saw some discussions long back of regressions due to
replacing lock_kernel by lock_super in FAT code.
Or should the sb mutex be unlocked before calling the callback filldir
in the __fat_readdir?

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/