On 5/15/26 1:36 PM, Luca Boccassi wrote: > On Fri, 15 May 2026 at 11:32, Kevin Traynor <[email protected]> wrote: >> >> On 4/30/26 12:02 PM, Kevin Traynor wrote: >>> On 4/30/26 10:58 AM, Thomas Monjalon wrote: >>>> 30/04/2026 11:32, Kevin Traynor: >>>>> On 4/21/26 7:46 AM, Shani Peretz wrote: >>>>>> The planned date for the final release is 30 April 2026. >>>>> >>>>> As discussed on thread [0] there was a quite serious regression caused >>>>> by "net: fix packet type for stacked VLAN" >>>>> >>>>> As discussion on the fix is ongoing, I would suggest to just revert this >>>>> patch for your release. >>>> >>>> I agree the revert is the best option here. >>>> >>>>> It doesn't require a new RC and re-validation as it's an isolated issue >>>>> (and there wasn't test cases to catch before Robin's new patch anyway) >>>> >>>> I suppose 24.11.5 and 25.11.1 are also impacted? >>>> >>>> >>> >>> Yes, I was hoping we would have a fix in a few days and we could add and >>> re-release. Given that there's now discussion on the patch and what >>> functionality is needed, it's probably best to just revert and release a >>> new 24.11/25.11. >> >> Hi Luca. Are you planning to do a 24.11 release with revert for above >> issue ? If you have a time issue, let me know and I can help out. > > Hi, is it strictly necessary? Could it wait for the next one? >
It's a user visible regression from the previous release that impacts tap device with VLAN, causing good packets to be discarded. It's also visible to any application using the net API in a similar way. Given the effort is low as it's just a revert and we don't need validation teams involved, then I think it's worthwhile.
