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

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

Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

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

Contents

  Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Thomas Leuxner <tlx@leuxner.net> - 2018-07-14 18:50 +0200
    Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-07-17 23:00 +0200
    Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Ben Hutchings <ben@decadent.org.uk> - 2018-07-17 23:00 +0200
    Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Ben Hutchings <ben@decadent.org.uk> - 2018-07-18 23:40 +0200
      Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Thomas Leuxner <tlx@leuxner.net> - 2018-07-19 11:40 +0200
        Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Salvatore Bonaccorso <carnil@debian.org> - 2018-07-19 14:50 +0200
          Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Thomas Leuxner <tlx@leuxner.net> - 2018-07-21 12:30 +0200
            Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Salvatore Bonaccorso <carnil@debian.org> - 2018-07-21 13:30 +0200
    Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-07-18 23:40 +0200
    Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-07-21 13:30 +0200
    Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings Stéphane Poignant <stephanepoignant@vialis.net> - 2018-07-25 02:00 +0200

#61405 — Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

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

Package: linux-image-4.9.0-7-amd64
Version: 4.9.110-1

Hi,

after upgrading today I started seeing these:

Jul 14 12:46:18 edi kernel: [   29.601249] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
Jul 14 12:46:24 edi kernel: [   35.920488] sit: non-ECT from 238.163.0.0 with TOS=0x2
Jul 14 12:46:24 edi kernel: [   35.956189] sit: non-ECT from 238.163.0.0 with TOS=0x2
Jul 14 12:46:24 edi kernel: [   35.980514] sit: non-ECT from 238.163.0.0 with TOS=0x2
Jul 14 12:46:25 edi kernel: [   36.207554] sit: non-ECT from 0.12.0.0 with TOS=0xb
Jul 14 12:46:25 edi kernel: [   36.230568] sit: non-ECT from 0.12.0.0 with TOS=0x6
Jul 14 12:46:25 edi kernel: [   36.413928] sit: non-ECT from 0.12.0.0 with TOS=0x6
Jul 14 12:46:25 edi kernel: [   36.437173] sit: non-ECT from 0.12.0.0 with TOS=0x6#

Regards
Thomas

[toc] | [next] | [standalone]

#61442 — Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

Processing control commands:

> tag -1 moreinfo
Bug #903776 [src:linux] Kernel 4.9.110-1 sit: non-ECT warnings
Added tag(s) moreinfo.

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

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

#61443

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

Control: tag -1 moreinfo

On Sat, 2018-07-14 at 18:39 +0200, Thomas Leuxner wrote:
> Package: linux-image-4.9.0-7-amd64
> Version: 4.9.110-1
> 
> Hi,
> 
> after upgrading today I started seeing these:
> 
> Jul 14 12:46:18 edi kernel: [   29.601249] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> Jul 14 12:46:24 edi kernel: [   35.920488] sit: non-ECT from 238.163.0.0 with TOS=0x2
> Jul 14 12:46:24 edi kernel: [   35.956189] sit: non-ECT from 238.163.0.0 with TOS=0x2
> Jul 14 12:46:24 edi kernel: [   35.980514] sit: non-ECT from 238.163.0.0 with TOS=0x2
> Jul 14 12:46:25 edi kernel: [   36.207554] sit: non-ECT from 0.12.0.0 with TOS=0xb
> Jul 14 12:46:25 edi kernel: [   36.230568] sit: non-ECT from 0.12.0.0 with TOS=0x6
> Jul 14 12:46:25 edi kernel: [   36.413928] sit: non-ECT from 0.12.0.0 with TOS=0x6
> Jul 14 12:46:25 edi kernel: [   36.437173] sit: non-ECT from 0.12.0.0 with TOS=0x6#

I con't see any changes in the sit driver's receive path since the
previous upstream version (4.9.88), and we don't have any Debian-
specific patches for it, so I don't think this is the result of a
regression.

Is it possible that the network configuration applied after reboot is
not the same as you had applied previously?

The sit module has a module parameter (log_ecn_error) that controls
this log message.  Perhaps that was set to 0/N previously?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

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

#61468

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

Control: tag -1 - moreinfo

On Wed, 2018-07-18 at 22:31 +0200, Thomas Leuxner wrote:
> * Ben Hutchings <ben@decadent.org.uk> 2018.07.17 22:52:
> 
> > > Jul 14 12:46:18 edi kernel: [   29.601249] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> > > Jul 14 12:46:24 edi kernel: [   35.920488] sit: non-ECT from 238.163.0.0 with TOS=0x2
> > > Jul 14 12:46:24 edi kernel: [   35.956189] sit: non-ECT from 238.163.0.0 with TOS=0x2
> > > Jul 14 12:46:24 edi kernel: [   35.980514] sit: non-ECT from 238.163.0.0 with TOS=0x2
> > > Jul 14 12:46:25 edi kernel: [   36.207554] sit: non-ECT from 0.12.0.0 with TOS=0xb
> > > Jul 14 12:46:25 edi kernel: [   36.230568] sit: non-ECT from 0.12.0.0 with TOS=0x6
> > > Jul 14 12:46:25 edi kernel: [   36.413928] sit: non-ECT from 0.12.0.0 with TOS=0x6
> > > Jul 14 12:46:25 edi kernel: [   36.437173] sit: non-ECT from 0.12.0.0 with TOS=0x6#
> > 
> > I con't see any changes in the sit driver's receive path since the
> > previous upstream version (4.9.88), and we don't have any Debian-
> > specific patches for it, so I don't think this is the result of a
> > regression.
> > 
> > Is it possible that the network configuration applied after reboot is
> > not the same as you had applied previously?
> 
> Hi,
> 
> the network configuration hasn't changed.
>  
> > The sit module has a module parameter (log_ecn_error) that controls
> > this log message.  Perhaps that was set to 0/N previously?
> 
> I could mitigate the noise by applying:
> 
> echo N > /sys/module/sit/parameters/log_ecn_error
> 
> So you may be right, maybe the default has changed?

No, I don't believe the default has changed.  I was suggesting that
perhaps that parameter had been changed on this system before the
reboot.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

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

#61499

* Ben Hutchings <ben@decadent.org.uk> 2018.07.18 23:28:

> No, I don't believe the default has changed.  I was suggesting that
> perhaps that parameter had been changed on this system before the
> reboot.

Well I haven't changed it. There is a recent ticket submitted (for another Kernel) which seems to indicate it has been changed upstream:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772775

Regards
Thomas

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

#61503

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

Hi,

On Thu, Jul 19, 2018 at 11:28:28AM +0200, Thomas Leuxner wrote:
> * Ben Hutchings <ben@decadent.org.uk> 2018.07.18 23:28:
> 
> > No, I don't believe the default has changed.  I was suggesting that
> > perhaps that parameter had been changed on this system before the
> > reboot.
> 
> Well I haven't changed it. There is a recent ticket submitted (for
> another Kernel) which seems to indicate it has been changed
> upstream:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772775

Can you check if the attached patch fixes the issue for you?

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2

Regards,
Salvatore

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

#61526

* Salvatore Bonaccorso <carnil@debian.org> 2018.07.19 14:38:

> Can you check if the attached patch fixes the issue for you?
> 
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
> 
> Regards,
> Salvatore

Thanks Salvatore. That regression fix did indeed fix it:

# uname -v
#1 SMP Debian 4.9.110-1a~test (2018-07-21)

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

#61528

Control: tags -1 + pending patch confirmed

On Sat, Jul 21, 2018 at 12:22:44PM +0200, Thomas Leuxner wrote:
> * Salvatore Bonaccorso <carnil@debian.org> 2018.07.19 14:38:
> 
> > Can you check if the attached patch fixes the issue for you?
> > 
> > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
> > 
> > Regards,
> > Salvatore
> 
> Thanks Salvatore. That regression fix did indeed fix it:

Thanks a lot for confirming. I applied the patch to our stretch
branch!

Regards,
Salvatore

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

#61471 — Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

Processing control commands:

> tag -1 - moreinfo
Bug #903776 [src:linux] Kernel 4.9.110-1 sit: non-ECT warnings
Removed tag(s) moreinfo.

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

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

#61527 — Processed: Re: Bug#903776: Kernel 4.9.110-1 sit: non-ECT warnings

Processing control commands:

> tags -1 + pending patch confirmed
Bug #903776 [src:linux] Kernel 4.9.110-1 sit: non-ECT warnings
Added tag(s) patch, confirmed, and pending.

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

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

#61549

On Sat, Jul 21, 2018 at 12:22:44PM +0200, Thomas Leuxner wrote:
 > * Salvatore Bonaccorso <carnil@debian.org> 2018.07.19 14:38:
 >
 > > Can you check if the attached patch fixes the issue for you?
 > >
 > > 
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
 > >
 > > Regards,
 > > Salvatore
 >
 > Thanks Salvatore. That regression fix did indeed fix it:


Hello,

I'm using the sit module to establish a 6in4 tunnel to connect to my 
IPv6 tunnel broker.

Two days ago, I upgraded from 4.9.0-6-amd64 to 4.9.0-7-amd64 and started 
experiencing random connection failures on IPv6 traffic. It looked like 
the new kernel was dropping some packets received from the remote tunnel 
endpoint (tcpdump saw them coming on the IPv4 interface but not on the 
IPv6 tunnel interface, and they were not processed by the host nor 
forwarded).

The link with the upgrade was confirmed since downgrading back to 
4.9.0-6-amd64 made the issue disappear.

After further testing I made the assumption that the triggering factor 
was a value of 1 for the third and forth bits of the IPv6 header Flow 
Label field, which I then successfully confirmed by generating traffic 
with arbitrary Flow Label values. 100% of the ping requests matching the 
condition were dropped, and 100% of those not matching the condition 
were answered.

I also noticed that everytime a packet was dropped, a line similar to 
this one appeared in the dmesg:

sit: non-ECT from 74.232.98.121 with TOS=0x3

It happens that the offset of those two bits relative to the beginning 
of the IPv6 header is the same as the offset of the ECN field relative 
to the start of a IPv4 header. In addition, the reported IP and TOS 
values were always matching the data at offset 11 and 1 of the 
encapsulated IPv6 header, which happens to be the same offset than the 
Source IP address and TOS fields in a IPv4 header.

In the light of this, I started suspecting that something inside the 
kernel was mistakenly interpreting the inner IPv6 header as an IPv4 
header and was probably the cause of the problem.

I then found this bug report after searching for the aforementioned 
dmesg message. And it turned out that there is clearly a link with my 
IPv6 issue: I was no longer reproducing with an kernel image built from 
since 4.9.110-1 with David S. Miller patch applied (and without changing 
anything else).

It looks like this bug has probably more severe consequences than only 
dmesg spam.

Best regards,
Stephane Poignant

[toc] | [prev] | [standalone]

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

csiph-web