From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Should we go for Linux 5.15.64 for Core Update 170? Date: Mon, 05 Sep 2022 10:59:34 +0100 Message-ID: <8000BCF6-4215-4D1F-A9D1-F63AC48C036B@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4225454250604026084==" List-Id: --===============4225454250604026084== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 2 Sep 2022, at 17:45, Peter M=C3=BCller wro= te: >=20 > Hello development folks, >=20 > earlier today, I came across https://cdn.kernel.org/pub/linux/kernel/v5.x/C= hangeLog-5.15.64, in > which several commits caught my attention, particularly all those in the tc= p/netfilter subsystems. The kernel log always reads a bit scary. And yes, if in doubt, I would prefer= to rather ship one kernel too many. However, this massively breaks our development model and makes the entire sta= bilisation phase a lot harder - and we are already struggling with that. Now, .65 is already out as well. I wouldn=E2=80=99t object to update to this,= but I am very short on time this week and really would like to see the updat= e going out soon. > Generally, I am not a fan of updating the kernel in Core Updates while they= are already in > testing (unless something is badly broken, of course), since this is an uph= ill battle, and in > the past has delayed releases quite notably. Agreed. > Therefore, I would be grateful for input, since I am not too sure how to ju= dge the severity of > these aforementioned kernel commits. Is this something we should bring to o= ur users sooner rather > than later? Does anything strike you as "hey, we have dealt with this bug f= or ages, and it is > finally resolved upstream"? I didn=E2=80=99t spot anything that would be incredibly scary, but I agree th= at there is an unusually high amount of networking patches in this release. -Michael > Thanks in advance, and best regards, > Peter M=C3=BCller --===============4225454250604026084==--