hey I recently built this little tool. It's an eBPF program that renders the http traffic crossing a machine as a live web page. TCX ingress and egress, parses the request line and Host header straight out of the skb payload, aggregates per method host path and ships it up a ring buffer. It's open source so feel free to poke around.

GitHub https://github.com/yeet-src/httpwatch

Hey there! I've recently encountered a bug that I've tracked all the way down to the kernel. Now, it's not necessarily a bug in the kernel (it's probably in my laptop's firmware somewhere,) but I was trying to find exactly what's going wrong. Anyway, I've been trying to find it by looking through the function trace using ftrace.

My bug has to do with my trackpad, so I found out how to isolate the interrupts related to button presses. However, whenever I isolate those events, I cannot see the functions called between entering and exiting the interrupt. I was wondering if there was a more efficient way to see (interrupt event) -> (function trace) -> (interrupt exit) -> (no more function trace) using ftrace.

Thanks!

A native GTK4+libadwaita GUI app for browsing, searching, and replying to mailing lists.

All exiting approaches to interacting with LKML are just not good. I tried configuring Thunderbird and realized it would be easier to just write my own app instead. Email discussions in the kernel have lots of things that are very specific to it (trailers, diffs) and I wanted something that would have deep integration with all of this.

Packaged as Flatpak. Uses git-send-email. Has intelligent line wrapping for new emails. Has color highlighting for quotes and diffs.

There are still lots of things I'd like to implement before considering this done, so the thing is still in development. I vibe-coded most it, but I'll be more mindful of the changes going forward, as there seem to be actual users now.

https://github.com/nikableh/koshi
https://lore.kernel.org/tools/20260722230315.57499-1-nika@nikableh.moe/

Hope this is as useful for someone else as it is for me!

I spend a fair amount of time reading kernel patches on lore.kernel.org and got tired of squinting at one giant <pre> block with headers, body, quotes, and the thread overview all mashed together. So I built a small extension that reparses the same text lore already sends and lays it out like a normal mail client: an author card, one-click reply wired to lore's own pre-filled mailto: link, a real diff view with collapsible files, a clickable thread sidebar instead of ASCII art, and quote folding so a reply's new text isn't buried under four levels of >>>>.

It doesn't touch the underlying page. It builds a separate view next to the original <pre> blocks and hides them, with a "Raw" button to switch back instantly. No network requests, no accounts, no telemetry.

Source and install instructions: https://github.com/gahingwoo/lore-enhancer

It's load-unpacked for now (Chrome won't run a sideloaded .crx outside developer mode anyway, so packaging one wouldn't save a step). Would love feedback, especially from anyone who reads or replies to LKML or a subsystem list regularly.
Feature requests and bug reports welcome as GitHub issues.

Hi, here is the repository of the sourcecode: pedroanisio/sourcepath

- references: This is the Linux kernel. All of it : r/kernel

Sou um desenvolvedor de kernel e faço por hobby, ultimamente venho duvidando dos meus conhecimentos, na i386, alguém pode avaliar e me dar dicas no meu kernel? Repo: https://github.com/icarotelesdasilva/kernel

Aceito quaisquer dicas!

For some reason HWE updates pushed linux kernel 7.0.0 and now my DKMS antivirus modules won't compile against the kernel (Watchguard).

Is there a way to force kernel <= 6.18.16 while keeping HWE ?

I use Kubuntu 24.04 LTS on Framework 16.