[12:10] <pent1ckel> 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] <pent1ckel> my question is: how to get this patch backported to supported Ubuntu18 kernels
[12:10] <apw> pent1ckel, i assume you mean 18.04
[12:11] <pent1ckel> I'm sorry. yes I meant 18.04 apw 
[12:12] <apw> 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] <pent1ckel> so it is very new I would say
[12:13] <apw> it is a few weeks old, so there is hope
[12:20] <apw> pent1ckel, no not made it to stable; so to get it into ubuntu more agressivly you should file a bug
[12:20] <apw> against the kernel (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug)
[12:20] <apw> and add the detail of the commit which fixes it and which series are affected
[12:20] <apw> and let us know here the #
[12:21] <pent1ckel> 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] <apw> pent1ckel, thanks
[12:22] <pent1ckel> apw: is there a list where I also could have searched for this patch and the current state?
[12:22] <apw> pent1ckel, the stable tree is where i looked to see if it was going to be coming soon
[12:22] <apw> pent1ckel, as it is not, it really is only in linus' tree
[12:24] <pent1ckel> it is in mainline as well. I've downloaded 5.4.0 and it is there
[12:24] <pent1ckel> or did I understood you wrong?
[12:24] <apw> pent1ckel, the bug is present ?
[12:24] <apw> or the fix is present
[12:25] <apw> the fix is present in 5.4-rc8 i think i saw
[12:25] <pent1ckel> 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] <pent1ckel> here it is
[12:26] <apw> right it is in only in linus' tree at this time; it has not made it to the stables yet
[12:26] <apw> which is why we are talking about a bug
[12:27] <pent1ckel> 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] <apw> that is not a kernl produced by the upstream stable team
[12:28] <pent1ckel> ohhh
[12:28] <apw> it is a final version of the development kernel
[12:28] <pent1ckel> ok. I'm sorry. this is new to me
[12:28] <apw> it will be the kernel in our devleopment release soon
[12:28] <pent1ckel> understand. I will verify and file the bug
[12:28] <apw> selected fixes from the primary kernel get backportedd and put out as updates to older upstream versions
[12:29] <apw> and we use those to see fixes for our kernels based on those versions
[12:29] <pent1ckel> sure ... it is caled mainline ... now I got it. sorry for misunderstanding
[12:30] <pent1ckel> I'm sorry. I nenver recognized this
[12:30] <apw> pent1ckel, no need to appologise, it is complex, and the relationships between the kernels produced by distros and upstream even more so
[12:31] <pent1ckel> apw: thank a lot. also I learned somethign new today
[18:03] <mcphail> 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?
[20:26] <apw> mcphail, there is a wireguard package in ubuntu you could file them against i guess
[20:32] <mcphail> 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] <apw> mcphail, the oops will always be key to solving that kind of thing i would think
[21:12] <mcphail> 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:13] <apw> mcphail, could you subscribe launchpad user apw to it
[21:15] <mcphail> apw: done