public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jianlin Lv <iecedge@gmail.com>
Cc: kernel-team@lists.ubuntu.com, jianlv@ebay.com,
	Dominique Martinet <dominique.martinet@atmark-techno.com>,
	stable@vger.kernel.org, Ahmed Naseef <naseefkm@gmail.com>,
	Oliver Neukum <oneukum@suse.com>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [SRU] [Noble] [PATCH 1/1] net: usb: usbnet: restore usb%d name exception for local mac addresses
Date: Tue, 27 May 2025 17:08:11 +0200	[thread overview]
Message-ID: <2025052735-suffix-culinary-9241@gregkh> (raw)
In-Reply-To: <83eababe153e10f30ba5097717299b5260d0b574.1748010457.git.iecedge@gmail.com>

On Fri, May 23, 2025 at 10:30:58PM +0800, Jianlin Lv wrote:
> From: Dominique Martinet <dominique.martinet@atmark-techno.com>
> 
> BugLink: https://bugs.launchpad.net/bugs/2111592
> 
> commit 8a7d12d674ac ("net: usb: usbnet: fix name regression") assumed
> that local addresses always came from the kernel, but some devices hand
> out local mac addresses so we ended up with point-to-point devices with
> a mac set by the driver, renaming to eth%d when they used to be named
> usb%d.
> 
> Userspace should not rely on device name, but for the sake of stability
> restore the local mac address check portion of the naming exception:
> point to point devices which either have no mac set by the driver or
> have a local mac handed out by the driver will keep the usb%d name.
> 
> (some USB LTE modems are known to hand out a stable mac from the locally
> administered range; that mac appears to be random (different for
> mulitple devices) and can be reset with device-specific commands, so
> while such devices would benefit from getting a OUI reserved, we have
> to deal with these and might as well preserve the existing behavior
> to avoid breaking fragile openwrt configurations and such on upgrade.)
> 
> Link: https://lkml.kernel.org/r/20241203130457.904325-1-asmadeus@codewreck.org
> Fixes: 8a7d12d674ac ("net: usb: usbnet: fix name regression")
> Cc: stable@vger.kernel.org
> Tested-by: Ahmed Naseef <naseefkm@gmail.com>
> Signed-off-by: Dominique Martinet <dominique.martinet@atmark-techno.com>
> Acked-by: Oliver Neukum <oneukum@suse.com>
> Link: https://patch.msgid.link/20250326-usbnet_rename-v2-1-57eb21fcff26@atmark-techno.com
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> 
> (cherry picked from commit 2ea396448f26d0d7d66224cb56500a6789c7ed07)
> Signed-off-by: Jianlin Lv <iecedge@gmail.com>
> ---
>  drivers/net/usb/usbnet.c | 21 +++++++++++++++------
>  1 file changed, 15 insertions(+), 6 deletions(-)

This is already in all stable kernel branches, why send it again?

confused,

greg k-h

  reply	other threads:[~2025-05-27 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1748010457.git.iecedge@gmail.com>
2025-05-23 14:30 ` [SRU] [Noble] [PATCH 1/1] net: usb: usbnet: restore usb%d name exception for local mac addresses Jianlin Lv
2025-05-27 15:08   ` Greg KH [this message]
     [not found] <cover.1747992812.git.iecedge@gmail.com>
2025-05-23  9:37 ` Jianlin Lv
2025-05-23 14:13   ` Jianlin Lv
2025-05-27 14:55   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025052735-suffix-culinary-9241@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dominique.martinet@atmark-techno.com \
    --cc=iecedge@gmail.com \
    --cc=jianlv@ebay.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=kuba@kernel.org \
    --cc=naseefkm@gmail.com \
    --cc=oneukum@suse.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox