[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
This bug was fixed in the package linux - 4.15.0-34.37 --- linux (4.15.0-34.37) bionic; urgency=medium * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744) * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352) - MIPS: c-r4k: Fix data corruption related to cache coherence - MIPS: ptrace: Expose FIR register through FP regset - MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs - KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable" - affs_lookup(): close a race with affs_remove_link() - fs: don't scan the inode cache before SB_BORN is set - aio: fix io_destroy(2) vs. lookup_ioctx() race - ALSA: timer: Fix pause event notification - do d_instantiate/unlock_new_inode combinations safely - mmc: sdhci-iproc: remove hard coded mmc cap 1.8v - mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register - mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus - libata: Blacklist some Sandisk SSDs for NCQ - libata: blacklist Micron 500IT SSD with MU01 firmware - xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent - drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros - arm64: lse: Add early clobbers to some input/output asm operands - powerpc/64s: Clear PCR on boot - IB/hfi1: Use after free race condition in send context error path - IB/umem: Use the correct mm during ib_umem_release - idr: fix invalid ptr dereference on item delete - Revert "ipc/shm: Fix shmat mmap nil-page protection" - ipc/shm: fix shmat() nil address after round-down when remapping - mm/kasan: don't vfree() nonexistent vm_area - kasan: free allocated shadow memory on MEM_CANCEL_ONLINE - kasan: fix memory hotplug during boot - kernel/sys.c: fix potential Spectre v1 issue - KVM: s390: vsie: fix < 8k check for the itdba - KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed - kvm: x86: IA32_ARCH_CAPABILITIES is always supported - powerpc/64s: Improve RFI L1-D cache flush fallback - powerpc/pseries: Restore default security feature flags on setup - powerpc/64s: Fix section mismatch warnings from setup_rfi_flush() - MIPS: generic: Fix machine compatible matching - mac80211: mesh: fix wrong mesh TTL offset calculation - ARC: Fix malformed ARC_EMUL_UNALIGNED default - ptr_ring: prevent integer overflow when calculating size - arm64: dts: rockchip: fix rock64 gmac2io stability issues - arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire - libata: Fix compile warning with ATA_DEBUG enabled - selftests: sync: missing CFLAGS while compiling - selftest/vDSO: fix O= - selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m - selftests: memfd: add config fragment for fuse - ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt - ARM: OMAP3: Fix prm wake interrupt for resume - ARM: OMAP2+: Fix sar_base inititalization for HS omaps - ARM: OMAP1: clock: Fix debugfs_create_*() usage - tls: retrun the correct IV in getsockopt - xhci: workaround for AMD Promontory disabled ports wakeup - IB/uverbs: Fix method merging in uverbs_ioctl_merge - IB/uverbs: Fix possible oops with duplicate ioctl attributes - IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy - arm64: dts: rockchip: Fix DWMMC clocks - ARM: dts: rockchip: Fix DWMMC clocks - iwlwifi: mvm: fix security bug in PN checking - iwlwifi: mvm: fix IBSS for devices that support station type API - iwlwifi: mvm: always init rs with 20mhz bandwidth rates - NFC: llcp: Limit size of SDP URI - rxrpc: Work around usercopy check - MD: Free bioset when md_run fails - md: fix md_write_start() deadlock w/o metadata devices - s390/dasd: fix handling of internal requests - xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos - mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4 - mac80211: fix a possible leak of station stats - mac80211: fix calling sleeping function in atomic context - cfg80211: clear wep keys after disconnection - mac80211: Do not disconnect on invalid operating class - mac80211: Fix sending ADDBA response for an ongoing session - gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle - gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle - md raid10: fix NULL deference in handle_write_completed() - drm/exynos: g2d: use monotonic timestamps - drm/exynos: fix comparison to bitshift when dealing with a mask - drm/meson: fix vsync buffer update - arm64: perf: correct PMUVer probing - RDMA/bnxt_re: Unpin SQ and RQ memory if QP create fails - RDMA/bnxt_re: Fix system crash during load/unload - net/mlx5e: Return error if prio is specified when offloading eswitch vlan push - locking/xchg/al
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
Verification: ubuntu@d06-3:~$ cat /proc/version Linux version 4.15.0-34-generic (buildd@bos02-arm64-002) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 ubuntu@d06-3:~$ lsmod | grep hinic hinic 94208 0 ubuntu@d06-3:~$ grep eth /proc/net/dev ubuntu@d06-3:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] lsmod | grep hinic grep eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Description changed: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] - grep ^eth /proc/net/dev + lsmod | grep hinic + grep eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] lsmod | grep hinic grep eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. 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-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
This bug was fixed in the package linux - 4.17.0-7.8
---
linux (4.17.0-7.8) cosmic; urgency=medium
* linux: 4.17.0-7.8 -proposed tracker (LP: #1785242)
* Cosmic update to 4.17.12 stable release (LP: #1785211)
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- mm: disallow mappings that conflict for devm_memremap_pages()
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double free of event_trigger_data
- tracing: Fix possible double free in event_enable_trigger_func()
- kthread, tracing: Don't expose half-written comm when creating kthreads
- tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
- tracing: Quiet gcc warning about maybe unused link variable
- arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
- drm/i915/glk: Add Quirk for GLK NUC HDMI port issues.
- mlxsw: spectrum_switchdev: Fix port_vlan refcounting
- kcov: ensure irq code sees a valid area
- mm: check for SIGKILL inside dup_mmap() loop
- drm/amd/powerplay: Set higher SCLK&MCLK frequency than dpm7 in OD (v2)
- xen/netfront: raise max number of slots in xennet_get_responses()
- hv_netvsc: fix network namespace issues with VF support
- skip LAYOUTRETURN if layout is invalid
- ixgbe: Fix setting of TC configuration for macvlan case
- ALSA: emu10k1: add error handling for snd_ctl_add
- ALSA: fm801: add error handling for snd_ctl_add
- NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
- nfsd: fix error handling in nfs4_set_delegation()
- nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
- vfio: platform: Fix reset module leak in error path
- vfio/mdev: Check globally for duplicate devices
- vfio/type1: Fix task tracking for QEMU vCPU hotplug
- kernel/hung_task.c: show all hung tasks before panic
- mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the
same cacheline
- mm: /proc/pid/pagemap: hide swap entries from unprivileged users
- mm: vmalloc: avoid racy handling of debugobjects in vunmap
- mm/slub.c: add __printf verification to slab_err()
- rtc: ensure rtc_set_alarm fails when alarms are not supported
- rxrpc: Fix terminal retransmission connection ID to include the channel
- perf tools: Fix pmu events parsing rule
- netfilter: ipset: forbid family for hash:mac sets
- netfilter: ipset: List timing out entries with "timeout 1" instead of zero
- irqchip/ls-scfg-msi: Map MSIs in the iommu
- watchdog: da9063: Fix updating timeout value
- media: arch: sh: migor: Fix TW9910 PDN gpio
- printk: drop in_nmi check from printk_safe_flush_on_panic()
- bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
- ceph: fix alignment of rasize
- ceph: fix use-after-free in ceph_statfs()
- e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
- infiniband: fix a possible use-after-free bug
- powerpc/lib: Adjust .balign inside string functions for PPC32
- powerpc/64s: Add barrier_nospec
- powerpc/eeh: Fix use-after-release of EEH driver
- hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
- powerpc/64s: Fix compiler store ordering to SLB shadow area
- clk-si544: Properly round requested frequency to nearest match
- clk: ingenic: jz4770: Modify C1CLK clock to disable CPU clock stop on idle
- RDMA/mad: Convert BUG_ONs to error flows
- lightnvm: fix partial read error path
- lightnvm: proper error handling for pblk_bio_add_pages
- lightnvm: pblk: warn in case of corrupted write buffer
- netfilter: nf_tables: check msg_type before nft_trans_set(trans)
- pnfs: Don't release the sequence slot until we've processed layoutget on
open
- NFS: Fix up nfs_post_op_update_inode() to force ctime updates
- disable loading f2fs module on PAGE_SIZE > 4KB
- f2fs: fix error path of move_data_page
- f2fs: don't drop dentry pages after fs shutdown
- f2fs: fix to don't trigger writeback during recovery
- f2fs: fix to wait page writeback during revoking atomic write
- f2fs: Fix deadlock in shutdown ioctl
- f2fs: fix missing clear FI_NO_PREALLOC in some error case
- f2fs: fix to detect failure of dquot_initialize
- f2fs: fix race in between GC and atomic open
- block, bfq: remove wrong lock in bfq_requests_merged
- usbip: usbip_detach: Fix memory, udev context and udev leak
- usbip: dynamically allocate idev by nports found in sysfs
- perf/x86/intel/uncore: Correct fixed counter index check in generic code
- perf/x86/intel/uncore: Correct fixed counter index check for NHM
- sel
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Description changed: - On a HiSilicon D06 system we noticed that interfaces provided by a plug- - in "HINIC" network card are not getting assigned predictable names. - We're getting "ethX" names instead of the expected "enPblah" names. + [Impact] + Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. + + [*] + https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ + + [Test Case] + grep ^eth /proc/net/dev + + [Fix] + There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. + + [Regression Risk] + The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: On a HiSilicon D06 system we noticed that interfaces provided by a plug-in "HINIC" network card are not getting assigned predictable names. We're getting "ethX" names instead of the expected "enPblah" names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: On a HiSilicon D06 system we noticed that interfaces provided by a plug-in "HINIC" network card are not getting assigned predictable names. We're getting "ethX" names instead of the expected "enPblah" names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
Is this critical for 18.04.1 release? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: On a HiSilicon D06 system we noticed that interfaces provided by a plug-in "HINIC" network card are not getting assigned predictable names. We're getting "ethX" names instead of the expected "enPblah" names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
fyi, this appears to fix the problem for me. ** Patch added: "0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: On a HiSilicon D06 system we noticed that interfaces provided by a plug-in "HINIC" network card are not getting assigned predictable names. We're getting "ethX" names instead of the expected "enPblah" names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
