linux-kernel - git <8f6576a> Causes non-interruptible stalls in NFS clients

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>] [day] [month] [year] [list]

Date:	Thu, 31 May 2012 05:01:01 -0700
From:	walt <w41ter@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: git <8f6576a> Causes non-interruptible stalls in NFS clients

Merge: 8f6576a cc0a984
Author: Linus Torvalds 
Date:   Tue May 29 10:43:51 2012 -0700

    Merge tag 'nfs-for-3.5-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs

    Pull NFS client updates from Trond Myklebust:

- Improve the code sharing between NFSv2/v3 and v4 mounts

That last comment gave me the idea to enable NFSv4 client support in my kernel
(which I had disabled many months ago because of NFSv4 weirdness).

Enabling NFSv4 client support completely fixed the non-interruptible NFS stalls
and, strangely, also fixed the very similar stalls in my scp/sftp clients when
pushing files > 800KB or so.

Enabling the NFSv4 client support fixes everything even though I'm still using
NFSv3 mounts explicitly/exclusively.

--
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/