Dear Diederik,
> > we just upgraded our xen test cluster's kernel to the latest kernel from
> > s-p-u and noticed that network communication is broken. We do have a
> > 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> > communication is possible for the domU.
> >
> > If there is anything we can do to help fixing that issue, we'll gladly do
> > that!
thank you very much for your help!
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 describes a (relatively simple) way to test a patch.
>
> I found in current master/6.1 branch 2 commits which may be relevant:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
> id=7dfa764e0223a324366a2a1fc056d4d9d4e95491
This patch did the trick; while digging through the source, I noticed that
this fix is already included in the patch for XSA-423[1][2] referenced at
the oss-sec list.
Obviously the patch for XSA-423v1 has been included in 5.10.158-1 while
XSA-423v2 is the most recent version of the patch. The difference between
the two versions of that patch is exactly the initialization of the variable
'err' that just fixes this issue.
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
> id=9e624651859214fb2c4e442b059eba0aefcd0801
This patch does not seem to be necessary as the patch for XSA-424 does
alreay contain a different fix for this issue.
> You'd possibly need to backport it to the 5.10 code, but if you can do that
> and test whether the updated kernel fixes the issue, that would be great.
Again: thank you very much for the quick response. I can confirm that the
issue is indeed fixed with the first patch; maybe updating to XSA-423v2 is
the more appropriate way to fix the issue.
all the best,
Adi
[1] https://seclists.org/oss-sec/2022/q4/174
[2] https://seclists.org/oss-sec/2022/q4/att-174/xsa423-linux.patch
Attachment:
signature.asc
Description: PGP signature