From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
lennart@poettering.net,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Multiple MODALIAS= in uevent file confuses userspace
Date: Mon, 18 Jan 2021 15:58:18 +0100 [thread overview]
Message-ID: <YAWiCkJwiOS8i50c@kroah.com> (raw)
In-Reply-To: <20210118144853.GP4077@smile.fi.intel.com>
On Mon, Jan 18, 2021 at 04:48:53PM +0200, Andy Shevchenko wrote:
> On Mon, Jan 18, 2021 at 03:26:28PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Jan 18, 2021 at 04:12:38PM +0200, Mika Westerberg wrote:
> > > On Mon, Jan 18, 2021 at 02:50:33PM +0100, Rafael J. Wysocki wrote:
> > > > On Mon, Jan 18, 2021 at 8:27 AM Kai-Heng Feng
> > > > <kai.heng.feng@canonical.com> wrote:
> > > > > On Sat, Jan 9, 2021 at 12:25 AM Kai-Heng Feng
> > > > > <kai.heng.feng@canonical.com> wrote:
> > > > > >
> > > > > > Commit 8765c5ba19490 ("ACPI / scan: Rework modalias creation when
> > > > > > "compatible" is present") creates two modaliases for certain ACPI
> > > > > > devices. However userspace (systemd-udevd in this case) assumes uevent
> > > > > > file doesn't have duplicated keys, so two "MODALIAS=" breaks the
> > > > > > assumption.
> > > > > >
> > > > > > Based on the assumption, systemd-udevd internally uses hashmap to
> > > > > > store each line of uevent file, so the second modalias always replaces
> > > > > > the first modalias.
> > > > > >
> > > > > > My attempt [1] is to add a new key, "MODALIAS1" for the second
> > > > > > modalias. This brings up the question of whether each key in uevent
> > > > > > file is unique. If it's no unique, this may break may userspace.
> > > > >
> > > > > Does anyone know if there's any user of the second modalias?
> > > > > If there's no user of the second one, can we change it to OF_MODALIAS
> > > > > or COMPAT_MODALIAS?
> > >
> > > The only users I'm aware are udev and the busybox equivalent (udev,
> > > mdev) but I'm not sure if they use the second second modalias at all so
> > > OF_MODALIAS for the DT compatible string sounds like a good way to solve
> > > this.
> >
> > As udev seems to "break" with this (which is where we got the original
> > report from), I don't think you need to worry about that user :)
>
> > Does anyone use mdev anymore, and in any ACPI-supported systems?
>
> Yes, regularly.
Ok, and how badly does it break when MODALIAS is multiple lines like
this? Or can it handle it?
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-18 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 16:25 Multiple MODALIAS= in uevent file confuses userspace Kai-Heng Feng
2021-01-18 7:26 ` Kai-Heng Feng
2021-01-18 13:50 ` Rafael J. Wysocki
2021-01-18 14:12 ` Mika Westerberg
2021-01-18 14:26 ` Greg Kroah-Hartman
2021-01-18 14:48 ` Andy Shevchenko
2021-01-18 14:58 ` Greg Kroah-Hartman [this message]
2021-01-18 15:27 ` Andy Shevchenko
2021-01-18 16:40 ` Greg Kroah-Hartman
2021-01-18 16:46 ` Andy Shevchenko
2021-01-18 14:52 ` Mika Westerberg
2021-01-18 14:51 ` Andy Shevchenko
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=YAWiCkJwiOS8i50c@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=lennart@poettering.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@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