Public bug reported:
[Impact]
Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" in
ethtool) to be disabled by default, yet previously it was enabled.
[Fix]
Backport upstream patch to fix the regression
[Testcase]
Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed
package.
[Regression Potential]
Link features were incorrectly initialised, this fix changes the initialisation
code back to the correct default values. This changes the defaults back to what
they are in all other releases. Users on zesty release may have been accustomed
to the wrong defaults and may need to adjust .link files to e.g. disable tso if
that is the behavior they want.
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Zesty)
Importance: Medium
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Affects: systemd (Debian)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #864073
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864073
** Changed in: systemd (Debian)
Remote watch: None => Debian Bug tracker #864073
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Zesty)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates
** Changed in: systemd (Ubuntu Zesty)
Importance: Undecided => Medium
** Bug watch added: github.com/systemd/systemd/issues #4650
https://github.com/systemd/systemd/issues/4650
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4650
Importance: Unknown
Status: Unknown
** Description changed:
- Imported from Debian bug http://bugs.debian.org/864073:
+ [Impact]
+ Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso"
in ethtool) to be disabled by default, yet previously it was enabled.
- Received: (at submit) by bugs.debian.org; 3 Jun 2017 23:56:35 +0000
- From [email protected] Sat Jun 03 23:56:35 2017
- X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
- (2014-02-07) on buxtehude.debian.org
- X-Spam-Level:
- X-Spam-Status: No, score=-7.9 required=4.0 tests=BAYES_00,DKIM_SIGNED,
- DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HAS_PACKAGE,HTML_MESSAGE,MULTALT,
- MURPHY_DRUGS_REL8,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_CNKR,VERSION
autolearn=ham
- autolearn_force=no version=3.4.0-bugs.debian.org_2005_01_02
- X-Spam-Bayes: score:0.0000 Tokens: new, 34; hammy, 129; neutral, 51; spammy,
- 1. spammytokens:0.937-+--H*c:alternative hammytokens:0.000-+--systemd,
- 0.000-+--H*RU:232, 0.000-+--Hx-spam-relays-external:232,
0.000-+--ethtool,
- 0.000-+--Severity
- Return-path: <[email protected]>
- Received: from mail-oi0-x232.google.com ([2607:f8b0:4003:c06::232])
- by buxtehude.debian.org with esmtps
(TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
- (Exim 4.84_2)
- (envelope-from <[email protected]>)
- id 1dHIuJ-0007iH-Kl
- for [email protected]; Sat, 03 Jun 2017 23:56:35 +0000
- Received: by mail-oi0-x232.google.com with SMTP id l18so126707621oig.2
- for <[email protected]>; Sat, 03 Jun 2017 16:56:35 -0700 (PDT)
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
- d=gmail.com; s=20161025;
- h=mime-version:from:date:message-id:subject:to;
- bh=P2s8Tvq4CKfz8W5Y78Uo8cfNYa4L2UwP9RdxKouji8g=;
- b=EWkqFcZK7Kkfwtk661e1D8cmK+WwRDrg+sMFsg2tImUjaeG5/BdKTC+6hNkNnxSQB0
- /O65qCiNFIi0aI62FYoxv7IPN4276UB0v2Df7sI/JYTUJsAXCY+Ta8/ertXL7kGB30TQ
- zuvtvbIpZzCjaMx23BQ5YGI/axd/4XK4ue3m1vHFx9OkNc5+CdIeS/ZshIgDqv6RaLfb
- SERlSH1tRs8h+wwoG3UVtcJAIgr60N17hJAM6W02AtdOhApM3Dtr1xZ/ised74S3yuhE
- diiH14LL5dczRdU+vRBIHMHvCe09IQFL/cQUQ3uwkSV8LkfY5ZzHrVEukF3Waf2k8Fu1
- 4VGw==
- X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
- d=1e100.net; s=20161025;
- h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
- bh=P2s8Tvq4CKfz8W5Y78Uo8cfNYa4L2UwP9RdxKouji8g=;
- b=LDYps3bKd1vchc/VgOT/jCUYUr67qu+1u8lQXVzypiMHy3hq2YROHyllwonrwRZ6SF
- QdjjAFfrYdDYrY5Q+9EXaIqQ+WhVibhWqva9U/jiMVLv28yyMtdhqILepvsBMhCOPl2D
- RSTff+8AqTky8tfMzsbBH8ThVs+hleVCpP1jIWq6/xJQch9oQeFM0vaAJjVLVRZVFGIS
- AdXGpJj98i4vKecSUZzqFDxdXE34ehRH+k9DeEWP3dfdIHa7GWxkAcJ8kFwuKSY3pc/t
- gIhYbpNI5rMofNJSAJgS2hy74JpG+lnn6KtJeC0JoTuB38EfvAdm17z+kMrAjsSNWJv/
- hgkw==
- X-Gm-Message-State: AODbwcAjYRNipjL/v3Tu9K7r4EQ6JybB9Hg9Lo1nUqCPRkD6BAocantB
- 3aK1M/erRNk6IUSwrjZZXlP+YVChyPk3bVQ=
- X-Received: by 10.202.215.4 with SMTP id o4mr8080572oig.86.1496534188802; Sat,
- 03 Jun 2017 16:56:28 -0700 (PDT)
- MIME-Version: 1.0
- Received: by 10.157.19.53 with HTTP; Sat, 3 Jun 2017 16:56:28 -0700 (PDT)
- From: Hans-Kristian Bakke <[email protected]>
- Date: Sun, 4 Jun 2017 01:56:28 +0200
- Message-ID:
<CAD_cGvF9JVKquPhZ95owhUe2m+cdaxzf=ww1gvp_sgxtcbr...@mail.gmail.com>
- Subject: TCP offloads disabled by default
- To: [email protected]
- Content-Type: multipart/alternative; boundary="001a113d5154b7da370551170435"
- Delivered-To: [email protected]
+ [Fix]
+ Backport upstream patch to fix the regression
+
+ [Testcase]
+ Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed
package.
+
+ [Regression Potential]
+ Link features were incorrectly initialised, this fix changes the
initialisation code back to the correct default values. This changes the
defaults back to what they are in all other releases. Users on zesty release
may have been accustomed to the wrong defaults and may need to adjust .link
files to e.g. disable tso if that is the behavior they want.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703393
Title:
TCP offloads disabled by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1703393/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
