Re: nfs-utils - TCP ephemeral port exhaustion results in mount failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Do these patches require one another?
>
> What happens if I have a patched nfs-utils, but not a patched kernel or the other way around?

They don't require each other per se.

If you have a patched kernel without a patched nfs-utils, then
attempts to mount when all ephemeral ports are already a part of at
least 1 TCP connection will fail with an EADDRINUSE from mount.nfs(8)
attempting to call bind(2).  It will never get around to calling
mount(2) and never enter the kernel RPC code.

If you have a patched nfs-utils without a patched kernel, its a little
unfortunate in that mount.nfs(8) will call mount(2), but that will
give an EIO when `xs_bind' tries to call `kernel_bind' which returns
EADDRINUSE.

I say unfortunate because in this scenario you get the less helpful
EIO back from mount(2) rather than the EADDRINUSE from bind(2),
meaning the end user sees "input/output error" rather than "address
already in use," where the latter is the real issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux