All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "조홍식/책임연구원/SW Security개발실 SW Security TP" <hongsik.jo@lge.com>
Cc: "netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	"손영섭/책임연구원/SW Security개발실 SW Security TP" <loth.son@lge.com>,
	"남정주/책임연구원/SW Security개발실 SW Security TP" <jungjoo.nahm@lge.com>,
	"정재윤/Task Leader/SW Platform(연)선행Platform개발실 시스템SW Task"
	<jaeyoon.jung@lge.com>
Subject: Re: Symbol Collision between ulogd and jansson
Date: Mon, 13 Jan 2025 23:23:01 +0100	[thread overview]
Message-ID: <Z4WSRVQPmmYfpqvV@calendula> (raw)
In-Reply-To: <SE1P216MB155825DDA1CD5809E1569DDE8F1F2@SE1P216MB1558.KORP216.PROD.OUTLOOK.COM>

Hi,

On Mon, Jan 13, 2025 at 06:41:19AM +0000, 조홍식/책임연구원/SW Security개발실 SW Security TP wrote:
> The issue I would like to bring to your attention is as follows: We
> are using the JSON feature in the PACKAGECONFIG of ulogd, and we
> have discovered that both ulogd and jansson have methods with the
> same name, which can lead to a symbol reference error resulting in a
> segmentation fault.  The method in question is hashtable_del().
> Based on our backtrace analysis, it appears that when ulogd's
> hashtable_del() is executed instead of jansson's hashtable_del(), it
> leads to a segmentation fault (SEGV).
> To avoid this symbol collision, I modified ulogd's hashtable_del()
> to hashtable_delete(), and I have confirmed that this resolves the
> issue.

$ nm -D libjansson.so.4 | grep hashtable_del
$

Are you building a static binary? Otherwise, I don't see how the clash
is going on.

I am fine with this patch, would you submit it using git format-patch
and including Signed-off-by:?

Thanks.

  reply	other threads:[~2025-01-13 22:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  6:41 Symbol Collision between ulogd and jansson 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-13 22:23 ` Pablo Neira Ayuso [this message]
2025-01-14  5:00   ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-14  5:02     ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-14 10:41 ` Florian Westphal
2025-01-14 12:50   ` 정재윤/Task Leader/SW Platform(연)선행Platform개발실 시스템SW Task
2025-01-14 13:32     ` Florian Westphal
2025-01-15  8:08       ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-15 12:29         ` Florian Westphal

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=Z4WSRVQPmmYfpqvV@calendula \
    --to=pablo@netfilter.org \
    --cc=hongsik.jo@lge.com \
    --cc=jaeyoon.jung@lge.com \
    --cc=jungjoo.nahm@lge.com \
    --cc=loth.son@lge.com \
    --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 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.