From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, liam.howlett@oracle.com,
vbabka@suse.cz, jannh@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/1] tools: fix atomic_set() definition to set the value correctly
Date: Thu, 2 Jan 2025 14:12:24 +0000 [thread overview]
Message-ID: <9c5a1f67-728b-48c8-b124-280078486a31@lucifer.local> (raw)
In-Reply-To: <20241227222220.1726384-1-surenb@google.com>
On Fri, Dec 27, 2024 at 02:22:20PM -0800, Suren Baghdasaryan wrote:
> Currently vma test is failing because of the new vma_assert_attached()
> assertion. The check is failing because previous refcount_set() inside
> vma_mark_attached() is a NoOp. Fix the definition of atomic_set() to
> correctly set the value of the atomic.
>
> Fixes: 9325b8b5a1cb ("tools: add skeleton code for userland testing of VMA logic")
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
LGTM:
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> Applies over mm-unstable
>
> tools/testing/shared/linux/maple_tree.h | 2 +-
> tools/testing/vma/linux/atomic.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/shared/linux/maple_tree.h b/tools/testing/shared/linux/maple_tree.h
> index 06c89bdcc515..f67d47d32857 100644
> --- a/tools/testing/shared/linux/maple_tree.h
> +++ b/tools/testing/shared/linux/maple_tree.h
> @@ -2,6 +2,6 @@
> #define atomic_t int32_t
> #define atomic_inc(x) uatomic_inc(x)
> #define atomic_read(x) uatomic_read(x)
> -#define atomic_set(x, y) do {} while (0)
> +#define atomic_set(x, y) uatomic_set(x, y)
> #define U8_MAX UCHAR_MAX
> #include "../../../../include/linux/maple_tree.h"
> diff --git a/tools/testing/vma/linux/atomic.h b/tools/testing/vma/linux/atomic.h
> index 2e2021553196..788c597c4fde 100644
> --- a/tools/testing/vma/linux/atomic.h
> +++ b/tools/testing/vma/linux/atomic.h
> @@ -6,7 +6,7 @@
> #define atomic_t int32_t
> #define atomic_inc(x) uatomic_inc(x)
> #define atomic_read(x) uatomic_read(x)
> -#define atomic_set(x, y) do {} while (0)
> +#define atomic_set(x, y) uatomic_set(x, y)
> #define U8_MAX UCHAR_MAX
>
> #ifndef atomic_cmpxchg_relaxed
> --
> 2.47.1.613.gc27f4b7a9f-goog
>
prev parent reply other threads:[~2025-01-02 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 22:22 Suren Baghdasaryan
2025-01-02 14:12 ` Lorenzo Stoakes [this message]
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=9c5a1f67-728b-48c8-b124-280078486a31@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.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