All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: Sam Saffron <sam.saffron@gmail.com>,
	Simon Marchi <simon.marchi@efficios.com>
Subject: [lttng-dev] urcu 7ca7fe9c03 + _LGPL_SOURCE regression?
Date: Tue, 9 Aug 2022 18:19:27 +0000	[thread overview]
Message-ID: <20220809181927.GA3718@dcvr> (raw)

Hello, I've noticed liburcu v0.11.4+ and later fails with the
"mwrap" LD_PRELOAD malloc wrapper which initializes an rculfhash
in a constructor.

The problem happens when using _LGPL_SOURCE + rcu_dereference on
a cds_lfht pointer:

  In file included from /tmp/b/include/urcu/pointer.h:39,
                   from /tmp/b/include/urcu/urcu-bp.h:58,
                   from /tmp/b/include/urcu-bp.h:2,
                   from ../7ca7fe9c_regression.c:10:
  ../7ca7fe9c_regression.c: In function ‘main’:
  /tmp/b/include/urcu/static/pointer.h:101:18: error: invalid use of undefined type ‘struct cds_lfht’
    101 |     __typeof__(p + 0) _________p1;    \
        |                  ^
  /tmp/b/include/urcu/pointer.h:47:26: note: in expansion of macro ‘_rcu_dereference’
     47 | #define rcu_dereference  _rcu_dereference
        |                          ^~~~~~~~~~~~~~~~
  ../7ca7fe9c_regression.c:26:23: note: in expansion of macro ‘rcu_dereference’
     26 |  struct cds_lfht *t = rcu_dereference(totals);
        |                       ^~~~~~~~~~~~~~~

Removing _LGPL_SOURCE avoids the problem, but I'd rather not
introduce performance regressions.

In retrospect, my use of rcu_dereference seems unnecessary since
constructor functions should always fire before any threads are
created.

That means I can safely replace the assignment w/ CMM_STORE_SHARED,
and rcu_dereference with CMM_LOAD_SHARED, correct?

Sample code:
/*
 * shows a regression with _LGPL_SOURCE + urcu v0.11.4, commit:
 * 7ca7fe9c03217813 (Make temporary variable in _rcu_dereference non-const, 2021-07-29)
 * $(CC) -o x -I/path/to/include/ -L/path/to/lib/ __FILE__ -lurcu-bp -lurcu-cds
 *
 * Originally noticed in an LD_PRELOAD malloc wrapper:
 * https://80x24.org/mwrap.git (Ruby 2.6+)
 * https://80x24.org/mwrap-perl.git (Perl5)
 */
#define _LGPL_SOURCE
#include <urcu-bp.h>
#include <urcu/rculfhash.h>
static struct cds_lfht *totals; /* immortal */

__attribute__((constructor)) static void init_lfht(void)
{
	/* XXX replace with CMM_STORE_SHARED? */
	totals = cds_lfht_new(16384, 1, 0, CDS_LFHT_AUTO_RESIZE, 0);
}

int main(void) /* this is meant to be a malloc-family function in mwrap */
{
	/* XXX replace rcu_dereference with CMM_LOAD_SHARED? */
	struct cds_lfht *t = rcu_dereference(totals);
	return t ? 0 : 1;
}
---
Thanks for many years of urcu + cds!
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2022-08-09 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 18:19 Eric Wong via lttng-dev [this message]
2022-08-18 18:55 ` [lttng-dev] urcu 7ca7fe9c03 + _LGPL_SOURCE regression? Mathieu Desnoyers via lttng-dev
2022-08-20 18:51   ` Eric Wong via lttng-dev

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=20220809181927.GA3718@dcvr \
    --to=lttng-dev@lists.lttng.org \
    --cc=normalperson@yhbt.net \
    --cc=sam.saffron@gmail.com \
    --cc=simon.marchi@efficios.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 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.