News for hackers. Stuff that matters.
Re:How we spent two weeks hunting an NFS bug in the Linux ke... by drewg123 on Wednesday November 28, 2018 @07:48PM (#18557205)
I 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 ke... by lbotos on Thursday November 29, 2018 @02:00AM (#18558595)
We're getting there! :) I've asked my team to balance learning K8s with new learning lower level debugging tools like bcc and it's cohort.
Re:How we spent two weeks hunting an NFS bug in the Linux ke... by sofaofthedamned on Thursday November 29, 2018 @03:28AM (#18558850)
That's awesome. I see too many younger staff know the hotness but not the fundamentals, and not enough employers care. I've had to strace a K8s cluster before where it turned out the problem was in kube-dns.

We are relearning the same things we did wrong in the 90s once we got nice libraries and middleware, i.e. to forget the platform we're building on.

Re:How we spent two weeks hunting an NFS bug in the Linux ke... by kelleyk on Wednesday November 28, 2018 @09:00PM (#18557476)
Out of curiosity, what do you do that you get to do that? Sounds fascinating---I've had lots of fun with dtrace (and, more recently, bcc).
Re:How we spent two weeks hunting an NFS bug in the Linux ke... by drewg123 on Thursday November 29, 2018 @07:36AM (#18559738)
I work for Netflix on Open Connect, the Netflix CDN. We run a modified FreeBSD on our CDN nodes. My job involves improving performance and scalability in the FreeBSD kernel. See https://medium.com/netflix-techblog/serving-100-gbps-from-an... Very much like the NFS article author describes, I also tend to find "naive" solutions that end up being polished a lot before landing upstream.