[09:12] fling, the focal:linux kernel is a 5.4 kernel and has shiftfs applied; they are fairly discrete iirc so you should be able to find them there [09:39] apw: how to figure out which commits do I need? [09:40] apw: if I extract only patches affecting shiftfs.c then I can successfully apply them on kernels up to 5.4.48 [09:40] apw: but it produces warning with 5.4.49+ [09:50] apw: is not there a branch or something with all the needed commits? [11:21] fling, i don't track it that closely, sorry [11:25] apw: who should I ask about this? [11:26] fling, sforshee _may_ have more information [11:57] sforshee: Hello. [12:06] fling: there is no separate tree for shiftfs, just the commits to shiftfs.c should be enough. There are a also a handful of commits to overlayfs to support mounting over shiftfs, I think that's all of it [12:07] sforshee: should I somehow filter out overlayfs commits too? [12:08] fling: you don't need the overlayfs commits unless you want that functionality, but you also likely need to include the patches for mounting overlayfs in user namespaces [12:09] so how do I distinguish these commits? [12:09] if I use commits affecting shiftfs.c on 5.4.49 or later it produces a warning [12:10] what warning? [12:11] 1 [12:20] * Applying 5401-UBUNTU-SAUCE-shiftfs-uid-gid-shifting-bind-mount.patch ... [12:20] Hunk #1 succeeded at 96 with fuzz 1 (offset 1 line). [12:24] fling: almost certainly just some contest difference in kconfig or makefile, just check that the result looks the same as in the patch and everything should be fine [12:25] *context difference [13:13] sforshee: shiftfs.c you mean? [13:14] thanks! [13:15] sforshee: also how do I figure out which overlayfs commits are not from upstream? [13:53] fling: any non-upstream patches should start with "UBUNTU: SAUCE:" [14:16] oh === JanC is now known as Guest49463 === JanC_ is now known as JanC