How we spent two weeks hunting an NFS bug in the Linux kernel

Re:How we spent two weeks hunting an NFS bug in the Linux ke... by saketuec on Wednesday November 28, 2018 @09:31PM (#18557579)

Great post! In my own experience of working with NFS version 4 servers, we discovered several bugs that have been actually fixed in latest version of kernels. The unfortunate thing is that most enterprises still run old CentOS / Redhat release kernels that although are stable, but yet lack several of these fixes.

[ Parent | on HN ]

Re:How we spent two weeks hunting an NFS bug in the Linux ke... by asveikau on Wednesday November 28, 2018 @10:50PM (#18557918)

I don't have a lot of experience with NFS aside from a few machines that don't see insane use, but it's surprising to me how v4 implementations seem to introduce such instability. I had an experience a few years ago with a Mac client, quitting vim would cause a kernel panic. NFS v3 did fine.

[ Parent | on HN ]

Re:How we spent two weeks hunting an NFS bug in the Linux ke... by greglindahl on Wednesday November 28, 2018 @10:29PM (#18557824)

Red Hat usually backports those sorts of fixes to their old-looking kernel versions.

[ Parent | on HN ]

Re:How we spent two weeks hunting an NFS bug in the Linux ke... by KaiserPro on Thursday November 29, 2018 @04:58AM (#18559145)

NFS is normally fairly modern, as thats the reason that you pay for a RHEL licences, its the host fix should you run into a bug like this.

[ Parent | on HN ]