From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Vyacheslav Yurkov <uvv.mail@gmail.com>,
Openembedded-core@lists.openembedded.org
Cc: tmark@isc.org, Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
Subject: Re: [OE-core] [PATCH] dhcp: use included bind version
Date: Wed, 10 Jun 2020 16:05:46 +0100 [thread overview]
Message-ID: <6dd0de0be72028b355cd759e40fee22c9d24ca7b.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200610143520.2727827-1-uvv.mail@gmail.com>
On Wed, 2020-06-10 at 16:35 +0200, Vyacheslav Yurkov wrote:
> From: Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
>
> ISC DHCP should link against BIND9 libraries, which are tailored
> specifically for DHCP. BIND9 package in Yocto core layer has
> different
> configuraiton, in particular it has threads and epoll enabled.
>
> ISC DHCP isn't a multi-threaded application, running it with bind9
> libraries compiled in with threading enabled is not something ISC can
> vouch for.
>
> BIND9 libraries support a lot of options specifically geared towards
> optimizing DNS operations, many of which do not play nicely with
> ISC DHCP's "architecture". It isn't necessarily practical to build
> those libraries for both purposes.
>
> If threading is enabled, then DHCP sporadically fails/crashes with
> messages like:
>
> lib/isc/unix/socket.c:1054: epoll_ctl(DEL), 6: Bad file descriptor
> lib/isc/unix/socket.c:3332: INSIST(!sock->pending_send) failed.
You seem to disable parallel make yet no mention of that in the log?
Why doesn't dhcp build and link against a static libbind by default if
these issues are present the the dhcp authors don't want to work with
such libbinds?
Cheers,
Richard
next prev parent reply other threads:[~2020-06-10 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 14:35 [PATCH] dhcp: use included bind version Vyacheslav Yurkov
2020-06-10 15:02 ` ✗ patchtest: failure for " Patchwork
2020-06-10 15:05 ` Richard Purdie [this message]
2020-06-10 16:36 ` [OE-core] [PATCH] " Vyacheslav Yurkov
2020-06-13 0:41 ` Khem Raj
2020-06-13 8:31 ` Vyacheslav Yurkov
2020-06-17 10:35 ` Alexander Kanavin
2020-06-10 16:07 ` Adrian Bunk
2020-06-10 16:31 ` Vyacheslav Yurkov
2020-06-10 17:42 ` Adrian Bunk
2020-06-10 18:40 ` Vyacheslav Yurkov
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=6dd0de0be72028b355cd759e40fee22c9d24ca7b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=Vyacheslav.Yurkov@bruker.com \
--cc=tmark@isc.org \
--cc=uvv.mail@gmail.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