ChanServ changed the topic of #io_uring to: io_uring development discussion | Logs: https://oftc.irclog.whitequark.org/io_uring
<axboe> in terms of stable, as of recently, 5.10-stable and 5.15-stable have the exact same io_uring base. this was done to get the native workers backported to 5.10-stable, as the kthreads were a source of perpetual concern
<axboe> the main benefit is that we just have to focus on one identical core of code for 5.10/5.15 stable
<axboe> in any case, a bisect should still work fine
<axboe> what is the issue?
sgarzare has joined #io_uring
sgarzare_ has joined #io_uring
sgarzare__ has joined #io_uring
sgarzare has quit [Ping timeout: 480 seconds]
sgarzare_ has quit [Ping timeout: 480 seconds]
sgarzare__ has quit [Ping timeout: 480 seconds]
sgarzare has joined #io_uring
<cengiz_io> axboe: huge thanks for clarifying that. I need to check and backport some fixes to Ubuntu kernels (I can't share them here but you obviously already know which ones). Since there is a requirement to identify the `Fixes` hashes, I'm struggling a bit :)
<axboe> cengiz_io: makes sense
<cengiz_io> axboe: moving from ktreads certainly sound like a good indicator to track the changes. much appreciated.
<axboe> yep, this officially happened in the 5.11 release, the recent 5.10-stable backport just picked 5.15-stable to bring back to 5.10-stable to consolidate the stable bases too
sgarzare has quit [Quit: Leaving]