From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] e2fsprogs: nommu: Add patch to use vfork in nommu arch.
Date: Sat, 16 Nov 2013 10:42:23 +0100 [thread overview]
Message-ID: <20131116104223.1fc1af9f@skate> (raw)
In-Reply-To: <5286C388.2000004@mind.be>
Sonic,
On Sat, 16 Nov 2013 01:59:52 +0100, Arnout Vandecappelle wrote:
> Again, it doesn't look like these fork replacements will work...
I'd like to maybe give more details about this. What we are concerned
about is that the noMMU patches you are doing seem to simply be patches
that replace every invocation of fork() by vfork(), just for the sake
of making things build. But they should not only build, but also work :)
However, vfork() clearly doesn't have the same implications and
constraints as fork(), so each replacement of fork() by vfork() need a
careful study and analysis, with a proper justification as to why it is
actually possible. Ideally, such patches should go upstream, and
therefore really be working patches.
So I think what would be good is probably to require something like a
comment on top of each fork -> vfork replacement that justifies why it
is possible, like:
/*
* This is what happens, and which allows us to simply replace
* fork() by vfork(). Some more details here...
*/
#ifdef HAVE_FORK
p = fork();
#else
p = vfork();
#endif
Or, even better: instead of sending patches to Buildroot, simply send
them upstream. So upstream can study them, give feedback on fork() vs.
vfork() usage. Once a patch is upstream, it can get accepted
immediately into Buildroot, since we know upstream has accepted it, and
it will be part of the next upstream release.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-16 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 8:31 [Buildroot] [PATCH] e2fsprogs: Disable elf shared library when BR2_PREFER_STATIC_LIB is selected sonic.adi at gmail.com
2013-11-15 8:31 ` [Buildroot] [PATCH 1/3] e2fsprogs: nommu: Add patch to use vfork in nommu arch sonic.adi at gmail.com
2013-11-15 8:40 ` Thomas De Schampheleire
2013-11-16 0:59 ` Arnout Vandecappelle
2013-11-16 9:42 ` Thomas Petazzoni [this message]
2013-11-15 8:31 ` [Buildroot] [PATCH 2/3] e2fsprogs: flat: Add patch to append uuid link flag after the blkid link flags when checking the blkid library in the FLAT binary mode sonic.adi at gmail.com
2013-11-15 8:56 ` Thomas De Schampheleire
2013-11-15 8:31 ` [Buildroot] [PATCH 3/3] e2fsprogs: Disable elf shared library when BR2_PREFER_STATIC_LIB is selected sonic.adi at gmail.com
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=20131116104223.1fc1af9f@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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