Not every day you can say you were complemented by Linus Torvalds saying you had an “interesting idea”. Always look for those silver linings!
Fixing up a messed up Debian upgrade where I needed to reinstall, I had to hit “Select this only if you know what you are doing”. I don’t know what I’m doing, but I had to hit it to do what I needed to get done 😛
THIS IS IT!!!
The last hurdle for PREEMPT_RT being merged into mainline has just removed by this pull request. Leaving the door open for PREEMPT_RT to be added to 6.12!
With my new persistent memory mapped ring buffer, were I can retrieve the tracing buffer from the previous boot that crashed, I was able to debug a recent issue. To do this, I added code to allow trace_printk()
to be directed to the persistent ring buffer, along with enabling the printk console trace event (writes all printk()s to the tracing ring buffer), I was able to get the perfect idea of what was happening that lead up to the crash!
https://lore.kernel.org/lkml/20240823013902.135036960@goodmis.org/
A tribute to Daniel Bristot de Oliveira from Linux Plumbers. https://lpc.events/blog/current/index.php/2024/07/06/in-memory-of-daniel-bristot-de-oliveira/
Daniel Bristot de Oliveira passed away on Monday, June 24th at the age of 37. Another sad loss for the Linux kernel developer community, Daniel will be sorely missed.
In memory of Daniel: https://t.co/kQCQyTCo1a
[ stolen from a colleague ]
Linux Plumbers 2024 has accepted 9 Microconferences! But we had 26 submissions for 18 slots! What to do with that? Read about it here: https://lpc.events/blog/current/index.php/2024/05/03/awesome-amount-of-microconference-submissions/
Doing some testing against a change; I ran two traces. Recording the trace before applying the patch as trace-b.dat
and then calling the trace file after applying the patch as trace-a.dat
. Then doing an ls trace*.dat
I have:
trace-a.dat
trace-b.dat
And it looks like trace-a.dat
should come before trace-b.dat
. I’m so confused! 😛
I’m being “schooled” by Al Viro on how dcache, inodes, and files work internally.
This is a very interesting read that I recommend anyone that wants to understand VFS better should look at.
And don’t just stop at that email, the thread goes on. Very educational. Hopefully someone smarter than I can add this to the VFS documentation in the kernel 😉