=== chris14_ is now known as chris14 === arraybolt3 is now known as arraybolt3_tl === arraybolt3_tl is now known as arraybolt3 [16:35] fling, linux-oem-6.1? I think that's the only 6.1 kernel that is still around... [17:08] juergh: what is the git tree / branch / tag for it? [17:14] reading, isn't it < 6.5 if a commit is there? [17:15] commit: 91562895f803 ("ext4: properly sync file size update after O_SYNC direct IO") [17:15] thank you! [17:32] I'm really struggling to figure out which linux-aws packages have or do not have the ext4 corrpution bug. As far as I can tell, the current 'linux-image-aws-lts-22.04' is okay, include about the main 'linux-aws' package. Curious if there's a great way to sort this out as an end user, I'm trying to use https://code.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy currently. [20:02] jchittum: 91562895f803 is 6.6, not 6.1 [20:03] which tree is for linux-oem-6.1? === cascardo_ is now known as cascardo [21:43] ghavil : i don't think any of the current linux-aws packages should be affected. None are version 6.1. it's not affecting 6.2 in Ubuntu, so 22.04 linux-aws will be fine. all the others are older and unaffected (22.04 lts and 20.04 HWE are at 5.15, 20.04 LTS and 18.04 HWE are at 5.4) [21:43] nothing will have hit Ubuntu yet, as the commit was grabbed in Debian first. and now we know about it [21:44] Ah okay yeah, I kinda figured as much since I couldn't find the commit in the ubuntu sources either [21:45] I was originally worried as https://lore.kernel.org/stable/81a11ebe-ea47-4e21-b5eb-536b1a723168@linaro.org/ mentions 'linux-5.15' and I know the lts package is on 5.15 so I was worried it might have gotten grabbed. Happy to see it wasn't, that'll let me sleep easier tonight! [21:59] but where can I find recent-ish 6.1 with shiftfs? [22:04] ghavil: that ext4 bug is fixed with iomap: update ki_pos a little later in iomap_dio_complete [22:06] https://lwn.net/Articles/954285/