From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image-prelink.bbclass: use the pseudo env var PSEUDO_ALLOW_FSYNC for prelink
Date: Fri, 22 Nov 2013 13:47:29 +0000 [thread overview]
Message-ID: <1385128049.16887.165.camel@ted> (raw)
In-Reply-To: <CAP9ODKry-KUYhXeKqn7iefb=rchCN9Xiu-GyFwj6A_eXtxD42g@mail.gmail.com>
On Fri, 2013-11-22 at 11:42 -0200, Otavio Salvador wrote:
> On Thu, Nov 21, 2013 at 5:26 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
> > From: Jackie Huang <jackie.huang@windriver.com>
> >
> > (Note: this patch is sent for YP compliance, I don't believe it is
> > applicable to general oe-core.)
> >
> > This would actually emit fsync calls, which may fix the do_rootfs failure
> > on older systems like CentOS 5.x or SuSE 11.
> >
> > Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> > Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> > Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
> > Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>
> There're a Yocto bug about this issue, no?
There is and its not something we're going to fix in master since the
changes are invasive and likely pointless since its a race problem and
just moves the race. You'd probably have to run fsync after ever single
command just to be safe.
The correct fix is to use an OS with a working filesystem as far as I'm
concerned.
Cheers,
Richard
prev parent reply other threads:[~2013-11-22 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 19:26 [PATCH] image-prelink.bbclass: use the pseudo env var PSEUDO_ALLOW_FSYNC for prelink Mark Hatle
2013-11-21 19:26 ` [PATCH] syslinux: check for __i386__ and __x86_64__ instead of __SIZEOF_POINTER__ Mark Hatle
2013-11-22 13:51 ` Otavio Salvador
2013-11-22 13:42 ` [PATCH] image-prelink.bbclass: use the pseudo env var PSEUDO_ALLOW_FSYNC for prelink Otavio Salvador
2013-11-22 13:47 ` Richard Purdie [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=1385128049.16887.165.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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