linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Michael Walle <michael@walle.cc>,
	kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] driver core: Fix device link device name collision
Date: Thu, 7 Jan 2021 10:00:52 +0100	[thread overview]
Message-ID: <X/bNxMPWKq2nbqS4@kroah.com> (raw)
In-Reply-To: <20210106232641.459081-1-saravanak@google.com>

On Wed, Jan 06, 2021 at 03:26:41PM -0800, Saravana Kannan wrote:
> The device link device's name was of the form:
> <supplier-dev-name>--<consumer-dev-name>
> 
> This can cause name collision as reported here [1] as device names are
> not globally unique. Since device names have to be unique within the
> bus/class, add the bus/class name as a prefix to the device names used to
> construct the device link device name.
> 
> So the devuce link device's name will be of the form:
> <supplier-bus-name>:<supplier-dev-name>--<consumer-bus-name><consumer-dev-name>

Minor nit, you forgot a ':' in the consumer side of the link here.  The
code is correct.

> 
> [1] - https://lore.kernel.org/lkml/20201229033440.32142-1-michael@walle.cc/
> Reported-by: Michael Walle <michael@walle.cc>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
> ---
> 
> Michael,
> 
> Can you please test this? This should fix your issue.
> 
> Having said that, do you have some local DT changes when you are testing
> this? Because it's not obvious from the DT in upstream what dependency
> is even being derived from the firmware. I don't see any dependency in
> upstream DT files between mdio_bus/0000:00:00.1 and
> pci0000:00/0000:00:00.1

That looks really odd, why is the mdio bus using the same names as the
pci bus?

But anyway, your dev_bus_name() change here looks good, I'll take that
as a separate patch no matter what happens here :)

thanks,

greg k-h

  reply	other threads:[~2021-01-07  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 23:26 [PATCH v1] driver core: Fix device link device name collision Saravana Kannan
2021-01-07  9:00 ` Greg Kroah-Hartman [this message]
2021-01-07  9:19   ` Michael Walle
2021-01-07 23:17   ` Saravana Kannan
2021-01-07 23:19     ` Saravana Kannan
2021-01-07  9:56 ` Michael Walle
2021-01-07 23:39   ` Saravana Kannan
2021-01-08  0:22     ` Michael Walle
2021-01-08  1:19       ` Saravana Kannan

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=X/bNxMPWKq2nbqS4@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).