[12:10] I'm using Ubuntu18 together with Strongswan and figured out that there is a memoryleak which is solved in mainline kernel already: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86c6739eda7d2a03f2db30cbee67a5fb81afa8ba [12:10] my question is: how to get this patch backported to supported Ubuntu18 kernels [12:10] pent1ckel, i assume you mean 18.04 [12:11] I'm sorry. yes I meant 18.04 apw [12:12] pent1ckel, that sounds like the sort of thing which might come to us via stable; /me looks to see if it is pending [12:12] so it is very new I would say [12:13] it is a few weeks old, so there is hope [12:20] pent1ckel, no not made it to stable; so to get it into ubuntu more agressivly you should file a bug [12:20] against the kernel (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug) [12:20] and add the detail of the commit which fixes it and which series are affected [12:20] and let us know here the # [12:21] ok. so I will first verify this agains ubuntu kernel by my self (tested already with vanilla kernel) and created this bug with all information included [12:21] pent1ckel, thanks [12:22] apw: is there a list where I also could have searched for this patch and the current state? [12:22] pent1ckel, the stable tree is where i looked to see if it was going to be coming soon [12:22] pent1ckel, as it is not, it really is only in linus' tree [12:24] it is in mainline as well. I've downloaded 5.4.0 and it is there [12:24] or did I understood you wrong? [12:24] pent1ckel, the bug is present ? [12:24] or the fix is present [12:25] the fix is present in 5.4-rc8 i think i saw [12:25] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/net/xfrm/xfrm_state.c?id=v5.4&id2=v5.3 [12:25] here it is [12:26] right it is in only in linus' tree at this time; it has not made it to the stables yet [12:26] which is why we are talking about a bug [12:27] just to understand: https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.4.tar.xz this is not stable? there it is included [12:28] that is not a kernl produced by the upstream stable team [12:28] ohhh [12:28] it is a final version of the development kernel [12:28] ok. I'm sorry. this is new to me [12:28] it will be the kernel in our devleopment release soon [12:28] understand. I will verify and file the bug [12:28] selected fixes from the primary kernel get backportedd and put out as updates to older upstream versions [12:29] and we use those to see fixes for our kernels based on those versions [12:29] sure ... it is caled mainline ... now I got it. sorry for misunderstanding [12:30] I'm sorry. I nenver recognized this [12:30] pent1ckel, no need to appologise, it is complex, and the relationships between the kernels produced by distros and upstream even more so [12:31] apw: thank a lot. also I learned somethign new today [18:03] Hello. I've had 2 lock-ups in the past week when using wireguard with ubuntu-mate 19.10. I have .crash files in /var/crash which don't seem to be being sent by apport despite me selecting "report problem". Should I post them somewhere? === ben_r_ is now known as ben_r [20:26] mcphail, there is a wireguard package in ubuntu you could file them against i guess [20:32] apw: OK, will do. Wondered if the oops was useful to you guys. I wish I could work out how to trigger it again [20:40] mcphail, the oops will always be key to solving that kind of thing i would think [21:12] Ta. Have filed at https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1854225 and temporarily marked as "private" due to the info about the null pointer dereference [21:12] Error: ubuntu bug 1854225 not found [21:13] mcphail, could you subscribe launchpad user apw to it [21:15] apw: done