From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: CU178 kernel fixes Testing Date: Mon, 14 Aug 2023 15:03:53 +0100 Message-ID: <7CF60D2C-D9FE-4ED3-9711-98868E51E034@ipfire.org> In-Reply-To: <82b3acc4-29d5-47c2-9058-2e512fdb6e72@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4119958745345387772==" List-Id: --===============4119958745345387772== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, > On 14 Aug 2023, at 12:26, Adolf Belka wrote: >=20 > Hi All, >=20 >=20 > I didn't see any further notification about the kernel fixes in CU178 being= available to test but looking in the Changelog in the nightlies it seemed th= at the fixes were available in the CU178 version in master. Sorry for the confusion. Arne and I made a quick plan how to move forward wit= h all those large security issues over the phone. Since I was traveling last week I didn=E2=80=99t have a chance to test the up= date (so that at least a second pair of eyeballs has confirmed that we don=E2= =80=99t break things really) before the announcement went out. This morning, = I installed the update and pretty much immediately pressed the button for the= announcement. > So I have tested it on 2 vm systems that I have. >=20 > After update the systems were on 178 Development Build master/41e33931. Dur= ing the reboot on both systems no issues were found and no red warning messag= es. Very good! We decided to push all those changes straight to the master branch so that we= gain more testers quickly and moved c178 to 179 and left that in next. In or= der to be able to release the update as quickly as possible, we didn=E2=80=99= t back port anything else from next into master as we couldn=E2=80=99t find a= nything that is *really* urgent. > OpenVPN RW and N2N both worked as normal after the update. >=20 > Ran for a couple of hours and did a range of web activities. >=20 > Everything worked as expected and all graphs reviewed showed data as normal= ly expected. >=20 >=20 > No problems found. That is the stuff I want to hear :) Unless someone reports any new regressions, I would like to release this upda= te maybe on Wednesday or Thursday. Best, -Michael >=20 >=20 > Regards, >=20 > Adolf. >=20 >=20 --===============4119958745345387772==--