[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
This bug was fixed in the package linux - 5.8.0-31.33 --- linux (5.8.0-31.33) groovy; urgency=medium * groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299) * Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397) - drm/i915: Mark ininitial fb obj as WT on eLLC machines to avoid rcu lockup during fbdev init * CVE-2020-4788 - selftests/powerpc: rfi_flush: disable entry flush if present - powerpc/64s: flush L1D on kernel entry - powerpc/64s: flush L1D after user accesses - selftests/powerpc: entry flush test linux (5.8.0-30.32) groovy; urgency=medium * groovy/linux: 5.8.0-30.32 -proposed tracker (LP: #1903194) * Update kernel packaging to support forward porting kernels (LP: #1902957) - [Debian] Update for leader included in BACKPORT_SUFFIX * Avoid double newline when running insertchanges (LP: #1903293) - [Packaging] insertchanges: avoid double newline * EFI: Fails when BootCurrent entry does not exist (LP: #183) - efivarfs: Replace invalid slashes with exclamation marks in dentries. * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull codes that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: fix discard limits for raid1 and raid10 - dm raid: remove unnecessary discard limits for raid10 * Bionic: btrfs: kernel BUG at /build/linux- eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! (LP: #1902254) - btrfs: extent_io: do extra check for extent buffer read write functions - btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent() - btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref() - btrfs: ctree: check key order before merging tree blocks * Tiger Lake PMC core driver fixes (LP: #1899883) - platform/x86: intel_pmc_core: update TGL's LPM0 reg bit map name - platform/x86: intel_pmc_core: fix bound check in pmc_core_mphy_pg_show() - platform/x86: pmc_core: Use descriptive names for LPM registers - platform/x86: intel_pmc_core: Fix TigerLake power gating status map - platform/x86: intel_pmc_core: Fix the slp_s0 counter displayed value * drm/i915/dp_mst - System would hang during the boot up. (LP: #1902469) - Revert "UBUNTU: SAUCE: drm/i915/display: Fix null deref in intel_psr_atomic_check()" - drm/i915: Fix encoder lookup during PSR atomic check * Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems (LP: #1902694) - powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation - selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround * [20.04 FEAT] Support/enhancement of NVMe IPL (LP: #1902179) - s390/ipl: support NVMe IPL kernel parameters * uvcvideo: add mapping for HEVC payloads (LP: #1895803) - media: uvcvideo: Add mapping for HEVC payloads * risc-v 5.8 kernel oops on ftrace tests (LP: #1894613) - stop_machine, rcu: Mark functions as notrace * Groovy update: v5.8.17 upstream stable release (LP: #1902137) - xgb4: handle 4-tuple PEDIT to NAT mode translation - ibmveth: Switch order of ibmveth_helper calls. - ibmveth: Identify ingress large send packets. - ipv4: Restore flowi4_oif update before call to xfrm_lookup_route - mlx4: handle non-napi callers to napi_poll - net: dsa: microchip: fix race condition - net: fec: Fix phy_device lookup for phy_reset_after_clk_enable() - net: fec: Fix PHY init after phy_reset_after_clk_enable() - net: fix pos incrementment in ipv6_route_seq_next - net: ipa: skip suspend/resume activities if not set up - net: mptcp: make DACK4/DACK8 usage consistent among all subflows - net: sched: Fix suspicious RCU usage while accessing tcf_tunnel_info - net/smc: fix use-after-free of delayed events - net/smc: fix valid DMBE buffer sizes - net/tls: sendfile fails with ktls offload - net: usb: qmi_wwan: add Cellient MPL200 card - tipc: fix the skb_unshare() in tipc_buf_append() - socket: fix option SO_TIMESTAMPING_NEW - socket: don't clear SOCK_TSTAMP_NEW when SO_TIMESTAMPNS is disabled - can: m_can_platform: don't call m_can_class_suspend in runtime suspend - can: j1935: j1939_tp_tx_dat_new(): fix missing initialization of skbcnt - net: j1939: j1939_session_fresh_new(): fix missing initialization of skbcnt - net/ipv4: always honour route mtu during forwarding - net_sched: remove a redundant goto chain check - r8169: fix data corruption issue on RTL8402 - binder: fix UAF when releasing todo list - ALSA: bebob: potential info leak in hwdep_read() - ALSA: hda/hdmi: fix incorrect
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
This bug was fixed in the package linux - 5.4.0-56.62 --- linux (5.4.0-56.62) focal; urgency=medium * focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300) * CVE-2020-4788 - selftests/powerpc: rfi_flush: disable entry flush if present - powerpc/64s: flush L1D on kernel entry - powerpc/64s: flush L1D after user accesses - selftests/powerpc: entry flush test linux (5.4.0-55.61) focal; urgency=medium * focal/linux: 5.4.0-55.61 -proposed tracker (LP: #1903175) * Update kernel packaging to support forward porting kernels (LP: #1902957) - [Debian] Update for leader included in BACKPORT_SUFFIX * Avoid double newline when running insertchanges (LP: #1903293) - [Packaging] insertchanges: avoid double newline * EFI: Fails when BootCurrent entry does not exist (LP: #183) - efivarfs: Replace invalid slashes with exclamation marks in dentries. * CVE-2020-14351 - perf/core: Fix race in the perf_mmap_close() function * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull codes that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: fix discard limits for raid1 and raid10 - dm raid: remove unnecessary discard limits for raid10 * Bionic: btrfs: kernel BUG at /build/linux- eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! (LP: #1902254) - btrfs: drop unnecessary offset_in_page in extent buffer helpers - btrfs: extent_io: do extra check for extent buffer read write functions - btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent() - btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref() - btrfs: ctree: check key order before merging tree blocks * Ethernet no link lights after reboot (Intel i225-v 2.5G) (LP: #1902578) - igc: Add PHY power management control * Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems (LP: #1902694) - powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation - selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround * [20.04 FEAT] Support/enhancement of NVMe IPL (LP: #1902179) - s390: nvme ipl - s390: nvme reipl - s390/ipl: support NVMe IPL kernel parameters * uvcvideo: add mapping for HEVC payloads (LP: #1895803) - media: uvcvideo: Add mapping for HEVC payloads * Focal update: v5.4.73 upstream stable release (LP: #1902115) - ibmveth: Switch order of ibmveth_helper calls. - ibmveth: Identify ingress large send packets. - ipv4: Restore flowi4_oif update before call to xfrm_lookup_route - mlx4: handle non-napi callers to napi_poll - net: fec: Fix phy_device lookup for phy_reset_after_clk_enable() - net: fec: Fix PHY init after phy_reset_after_clk_enable() - net: fix pos incrementment in ipv6_route_seq_next - net/smc: fix valid DMBE buffer sizes - net/tls: sendfile fails with ktls offload - net: usb: qmi_wwan: add Cellient MPL200 card - tipc: fix the skb_unshare() in tipc_buf_append() - socket: fix option SO_TIMESTAMPING_NEW - can: m_can_platform: don't call m_can_class_suspend in runtime suspend - can: j1935: j1939_tp_tx_dat_new(): fix missing initialization of skbcnt - net: j1939: j1939_session_fresh_new(): fix missing initialization of skbcnt - net/ipv4: always honour route mtu during forwarding - net_sched: remove a redundant goto chain check - r8169: fix data corruption issue on RTL8402 - cxgb4: handle 4-tuple PEDIT to NAT mode translation - binder: fix UAF when releasing todo list - ALSA: bebob: potential info leak in hwdep_read() - ALSA: hda/hdmi: fix incorrect locking in hdmi_pcm_close - nvme-pci: disable the write zeros command for Intel 600P/P3100 - chelsio/chtls: fix socket lock - chelsio/chtls: correct netdevice for vlan interface - chelsio/chtls: correct function return and return type - ibmvnic: save changed mac address to adapter->mac_addr - net: ftgmac100: Fix Aspeed ast2600 TX hang issue - net: hdlc: In hdlc_rcv, check to make sure dev is an HDLC device - net: hdlc_raw_eth: Clear the IFF_TX_SKB_SHARING flag after calling ether_setup - net: Properly typecast int values to set sk_max_pacing_rate - net/sched: act_tunnel_key: fix OOB write in case of IPv6 ERSPAN tunnels - nexthop: Fix performance regression in nexthop deletion - nfc: Ensure presence of NFC_ATTR_FIRMWARE_NAME attribute in nfc_genl_fw_download() - r8169: fix operation under forced interrupt threading - selftests: forwarding: Add missing 'rp_filter' configuration - tcp: fix to update snd_wl1 in bulk receiver fast
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
Landed in Hirsute as well, closing the linux task. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
Verified on groovy: raw csum_off with bad offset (expected to fail) ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
@cypressyew could you confirm this is resolved in -proposed Groovy? Thanks, Ian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1032.33 --- linux-oem-5.6 (5.6.0-1032.33) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1032.33 -proposed tracker (LP: #1899926) * CVE-2020-12351 // CVE-2020-12352 // CVE-2020-24490 - Bluetooth: Disable High Speed by default - Bluetooth: MGMT: Fix not checking if BT_HS is enabled - [Config] Disable BlueZ highspeed support * CVE-2020-12351 - Bluetooth: L2CAP: Fix calling sk_filter on non-socket based channel * CVE-2020-12352 - Bluetooth: A2MP: Fix not initializing all members * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * [SRU]alsa: add Dell tgl soundwire machines support (LP: #1900069) - ALSA: hda: add autodetection for SoundWire - ASoC: Intel: common: add match table for TGL MAX98373 + RT5682 SoundWire driver - ASoC: Intel: soc-acpi: mirror CML and TGL configurations - ASoC: SOF: topology: send ipc for all found DAIs in sof_set_dai_config - ASoC: topology: set component dai_index to ipc dai config dai_index - ASoC: Intel: add codec name prefix to ACPI machine description - ASoC: Intel: sof_sdw: remove hard-coded codec_conf table - ASoC: Intel: sof_sdw_rt700: add codec prefix - ASoC: Intel: add support for new SoundWire hardware layout on TGL - ASoC: Intel: sof_sdw_rt711: remove hard-coded codec name - ASoC/soundwire: bus: use property to set interrupt masks - soundwire: bus: filter-out unwanted interrupt reports - soundwire: slave: add first_interrupt_done status - soundwire: bus: use quirk to filter out invalid parity errors - ASoC: codecs: realtek-soundwire: ignore initial PARITY errors * Fix system reboot when disconnecting WiFi (LP: #1899726) - iwlwifi: msix: limit max RX queues for 9000 family * Improve descriptions for XFAIL cases in kselftests/net/psock_snd (LP: #1900088) - selftests/net: improve descriptions for XFAIL cases in psock_snd.sh * Fix broken MSI interrupt after HDA controller was suspended (LP: #1899586) - ALSA: hda: Skip controller resume if not needed - ALSA: hda: Always use jackpoll helper for jack update after resume - SAUCE: ALSA: hda: fix jack detection with Realtek codecs when in D3 - ALSA: hda - let hs_mic be picked ahead of hp_mic * Enable brightness control on HP DreamColor panel (LP: #1898865) - drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * alsa/hda/realtek - The front Mic on a HP machine doesn't work (LP: #1899508) - SAUCE: ALSA: hda/realtek - The front Mic on a HP machine doesn't work -- Timo Aaltonen Fri, 16 Oct 2020 14:40:28 +0300 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12351 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12352 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-24490 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Description changed: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. - This test case exists since Bionic, and it can be cherry-picked. + This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => In Progress ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Tags added: ubuntu-kernel-selftests ** Description changed: == SRU Justification == - The test output in psock_snd.sh is confusing sometimes. Here is an output example: - raw csum_off with bad offset (fails) - ./psock_snd: write: Invalid argument + The test output in psock_snd.sh is confusing sometimes. + Here is an output example: + raw csum_off with bad offset (fails) + ./psock_snd: write: Invalid argument - The first line is the test case description, and the second is the test execution output. + The first line is the test case description, and the second is the + test execution output. + It feels like this test has failed, but it has passed instead. - The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. + The "fails" here means this test is expected to fail. But you will + have to check the source code to know this fact. == Fix == - * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh + * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in + psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. + == Test == + Patch tested by applying to the tree directly, the test description + will be changed as expected. + == Regression Potential == Low, minor changes for test case description only. ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: == SRU Justification == - The test output in psock_snd.sh is confusing sometimes. - Here is an output example: + The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument - The first line is the test case description, and the second is the - test execution output. - + The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. - The "fails" here means this test is expected to fail. But you will - have to check the source code to know this fact. + The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == - * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in - psock_snd.sh + * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. - == Test == - Patch tested by applying to the tree directly, the test description - will be changed as expected. + This test case exists only after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. ** Description changed: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. - This test case exists only after Bionic, and it can be cherry-picked. + This test case exists since Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Groovy: Incomplete Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in
