From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, jannh@google.com, surenb@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel test robot <lkp@intel.com>
Subject: [PATCH 1/1] fixup! tools: remove atomic_set_release() usage in tools/
Date: Sun, 16 Feb 2025 21:43:51 -0800 [thread overview]
Message-ID: <20250217054351.2973666-1-surenb@google.com> (raw)
Userspace versions of both atomic_set_release() and atomic_set() get
translated into uatomic_set(). To avoid extra definitions of
atomic_set_release(), replace its usage inside refcount_set_release()
with atomic_set(). This results in no functional changes.
Fixes: 1465347e498f ("mm: make vma cache SLAB_TYPESAFE_BY_RCU")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202502170049.sHfzQwpv-lkp@intel.com/
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
tools/include/linux/refcount.h | 2 +-
tools/testing/vma/linux/atomic.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/include/linux/refcount.h b/tools/include/linux/refcount.h
index 1ace03e1a4f8..1f30956e070d 100644
--- a/tools/include/linux/refcount.h
+++ b/tools/include/linux/refcount.h
@@ -62,7 +62,7 @@ static inline void refcount_set(refcount_t *r, unsigned int n)
static inline void refcount_set_release(refcount_t *r, unsigned int n)
{
- atomic_set_release(&r->refs, n);
+ atomic_set(&r->refs, n);
}
static inline unsigned int refcount_read(const refcount_t *r)
diff --git a/tools/testing/vma/linux/atomic.h b/tools/testing/vma/linux/atomic.h
index 683383d0f2bf..788c597c4fde 100644
--- a/tools/testing/vma/linux/atomic.h
+++ b/tools/testing/vma/linux/atomic.h
@@ -7,7 +7,6 @@
#define atomic_inc(x) uatomic_inc(x)
#define atomic_read(x) uatomic_read(x)
#define atomic_set(x, y) uatomic_set(x, y)
-#define atomic_set_release(x, y) uatomic_set(x, y)
#define U8_MAX UCHAR_MAX
#ifndef atomic_cmpxchg_relaxed
base-commit: b2a64caeafad6e37df1c68f878bfdd06ff14f4ec
--
2.48.1.601.g30ceb7b040-goog
reply other threads:[~2025-02-17 5:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250217054351.2973666-1-surenb@google.com \
--to=surenb@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®