Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jeroen Hofstee <oe@myspectrum.nl>,
	Jeroen Hofstee <jeroen@myspectrum.nl>,
		openembedded-core@lists.openembedded.org
Cc: Jeroen Hofstee <jhofstee@victronenergy.com>
Subject: Re: [OE-core] [PATCH] udev-extraconf: fix ifupdown for non hotplug devices
Date: Wed, 09 Apr 2025 11:52:31 +0100	[thread overview]
Message-ID: <2bef26e9df54c8e1b12a8e71790e0072e5f09fa7.camel@linuxfoundation.org> (raw)
In-Reply-To: <7eb23b12-1fd1-48a5-83cd-eab2edb8777b@myspectrum.nl>

On Wed, 2025-04-09 at 12:40 +0200, Jeroen Hofstee wrote:
> Hello Richard,
> 
> On 4/9/25 11:27, Richard Purdie via lists.openembedded.org wrote:
> > > > We've purposefully kept the code called from udev and in our
> > > > initscripts relatively minimal/simple as the overhead of executing
> > > > multiple programs does build up over time. Taking the above, we have
> > > > loops, then pipelines, each of which runs more commands. Each command
> > > > has a fork/exec overhead.
> > > > 
> > > > Is there some way we can simplify this rather than all the shell
> > > > pipelines and loops?
> > > The simplest solution is to patch busybox to respect  --allow=hotplug I guess.
> > Yes, I as wondering about that. I see patches from a long time ago but
> > I guess they were never merged. It probably is easier for busybox to
> > handle this rather than shell code but I don't know what chance they'd
> > have of being merged upstream.
> > 
> > I would probably perfer to fix busybox to support this but I don't know
> > how well that is going to work out...
> 
> Unless they changed their mind, upstream busybox won't accept it, so it
> has to be a patch in OE. But feel free to try to upstream it.

It would be worth a try at least asking as that was a long time ago and
we do have a specific need here which doesn't involve feature creep (as
far as I know).

> For completeness, this is not some theoretical issue, always calling if up
> directly after a network device is discovered does cause issues and is
> against spec as well.

Right, I don't doubt the issue and agree we should fix it, it is just a
question of how.

> The sed stuff isn't that complicated, is it?

It is about the principle and precedent. If I take this, it becomes so
much harder to me to argue against the next similar change and hard to
keep things simple overall. I'm therefore really torn.

I'm spelling things out to see if anyone else has opinions too. Mike's
alternative way of handling things is potentially interesting but I
worry that may also be "against spec".

Cheers,

Richard



  reply	other threads:[~2025-04-09 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 17:49 [OE-core] [PATCH] udev-extraconf: fix ifupdown for non hotplug devices Jeroen Hofstee
2025-04-09  8:37 ` Richard Purdie
2025-04-09  9:08   ` Jeroen Hofstee
2025-04-09  9:27     ` Richard Purdie
2025-04-09 10:40       ` Jeroen Hofstee
2025-04-09 10:52         ` Richard Purdie [this message]
2025-04-10 10:14         ` Alexander Kanavin
2025-04-10 12:17           ` Yoann Congal
2025-04-10 18:32             ` Jeroen Hofstee
2025-04-10 19:05               ` Alexander Kanavin
2025-04-09  9:28   ` Mike Looijmans

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=2bef26e9df54c8e1b12a8e71790e0072e5f09fa7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jeroen@myspectrum.nl \
    --cc=jhofstee@victronenergy.com \
    --cc=oe@myspectrum.nl \
    --cc=openembedded-core@lists.openembedded.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