From: <Mario_Limonciello@Dell.com>
To: <pali.rohar@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <davem@davemloft.net>, <andrew@lunn.ch>, <hayeswang@realtek.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <anthony.wong@canonical.com>
Subject: RE: [PATCH v6] r8152: Add support for setting pass through MAC address on RTL8153-AD
Date: Tue, 14 Jun 2016 16:55:21 +0000 [thread overview]
Message-ID: <ba393fe424fd4a8fb82703dd0f42eea7@ausx13mpc124.AMER.DELL.COM> (raw)
In-Reply-To: <201606141847.36109@pali>
> -----Original Message-----
> From: Pali Rohár [mailto:pali.rohar@gmail.com]
> Sent: Tuesday, June 14, 2016 11:48 AM
> To: Greg KH <gregkh@linuxfoundation.org>
> Cc: David Miller <davem@davemloft.net>; andrew@lunn.ch; Limonciello,
> Mario <Mario_Limonciello@Dell.com>; hayeswang@realtek.com; linux-
> kernel@vger.kernel.org; netdev@vger.kernel.org; linux-
> usb@vger.kernel.org; anthony.wong@canonical.com
> Subject: Re: [PATCH v6] r8152: Add support for setting pass through MAC
> address on RTL8153-AD
>
> On Tuesday 14 June 2016 18:40:17 Greg KH wrote:
> > On Tue, Jun 14, 2016 at 06:28:10PM +0200, Pali Rohár wrote:
> > > On Saturday 11 June 2016 19:42:26 David Miller wrote:
> > > > From: Andrew Lunn <andrew@lunn.ch>
> > > > Date: Sat, 11 Jun 2016 17:39:21 +0200
> > > >
> > > > > What is still open is do we want to accept it at all? Do we
> > > > > accept the concept of putting the same MAC address on multiple
> > > > > interfaces at hotplug time? Do we trust BIOS vendors to not
> > > > > keep changing DSDT property name, since it is not
> > > > > standardised?
> > > > >
> > > > > Do we want this at all should be decided by somebody more
> > > > > senior then those passing comments on the code.
> > > >
> > > > Indeed, I think the behavior of using the same MAC address on
> > > > multiple interfaces if we plug several of these in at once is not
> > > > good.
> > > >
> > > > We shouldn't behave this way just because the Microsoft driver
> > > > does.
> > >
> > > I agree, but in some cases it is night mare for local admins when
> > > booting different OS cause changing MAC address on local network.
> > >
> > > Another similar situation: Imagine that you have two USB network
> > > cards and both have "burned" into their registers same MAC
> > > address. If you connect both those USB network cards, linux kernel
> > > bind appropriate driver which read MAC address for both those
> > > cards. But those addresses are same. What will linux kernel do in
> > > this case?
> >
> > If you can find such a broken USB device, try it and see :)
>
> What do you mean by broken USB device?
>
> You have never seen two ethernet cards with same MAC addresses? Right I
> have not seen two USB, but there is non zero chance that could happen.
> Specially now when more and more people starts using USB network cards.
>
> > (hint, might be hard to find, I've never seen such a device before.)
> >
> > I don't see how that pertains to this issue, sorry, how does broken
> > USB hardware compare to a working Dell device?
>
> It is same, how to handle two network cards which tell us, that they
> have same MAC addresses.
>
The kernel handles this just fine. In doing this patch I checked to see
what it does in that scenario. Two devices are made. systemd doesn't
rename the second device via the MAC name (eg enxAABBCCDDEEFF).
next prev parent reply other threads:[~2016-06-14 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 18:22 Mario Limonciello
2016-06-11 5:51 ` David Miller
2016-06-11 15:39 ` Andrew Lunn
2016-06-11 17:42 ` David Miller
2016-06-14 15:08 ` Mario_Limonciello
2016-06-14 16:28 ` Pali Rohár
2016-06-14 16:40 ` Greg KH
2016-06-14 16:47 ` Pali Rohár
2016-06-14 16:55 ` Mario_Limonciello [this message]
2016-06-14 17:23 ` Andrew Lunn
2016-06-14 17:58 ` Mario_Limonciello
2016-06-14 18:35 ` David Miller
2016-06-14 22:27 ` Mario_Limonciello
2016-06-22 22:11 ` Mario_Limonciello
2016-07-11 21:54 ` Mario_Limonciello
2016-07-11 22:05 ` David Miller
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=ba393fe424fd4a8fb82703dd0f42eea7@ausx13mpc124.AMER.DELL.COM \
--to=mario_limonciello@dell.com \
--cc=andrew@lunn.ch \
--cc=anthony.wong@canonical.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali.rohar@gmail.com \
/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
all inboxes | Powered by JetHome®