How we spent two weeks hunting an NFS bug in the Linux kernel
about.gitlab.com
How we spent two weeks hunting an NFS bug in the Linux kernel
1–10 of 69 posts
Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#2(1): http://www.brendangregg.com/blog/2018-10-08/dtrace-for-linux...
Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#3Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#4I spend my days chasing bugs like this in the FreeBSD kernel, and make heavy use of dtrace. I expect that using something like bpftrace(1) might have accelerated their debugging as compared to inserting stack traces and prints... (1): http://www.brendangregg.com/blog/2018-10-08/dtrace-for-linux...
Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#5Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#6Excellent write-up, I like how they briefly summarized each section so you knew what to expect (I find it helps with understanding). Including the false path is very nice as well since those are very common when debugging.
Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#7Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#8Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#9https://bugzilla.redhat.com/show_bug.cgi?id=1648482
:(
Re: How we spent two weeks hunting an NFS bug in the Linux kernel
#10Great 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.