I confirm the exact same behavior with a fresh install of wheezy
(stable) with nfs4+MIT kerberos5.
Clients can no longer mount nfs shares and "hangs" forever. By looking
at the network traffic with Wireshark, it appears that the server never
send response to the client query "NFS V4 COMPOUND
Hello everyone,
I've been affected by this bug as well. After some further
investigations I found the root cause of this bug.
This bug is triggered when the client's IP address can't be mapped to an
hostname. The evil part is inside rpc.mountd, which is also the only
binary affected by this bug.
On 26/07/2012 18:58, Luk Claes wrote:
> Even if that was not the case, NFS is not only about NFS4 or use with
> krb5, so anything above important is wrong as long as these other use
> cases still work.
Sorry, maybe I have a little bit overrated the severity.
> Btw, there are quite some NFS4+krb5
On 07/26/2012 05:18 PM, Nicolas Bourdaud wrote:
> Since the bug does not seem to be as systematic as I originally thought,
> I set the severity back to the one set by the bug reporter.
Even if that was not the case, NFS is not only about NFS4 or use with
krb5, so anything above important is wrong
severity 682709 important
thanks
For a reason I don't understand, after the last reboot of the server and
client, everything works again. I suspect the last configuration changes
(before my previous email) did not propagate correctly because of some
caching (or some other reason that would go beyo
severity 682709 grave
thanks
Hi,
I am affected by the same bug. I have raised the severity of the bug to
grave because it makes NFSv4 mount with kerberos unusable.
Cheers,
Nicolas
signature.asc
Description: OpenPGP digital signature
6 matches
Mail list logo
