From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: "Ondřej Surý" <ondrej@sury.org>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] [PATCH 7/7] Fix: uatomic_or() need retyping to uintptr_t in rculfhash.c
Date: Tue, 21 Mar 2023 16:20:27 -0400 [thread overview]
Message-ID: <37b3c295-77a8-2341-2b26-f82005a26345@efficios.com> (raw)
In-Reply-To: <20230321145146.1095875-1-ondrej@sury.org>
On 2023-03-21 10:51, Ondřej Surý via lttng-dev wrote:
> When adding REMOVED_FLAG to the pointers in the rculfhash
> implementation, retype the generic pointer to unsigned long to fix the
> following compiler error:
You will need to update the patch subject as well.
Thanks,
Mathieu
>
> rculfhash.c:1201:2: error: address argument to atomic operation must be a pointer to integer ('struct cds_lfht_node **' invalid)
> uatomic_or(&node->next, REMOVED_FLAG);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/urcu/uatomic.h:60:8: note: expanded from macro 'uatomic_or'
> (void)__atomic_or_fetch((addr), (mask), __ATOMIC_RELAXED)
> ^ ~~~~~~
> rculfhash.c:1444:3: error: address argument to atomic operation must be a pointer to integer ('struct cds_lfht_node **' invalid)
> uatomic_or(&fini_bucket->next, REMOVED_FLAG);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/urcu/uatomic.h:60:8: note: expanded from macro 'uatomic_or'
> (void)__atomic_or_fetch((addr), (mask), __ATOMIC_RELAXED)
> ^ ~~~~~~
>
> This was not a problem before because the way the uatomic_or was
> implemented, but now we directly pass the addr to __atomic_or_fetch()
> and the compiler doesn't like the implicit conversion from pointer to
> pointer to integer.
>
> Signed-off-by: Ondřej Surý <ondrej@sury.org>
> ---
> src/rculfhash.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/rculfhash.c b/src/rculfhash.c
> index b456415..5292725 100644
> --- a/src/rculfhash.c
> +++ b/src/rculfhash.c
> @@ -1198,7 +1198,7 @@ int _cds_lfht_del(struct cds_lfht *ht, unsigned long size,
> * Knowing which wins the race will be known after the garbage
> * collection phase, stay tuned!
> */
> - uatomic_or(&node->next, REMOVED_FLAG);
> + uatomic_or((unsigned long *)&node->next, REMOVED_FLAG);
> /* We performed the (logical) deletion. */
>
> /*
> @@ -1441,7 +1441,7 @@ void remove_table_partition(struct cds_lfht *ht, unsigned long i,
> dbg_printf("remove entry: order %lu index %lu hash %lu\n",
> i, j, j);
> /* Set the REMOVED_FLAG to freeze the ->next for gc */
> - uatomic_or(&fini_bucket->next, REMOVED_FLAG);
> + uatomic_or((unsigned long *)&fini_bucket->next, REMOVED_FLAG);
> _cds_lfht_gc_bucket(parent_bucket, fini_bucket);
> }
> ht->flavor->read_unlock();
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-03-21 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 14:51 Ondřej Surý via lttng-dev
2023-03-21 20:20 ` Mathieu Desnoyers via lttng-dev [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-21 13:30 [lttng-dev] (no subject) Ondřej Surý via lttng-dev
2023-03-21 13:31 ` [lttng-dev] [PATCH 7/7] Fix: uatomic_or() need retyping to uintptr_t in rculfhash.c Ondřej Surý 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=37b3c295-77a8-2341-2b26-f82005a26345@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=ondrej@sury.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