Introducing systing| Josef Bacik’s Blog
tl;dr| Josef Bacik’s Blog
tl;dr| Josef Bacik’s Blog
tl;dr Use b4 to apply random patches locally for patch review. Use lei to pull down emails and pathces you care about for all linux kernel mailinglists locally. Use mutt to read that email and respond. Use msmtp for sending email using your email server’s settings.| Josef Bacik’s Blog
tl;dr| Josef Bacik’s Blog
tl;dr| Josef Bacik’s Blog
tl;dr Learn how to use BPF/BCC/bpftrace, they will make your life so much easier. I dump all of my scripts I write here, they are mostly very raw, but good starting points for “how the hell do I do X”.| Josef Bacik’s Blog
tl;dr Fedora Workstation and all of its descendants are switching to btrfs by default, hooray! The core btrfs team is organizing more under Github. Development update. I’m going to attempt to be more communicative about what we as the btrfs community are up to development wise and priority wise.| Josef Bacik’s Blog
The problem.| Josef Bacik’s Blog
tl;dr We (the Btrfs team) have a new testing setup that uses GitHub actions, you can find the yml here. Running fstests requires a two step process, one to build the kernel and deploy it onto the runners, then the step to run the tests on the runners. The GitHub self hosted runner masks SIGPIPE, which is pretty necessary for any shell based testing, so you need a wrapper like the one provided below to keep things from breaking.| Josef Bacik’s Blog