From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] build: add and use a symbol version map
Date: Wed, 19 Nov 2014 14:42:24 +0100 [thread overview]
Message-ID: <20141119134224.GA12289@salvia> (raw)
In-Reply-To: <1415797607-28793-1-git-send-email-jengelh@inai.de>
On Wed, Nov 12, 2014 at 02:06:47PM +0100, Jan Engelhardt wrote:
> It was possible to combine e.g. conntrackd-1.2.1 with
> libnetfilter_conntrack-0.0.101, causing libc to issue an exit from
> within conntrackd iff such a conntrackd was promoted to a master and
> tried to call nfexp_send, due to lazy symbol resolution in libc.
I wonder how you have reached such a situation. I can only think of
very broken packaging.
> Symbol versions enforce the checks at program startup, so add one.
>
> $ ldd -r /usr/sbin/conntrackd
> undefined symbol: nfexp_cmp (/usr/sbin/conntrackd)
> undefined symbol: nfexp_send (/usr/sbin/conntrackd)
> libnetfilter_conntrack.so.3 => /usr/lib/libnetfilter_conntrack.so.3 (0x77fe7000)
> libnfnetlink.so.0 => /usr/lib/libnfnetlink.so.0 (0x77fdf000)
> libc.so.6 => /lib/libc.so.6 (0x77e7b000)
> libdl.so.2 => /lib/libdl.so.2 (0x77e76000)
> /lib/ld.so.1 (0x55555000)
> $ dpkg-query -W conntrackd libnetfilter-conntrack3
> conntrackd 1:1.2.1-1
> libnetfilter-conntrack3 0.0.101-1
Would you also convert libnetfilter_conntrack to use the same
EXPORT_SYMBOL() macro that we use in more recent libnetfilter_*
libraries for consistency?
next prev parent reply other threads:[~2014-11-19 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 13:06 [PATCH] build: add and use a symbol version map Jan Engelhardt
2014-11-19 13:42 ` Pablo Neira Ayuso [this message]
2014-11-19 15:56 ` Jan Engelhardt
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=20141119134224.GA12289@salvia \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).