From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Leo Yan <leo.yan@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Regression] Missing device nodes for ETR, ETF and STM after CONFIG_UEVENT_HELPER=n
Date: Fri, 26 Jul 2019 13:43:25 +0200 [thread overview]
Message-ID: <20190726114325.GA18727@kroah.com> (raw)
In-Reply-To: <20190726133316.688a43d8@windsurf>
On Fri, Jul 26, 2019 at 01:33:16PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 26 Jul 2019 12:19:25 +0200
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > > This somehow is not mounting etr, etf, stm devices when uevent-helper is
> > > disabled. Anyways as Suzuki mentioned, using devtmpfs does fix the issue.
> >
> > Last I looked (many years ago) mdev requires uevent-helper in order for
> > it to work. I recommend that if you rely on mdev to keep that option
> > enabled, or to just use devtmpfs and udev :)
>
> Since Busybox 1.31.0, mdev has gained a daemon mode. In this mode, mdev
> runs in the background, and receives uevent through a netlink socket.
> So there's been some changes in how Busybox mdev works in recent times.
Ideally mdev should switch to what udev did many many years ago and not
do any device node creations and just leave all of that up to devtmpfs.
Then it can just stick to any symlinks and any specific owner:group
permissions that might be wanted separate from the default ones the
kernel provides.
Makes things much simpler and should save a lot of userspace code,
making mdev even smaller.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-26 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:19 [Regression] Missing device nodes for ETR, ETF and STM after CONFIG_UEVENT_HELPER=n Sai Prakash Ranjan
2019-07-26 6:26 ` Sai Prakash Ranjan
2019-07-26 7:04 ` Greg Kroah-Hartman
2019-07-26 8:20 ` Sai Prakash Ranjan
2019-07-26 8:41 ` Greg Kroah-Hartman
2019-07-26 9:28 ` Suzuki K Poulose
2019-07-26 9:58 ` Sai Prakash Ranjan
2019-07-26 10:02 ` Sai Prakash Ranjan
2019-07-26 9:44 ` Sai Prakash Ranjan
2019-07-26 10:14 ` Sai Prakash Ranjan
2019-07-26 10:19 ` Greg Kroah-Hartman
2019-07-26 10:24 ` Sai Prakash Ranjan
2019-07-26 11:33 ` Thomas Petazzoni
2019-07-26 11:43 ` Greg Kroah-Hartman [this message]
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=20190726114325.GA18727@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=geert+renesas@glider.be \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--cc=thomas.petazzoni@bootlin.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).