From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Streetman <ddstreet@canonical.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Rob Herring <robh@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/vio: use simple dummy struct device as bus parent
Date: Fri, 27 Sep 2019 20:18:56 +0200 [thread overview]
Message-ID: <20190927181856.GD1804168@kroah.com> (raw)
In-Reply-To: <20190927130402.687-1-ddstreet@canonical.com>
On Fri, Sep 27, 2019 at 09:04:02AM -0400, Dan Streetman wrote:
> The dummy vio_bus_device creates the /sys/devices/vio directory, which
> contains real vio devices under it; since it represents itself as having
> a bus = &vio_bus_type, its /sys/devices/vio/uevent does call the bus's
> .uevent function, vio_hotplug(), and as that function won't find a real
> device for the dummy vio_dev, it will return -ENODEV.
>
> One of the main users of the uevent node is udevadm, e.g. when it is called
> with 'udevadm trigger --devices'. Up until recently, it would ignore any
> errors returned when writing to devices' uevent file, but it was recently
> changed to start returning error if it gets an error writing to any uevent
> file:
> https://github.com/systemd/systemd/commit/97afc0351a96e0daa83964df33937967c75c644f
>
> since the /sys/devices/vio/uevent file has always returned ENODEV from
> any write to it, this now causes the udevadm trigger command to return
> an error. This may be fixed in udevadm to ignore ENODEV errors, but the
> vio driver should still be fixed.
>
> This patch changes the arch/powerpc/platform/pseries/vio.c 'dummy'
> parent device into a real dummy device with no .bus, so its uevent
> file will stop returning ENODEV and simply do nothing and return 0.
>
> Signed-off-by: Dan Streetman <ddstreet@canonical.com>
> ---
> arch/powerpc/platforms/pseries/vio.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/vio.c b/arch/powerpc/platforms/pseries/vio.c
> index 79e2287991db..63bc16631680 100644
> --- a/arch/powerpc/platforms/pseries/vio.c
> +++ b/arch/powerpc/platforms/pseries/vio.c
> @@ -32,11 +32,8 @@
> #include <asm/page.h>
> #include <asm/hvcall.h>
>
> -static struct vio_dev vio_bus_device = { /* fake "parent" device */
> - .name = "vio",
> - .type = "",
> - .dev.init_name = "vio",
> - .dev.bus = &vio_bus_type,
> +static struct device vio_bus = {
> + .init_name = "vio",
Eeek, no! Why are you creating a static device that will then be
reference counted? Not nice :(
What's wrong with a simple call to device_create() for your "fake"
device you want to make here? That's what it is there for :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-27 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 13:04 [PATCH] powerpc/vio: use simple dummy struct device as bus parent Dan Streetman
2019-09-27 18:18 ` Greg Kroah-Hartman [this message]
2019-09-27 19:48 ` Dan Streetman
2019-09-28 7:41 ` Greg Kroah-Hartman
2019-09-28 13:28 ` Dan Streetman
2019-10-03 19:10 ` Dan Streetman
2019-10-03 19:21 ` Greg Kroah-Hartman
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=20190927181856.GD1804168@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=ddstreet@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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).