[01:38] <nerdopolis> In https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016398 I have a script that replicates an overlayfs issue that I discovered, I was able to narrow it down to a single downstream commit. is there any more info that I need?
[01:38] -ubottu:#ubuntu-kernel- Launchpad bug 2016398 in linux (Ubuntu) "stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)" [Undecided, Confirmed]
[01:44] <sarnold> nerdopolis: nice :) thanks
[01:58] <nerdopolis> seems related to shiftfs https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/commit/?h=master-next&id=4f140b79ec36db30c9ba2118d966d875bef2a59b I don't know nearly enough on how to fix it though, but yeah, with my scripts, despite the mount namespaces that I mount my overlayfses in being long gone, lsmod says I have several thousand references to the overlayfs module, and the only way to fix it is to 
[01:58] <nerdopolis> reboot
[01:58] -ubottu:#ubuntu-kernel- Commit 4f140b7 in ~ubuntu-kernel/ubuntu/+source/linux/+git/lunar "UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files"
[12:26] <patersonc[m]> Hello, I have a question... If one wants to make changes to config.common.ubuntu, does one submit a patch to kernel-team@lists.ubuntu.com? Or are these Debian configs generated from upstream Linux configs?
[13:02] <arighi> patersonc[m], you can make a change directly to config.common.ubuntu, we (kernel team) maintain our own configs for the Ubuntu kernels. Optionally you can also add a note to debian.<kernel>/config/annotations to make sure your config changes are enforced
[13:03] <arighi> patersonc[m], starting with lunar 22.04 we merged evertyhing into annotations, so the configs are completely generated from the data defined in the annotations file (see https://discourse.ubuntu.com/t/kernel-configuration-in-ubuntu/35857)
[13:14] <patersonc[m]> Thank you arighi!