Public bug reported:
[Impact]
This upstream commit introduced that Intel ice driver exports "phys_port_name"
in sysfs interface:
37165e3f5664 ice: introduce VF port representor
And “phys_port_name” is used by systemd when renaming NIC,
so when upgrading kernel from 5.15 to 6.8, this causes NIC name changes from
ens2f0:
kernel: ice 0000:2a:00.0 ens2f0: renamed from eth0
to ens2f0np0:
kernel: [ 21.217165] ice 0000:2a:00.0 ens2f0np0: renamed from eth0
In some circumstances, bond won't work after upgrading kernel because of
its underlying NIC name changed
[Fix]
Later, upstream removed exporting "phys_port_name" in sysfs interface in this
commit:
41355365d252 ice: Remove ndo_get_phys_port_name
It's removed in 6.10:
git tag --contains 41355365d252
v6.10
Because phys_port_name is never used, mentioned in the commit message:
ndo_get_phys_port_name is never actually used, as in switchdev
devlink is always being created.
We should make it consistent to not having "npX" in the tail of NIC name
[ Test ]
Install 5.15 and 6.8 kernels on a machine with Intel ice NIC and see if
NIC name is the same.
[ Where the problems could occur ]
Since the "phys_port_name" is never actually used, it's find to remove
it.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: gerald.yang (gerald-yang-tw)
Status: In Progress
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: gerald.yang (gerald-yang-tw)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => gerald.yang (gerald-yang-tw)
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => gerald.yang (gerald-yang-tw)
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Description changed:
[Impact]
This upstream commit introduced that Intel ice driver exports
"phys_port_name" in sysfs interface:
37165e3f5664 ice: introduce VF port representor
And “phys_port_name” is used by systemd when renaming NIC,
so when upgrading kernel from 5.15 to 6.8, this causes NIC name changes from
ens2f0:
kernel: ice 0000:2a:00.0 ens2f0: renamed from eth0
to ens2f0np0:
kernel: [ 21.217165] ice 0000:2a:00.0 ens2f0np0: renamed from eth0
In some circumstances, bond won't work after upgrading kernel because of
its underlying NIC name changed
[Fix]
- Later, upstream removes exporting "phys_port_name" in sysfs interface in this
commit:
+ Later, upstream removed exporting "phys_port_name" in sysfs interface in this
commit:
41355365d252 ice: Remove ndo_get_phys_port_name
It's removed in 6.10:
git tag --contains 41355365d252
v6.10
Because phys_port_name is never used, mentioned in the commit message:
ndo_get_phys_port_name is never actually used, as in switchdev
devlink is always being created.
We should make it consistent to not having "npX" in the tail of NIC name
[ Test ]
Find a machine with Intel ice NIC, and boot into 5.15 and 6.8 kernels to
see if ice NIC name is the same.
[ Where the problems could occur ]
Since the "phys_port_name" is never actually used, it's find to remove
it.
** Description changed:
[Impact]
This upstream commit introduced that Intel ice driver exports
"phys_port_name" in sysfs interface:
37165e3f5664 ice: introduce VF port representor
And “phys_port_name” is used by systemd when renaming NIC,
so when upgrading kernel from 5.15 to 6.8, this causes NIC name changes from
ens2f0:
kernel: ice 0000:2a:00.0 ens2f0: renamed from eth0
to ens2f0np0:
kernel: [ 21.217165] ice 0000:2a:00.0 ens2f0np0: renamed from eth0
In some circumstances, bond won't work after upgrading kernel because of
its underlying NIC name changed
[Fix]
Later, upstream removed exporting "phys_port_name" in sysfs interface in this
commit:
41355365d252 ice: Remove ndo_get_phys_port_name
It's removed in 6.10:
git tag --contains 41355365d252
v6.10
Because phys_port_name is never used, mentioned in the commit message:
ndo_get_phys_port_name is never actually used, as in switchdev
devlink is always being created.
We should make it consistent to not having "npX" in the tail of NIC name
[ Test ]
- Find a machine with Intel ice NIC, and boot into 5.15 and 6.8 kernels to
- see if ice NIC name is the same.
+ Install 5.15 and 6.8 kernels on a machine with Intel ice NIC and see if
+ NIC name is the same.
[ Where the problems could occur ]
Since the "phys_port_name" is never actually used, it's find to remove
it.
--
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/2100264
Title:
ice: Remove ndo_get_phys_port_name
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
[Impact]
This upstream commit introduced that Intel ice driver exports
"phys_port_name" in sysfs interface:
37165e3f5664 ice: introduce VF port representor
And “phys_port_name” is used by systemd when renaming NIC,
so when upgrading kernel from 5.15 to 6.8, this causes NIC name changes from
ens2f0:
kernel: ice 0000:2a:00.0 ens2f0: renamed from eth0
to ens2f0np0:
kernel: [ 21.217165] ice 0000:2a:00.0 ens2f0np0: renamed from eth0
In some circumstances, bond won't work after upgrading kernel because
of its underlying NIC name changed
[Fix]
Later, upstream removed exporting "phys_port_name" in sysfs interface in this
commit:
41355365d252 ice: Remove ndo_get_phys_port_name
It's removed in 6.10:
git tag --contains 41355365d252
v6.10
Because phys_port_name is never used, mentioned in the commit message:
ndo_get_phys_port_name is never actually used, as in switchdev
devlink is always being created.
We should make it consistent to not having "npX" in the tail of NIC
name
[ Test ]
Install 5.15 and 6.8 kernels on a machine with Intel ice NIC and see
if NIC name is the same.
[ Where the problems could occur ]
Since the "phys_port_name" is never actually used, it's find to remove
it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100264/+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
