From: Emilio Cota <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Emilio Cota" <cota@braap.org>
Subject: [PATCH 2/4] util/qht: add missing atomic_set(hashes[i])
Date: Sun, 8 Jan 2023 11:39:03 -0500 [thread overview]
Message-ID: <20230108163905.59601-3-cota@braap.org> (raw)
In-Reply-To: <20230108163905.59601-1-cota@braap.org>
We forgot to add this one in "a890643958 util/qht: atomically set b->hashes".
Detected with tsan.
Signed-off-by: Emilio Cota <cota@braap.org>
---
util/qht.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/util/qht.c b/util/qht.c
index 065fc501f4..15866299e6 100644
--- a/util/qht.c
+++ b/util/qht.c
@@ -688,7 +688,7 @@ static inline void qht_bucket_remove_entry(struct qht_bucket *orig, int pos)
int i;
if (qht_entry_is_last(orig, pos)) {
- orig->hashes[pos] = 0;
+ qatomic_set(&orig->hashes[pos], 0);
qatomic_set(&orig->pointers[pos], NULL);
return;
}
--
2.34.1
next prev parent reply other threads:[~2023-01-08 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 16:39 [PATCH 0/4] tsan fixes Emilio Cota
2023-01-08 16:39 ` [PATCH 1/4] cpu: free cpu->tb_jmp_cache with RCU Emilio Cota
2023-01-08 19:19 ` Richard Henderson
2023-01-09 21:52 ` Emilio Cota
2023-01-08 16:39 ` Emilio Cota [this message]
2023-01-08 19:20 ` [PATCH 2/4] util/qht: add missing atomic_set(hashes[i]) Richard Henderson
2023-01-08 19:54 ` Philippe Mathieu-Daudé
2023-01-08 16:39 ` [PATCH 3/4] util/qht: use striped locks under TSAN Emilio Cota
2023-01-08 19:51 ` Richard Henderson
2023-01-09 22:10 ` Emilio Cota
2023-01-08 16:39 ` [PATCH 4/4] plugins: make qemu_plugin_user_exit's locking order consistent with fork_start's Emilio Cota
2023-01-08 19:31 ` Richard Henderson
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=20230108163905.59601-3-cota@braap.org \
--to=cota@braap.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.