Besides Linus Torvalds examining various elements of code he's merging and build testing it on his [1]AMD Ryzen Threadripper workstation and now also [2]testing more on ARM64 with Ampere Altra , he does these days still believe in "dogfooding" and is in fact running the leading-edge Linux kernel code even during the merge window.

For those curious how much Linus Torvalds is running "on the edge" of the Linux kernel code even during the very busy merge window: yes, he's still doing so as a big proponent of dogfooding.

During a mailing list discussion yesterday when working through issues that came up from the [3]DRM graphics driver updates for Linux 6.10 , he [4]commented on his current dogfooding approach to the Linux kernel:

[DRM maintainer David Airlie] This worries me actually, it's possible this warn could cause a problem, but I'm not convinced it should have machine ending properties without some sort of different error at the end, so I'd keep an eye open here.

[Linus Torvalds] Well, since I'm a big believer in dogfooding, I always run my own kernel even during the merge window. I don't reboot between each pull, but I try to basically reboot daily.

So there you have it, yes, Linus does continue dogfooding the Linux kernel even during the very busy two week merge window periods where lots of new code (and bugs) are introduced. As for the bug being discussed yesterday the belief was attributed ultimately to Btrfs or [5]the new DRM buddy clear page tracking code . There's already [6]a new pull with a DRM buddy allocator fix.



[1] https://www.phoronix.com/news/Torvalds-Threadripper

[2] https://www.phoronix.com/news/Linus-Torvalds-Ampere-More-ARM

[3] https://www.phoronix.com/news/Linux-6.10-DRM-Graphics

[4] https://lore.kernel.org/lkml/CAHk-=wizH1b8vv67xVSoSHqp5B=dNsqtpP+86RM7G5z14nuRHw@mail.gmail.com/

[5] https://www.phoronix.com/news/DRM-Buddy-Clear-Page-Tracking

[6] https://lore.kernel.org/dri-devel/CAPM=9tx_KS1qc8E1kUB5PPBvO9EKHNkk7hYWu-WwWJ6os=otJA@mail.gmail.com/T/#u