Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #77591 > unrolled thread

Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u Adi Kriegisch <adi@kriegisch.at> - 2022-12-13 16:30 +0100
    Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u Diederik de Haas <didi.debian@cknow.org> - 2022-12-13 17:20 +0100
      Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u Adi Kriegisch <adi@kriegisch.at> - 2022-12-13 22:00 +0100
    Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u Salvatore Bonaccorso <carnil@debian.org> - 2022-12-13 22:30 +0100
    Bug#1026035: marked as done (xen netback broken with  5.10.0-20-amd64 in s-p-u) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-13 22:30 +0100
    Bug#1026035: marked as done (xen netback broken with  5.10.0-20-amd64 in s-p-u) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-22 22:40 +0100

#77591 — Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

[Multipart message — attachments visible in raw view] — view raw

Source: linux
Version: 5.10.158-1

Dear maintainers,

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.

We can see packets arrive at the domU and packets leave the domU; but they
never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
counters stay at 0 too).

When migrating the domU back to the other server which has not been
upgraded, the machine is reachable again.

If there is anything we can do to help fixing that issue, we'll gladly do
that!

Thank you very much!

-- Adi

[toc] | [next] | [standalone]

#77593

[Multipart message — attachments visible in raw view] — view raw

On Tuesday, 13 December 2022 15:40:04 CET Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
> 
> 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!

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

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
id=9e624651859214fb2c4e442b059eba0aefcd0801

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.

If you have any questions, feel free to ask them.

[toc] | [prev] | [next] | [standalone]

#77596

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#77599

Source: linux
Source-Version: 5.10.158-2

Hi Adi,

On Tue, Dec 13, 2022 at 03:40:04PM +0100, Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
> 
> Dear maintainers,
> 
> 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.
> 
> We can see packets arrive at the domU and packets leave the domU; but they
> never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
> counters stay at 0 too).
> 
> When migrating the domU back to the other server which has not been
> upgraded, the machine is reachable again.
> 
> If there is anything we can do to help fixing that issue, we'll gladly do
> that!
> 
> Thank you very much!

This is adressed with a subsequent upload which should hit the archive
soon and hopefully in time for the point release (I did miss to close
this bug with the upload, doing so manually to have proper version
tracking).

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#77600 — Bug#1026035: marked as done (xen netback broken with 5.10.0-20-amd64 in s-p-u)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 13 Dec 2022 22:17:33 +0100
with message-id <Y5jr7djlwfqFkiQ/@eldamar.lan>
and subject line Re: Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u
has caused the Debian Bug report #1026035,
regarding xen netback broken with 5.10.0-20-amd64 in s-p-u
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1026035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77688 — Bug#1026035: marked as done (xen netback broken with 5.10.0-20-amd64 in s-p-u)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 22 Dec 2022 21:26:49 +0000
with message-id <E1p8T5V-003Tw5-NI@fasolo.debian.org>
and subject line Bug#1026035: fixed in linux 6.1.1-1~exp1
has caused the Debian Bug report #1026035,
regarding xen netback broken with 5.10.0-20-amd64 in s-p-u
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1026035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web