From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] openssl: fix race condition when symlink shared libs
Date: Wed, 25 Nov 2015 14:31:38 -0500 [thread overview]
Message-ID: <20151125193138.GO23754@vapier.lan> (raw)
In-Reply-To: <565070A7.10001@mind.be>
On 21 Nov 2015 14:24, Arnout Vandecappelle wrote:
> On 20-11-15 17:23, Ryan Barnett wrote:
> > The build-shared target depends on do_crypto and link-shared, which
> > will be executed in parallel. do_crypto calls
> > link_a.linux_shared -> link_a.gnu which does SYMLINK_SO; in parallel,
> > link-shared calls symlink.linux_shared which also does SYMLINK_SO.
> > Before the symlink is created, it is rm'ed, but there is a tiny chance
> > that the second one is created after the rm has been called.
> >
> > Fix this by using 'ln -sf' instead of 'ln -s' so the build doesn't
> > error out.
> >
> > Patch submitted upstream at:
> > https://bugs.gentoo.org/show_bug.cgi?id=566260
>
> Ahem, gentoo is not exactly upstream :-) From [1]:
>
> To report a bug or make an enhancement request, send email to rt at openssl.org.
which these have been already. they don't respond. in fact, you can see
a link to the relevant upstream report in every Gentoo parallel patch.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151125/729563ba/attachment.asc>
prev parent reply other threads:[~2015-11-25 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 16:23 [Buildroot] [PATCH v2] openssl: fix race condition when symlink shared libs Ryan Barnett
2015-11-21 0:55 ` Ryan Barnett
2015-11-21 23:46 ` Arnout Vandecappelle
2015-11-21 13:24 ` Arnout Vandecappelle
2015-11-21 16:32 ` Ryan Barnett
2015-11-25 19:31 ` Mike Frysinger [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=20151125193138.GO23754@vapier.lan \
--to=vapier@gentoo.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.