From: Oliver Neukum <oneukum@suse.com>
To: Andrew Lunn <andrew@lunn.ch>, Oliver Neukum <oneukum@suse.com>
Cc: hayeswang@realtek.com, netdev@vger.kernel.org
Subject: Re: [RFC] r8152: pass through needs to be singular
Date: Tue, 2 Aug 2022 12:52:05 +0200 [thread overview]
Message-ID: <34f7cb15-91e8-e92c-7dcd-f5b28724df92@suse.com> (raw)
In-Reply-To: <YuMJhAuZVVZtl9VZ@lunn.ch>
On 29.07.22 00:11, Andrew Lunn wrote:
> On Thu, Jul 28, 2022 at 09:18:51PM +0200, Oliver Neukum wrote:
>> If multiple devices are connected only one of them
>> is allowed to get the pass through MAC
>
> Is that true? Ethernet switches often use the same MAC address on
> multiple ports. It is not inherently broken to have the same MAC
> address on multiple interfaces.
Well, yes, but for a host to assigning the same MAC by default
is a bug. The whole point of MACs is kind of that they be unique.
For the same reason I fixed usbnet to not hand out the same
random address. In theory I have broken setups which relied on
people reconnecting a device getting the same MAC.
> We know this implementation of pass through it very broken, but
> unfortunately, it is there, and we have to follow the normal
> regression rules, even if we really would like to throw it all out.
True. Nevertheless, do we really want to say that we dislike a design
so much that we are not fixing bugs?
> What exactly is your problem which you are trying to fix?
Adressing the comment Hayes made when reset_resume() was fixed
from a deadlock, that it still assigns wrong MACs. I feel that
before I fix keeping the correct address I better make sure the
MAC is sane in the first place.
Regards
Oliver
next prev parent reply other threads:[~2022-08-02 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 19:18 [RFC] r8152: pass through needs to be singular Oliver Neukum
2022-07-28 22:11 ` Andrew Lunn
2022-08-02 10:52 ` Oliver Neukum [this message]
2022-08-02 13:31 ` Andrew Lunn
2022-08-04 9:24 ` Oliver Neukum
2022-08-04 13:24 ` Andrew Lunn
2022-08-04 13:29 ` Oliver Neukum
2022-08-04 14:31 ` Andrew Lunn
2022-08-03 3:48 ` Hayes Wang
2022-08-04 8:57 ` Oliver Neukum
2022-08-08 7:04 ` Hayes Wang
2022-08-23 7:53 ` Oliver Neukum
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=34f7cb15-91e8-e92c-7dcd-f5b28724df92@suse.com \
--to=oneukum@suse.com \
--cc=andrew@lunn.ch \
--cc=hayeswang@realtek.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.