From: Juergen Gross <jgross@suse.com>
To: Julien Grall <julien@xen.org>, xen-devel@lists.xenproject.org
Cc: Wei Liu <wl@xen.org>, Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH v3 12/17] tools/xenstore: don't let hashtable_remove() return the removed value
Date: Wed, 18 Jan 2023 07:17:34 +0100 [thread overview]
Message-ID: <fb160e56-8a6a-85fd-0140-ae25322479c7@suse.com> (raw)
In-Reply-To: <19a0c39c-31b3-ce9c-6f03-466b6109b88f@xen.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 2366 bytes --]
On 17.01.23 23:03, Julien Grall wrote:
> Hi Juergen,
>
> On 17/01/2023 09:11, Juergen Gross wrote:
>> Letting hashtable_remove() return the value of the removed element is
>> not used anywhere in Xenstore, and it conflicts with a hashtable
>> created specifying the HASHTABLE_FREE_VALUE flag.
>>
>> So just drop returning the value.
>
> Any reason this can't be void? If there are, then I would consider to return a
> bool as the return can only be 2 values.
I think you are right. Switching to void should be fine.
>
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> V3:
>> - new patch
>> ---
>> tools/xenstore/hashtable.c | 10 +++++-----
>> tools/xenstore/hashtable.h | 4 ++--
>> 2 files changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/tools/xenstore/hashtable.c b/tools/xenstore/hashtable.c
>> index 299549c51e..6738719e47 100644
>> --- a/tools/xenstore/hashtable.c
>> +++ b/tools/xenstore/hashtable.c
>> @@ -214,7 +214,7 @@ hashtable_search(struct hashtable *h, void *k)
>> }
>> /*****************************************************************************/
>> -void * /* returns value associated with key */
>> +int
>> hashtable_remove(struct hashtable *h, void *k)
>> {
>> /* TODO: consider compacting the table when the load factor drops enough,
>> @@ -222,7 +222,6 @@ hashtable_remove(struct hashtable *h, void *k)
>> struct entry *e;
>> struct entry **pE;
>> - void *v;
>> unsigned int hashvalue, index;
>> hashvalue = hash(h,k);
>> @@ -236,16 +235,17 @@ hashtable_remove(struct hashtable *h, void *k)
>> {
>> *pE = e->next;
>> h->entrycount--;
>> - v = e->v;
>> if (h->flags & HASHTABLE_FREE_KEY)
>> free(e->k);
>> + if (h->flags & HASHTABLE_FREE_VALUE)
>> + free(e->v);
>
> I don't quite understand how this change is related to this patch.
With not returning the value pointer any longer there would be no way
for the caller to free it, so it must be freed by hashtable_remove()
if the related flag was set.
I can add a sentence to the commit message.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-01-18 6:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 9:11 [PATCH v3 00/17] tools/xenstore: do some cleanup and fixes Juergen Gross
2023-01-17 9:11 ` [PATCH v3 01/17] tools/xenstore: let talloc_free() preserve errno Juergen Gross
2023-01-17 13:56 ` Julien Grall
2023-01-17 9:11 ` [PATCH v3 02/17] tools/xenstore: remove all watches when a domain has stopped Juergen Gross
2023-01-17 9:11 ` [PATCH v3 03/17] tools/xenstore: add hashlist for finding struct domain by domid Juergen Gross
2023-01-17 9:11 ` [PATCH v3 04/17] tools/xenstore: introduce dummy nodes for special watch paths Juergen Gross
2023-01-17 14:02 ` Julien Grall
2023-01-17 15:50 ` Juergen Gross
2023-01-17 9:11 ` [PATCH v3 05/17] tools/xenstore: replace watch->relative_path with a prefix length Juergen Gross
2023-01-17 14:04 ` Julien Grall
2023-01-17 9:11 ` [PATCH v3 06/17] tools/xenstore: move changed domain handling Juergen Gross
2023-01-17 14:06 ` Julien Grall
2023-01-17 9:11 ` [PATCH v3 07/17] tools/xenstore: change per-domain node accounting interface Juergen Gross
2023-01-18 7:31 ` Juergen Gross
2023-01-17 9:11 ` [PATCH v3 08/17] tools/xenstore: don't allow creating too many nodes in a transaction Juergen Gross
2023-01-17 14:08 ` Julien Grall
2023-01-17 15:51 ` Juergen Gross
2023-01-17 9:11 ` [PATCH v3 09/17] tools/xenstore: replace literal domid 0 with dom0_domid Juergen Gross
2023-01-17 9:11 ` [PATCH v3 10/17] tools/xenstore: make domain_is_unprivileged() an inline function Juergen Gross
2023-01-17 9:11 ` [PATCH v3 11/17] tools/xenstore: let chk_domain_generation() return a bool Juergen Gross
2023-01-17 9:11 ` [PATCH v3 12/17] tools/xenstore: don't let hashtable_remove() return the removed value Juergen Gross
2023-01-17 22:03 ` Julien Grall
2023-01-18 6:17 ` Juergen Gross [this message]
2023-01-18 9:27 ` Julien Grall
2023-01-17 9:11 ` [PATCH v3 13/17] tools/xenstore: switch hashtable to use the talloc framework Juergen Gross
2023-01-18 9:30 ` Julien Grall
2023-01-17 9:11 ` [PATCH v3 14/17] tools/xenstore: make log macro globally available Juergen Gross
2023-01-17 9:11 ` [PATCH v3 15/17] tools/xenstore: introduce trace classes Juergen Gross
2023-01-17 22:15 ` Julien Grall
2023-01-18 6:18 ` Juergen Gross
2023-01-17 9:11 ` [PATCH v3 16/17] tools/xenstore: let check_store() check the accounting data Juergen Gross
2023-01-17 22:36 ` Julien Grall
2023-01-18 6:23 ` Juergen Gross
2023-01-18 9:35 ` Julien Grall
2023-01-18 9:37 ` Juergen Gross
2023-01-17 9:11 ` [PATCH v3 17/17] tools/xenstore: make output of "xenstore-control help" more pretty Juergen Gross
2023-01-17 22:39 ` Julien Grall
2023-01-17 9:37 ` [PATCH v3 00/17] tools/xenstore: do some cleanup and fixes Jan Beulich
2023-01-17 9:50 ` Juergen Gross
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=fb160e56-8a6a-85fd-0140-ae25322479c7@suse.com \
--to=jgross@suse.com \
--cc=anthony.perard@citrix.com \
--cc=julien@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.