From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, David Hildenbrand <david@kernel.org>
Subject: Re: [PATCH] mm: Make VM_FAULT_RESULT_TRACE compatible with sparse
Date: Fri, 7 Aug 2026 18:21:10 +0100 [thread overview]
Message-ID: <anYSxm7GHV-bymDQ@lucifer> (raw)
In-Reply-To: <e56c9e2aead04f79192c3110de80d846e41e3791.1786122711.git.bvanassche@acm.org>
On Fri, Aug 07, 2026 at 10:13:10AM -0700, Bart Van Assche wrote:
> Fix the following sparse warnings that appear while building f2fs:
>
> ./include/trace/events/f2fs.h:1469:1: warning: incorrect type in initializer (different base types)
> ./include/trace/events/f2fs.h:1469:1: expected unsigned long mask
> ./include/trace/events/f2fs.h:1469:1: got restricted vm_fault_t
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
I no longer work at Oracle ;)
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
This seems reasonable to me, AFAICT.
Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> include/linux/mm_types.h | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index b18c2b2e7d2c..fcd7d6cfce0f 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -1703,20 +1703,20 @@ enum vm_fault_reason {
> VM_FAULT_SIGSEGV | VM_FAULT_HWPOISON | \
> VM_FAULT_HWPOISON_LARGE | VM_FAULT_FALLBACK)
>
> -#define VM_FAULT_RESULT_TRACE \
> - { VM_FAULT_OOM, "OOM" }, \
> - { VM_FAULT_SIGBUS, "SIGBUS" }, \
> - { VM_FAULT_MAJOR, "MAJOR" }, \
> - { VM_FAULT_HWPOISON, "HWPOISON" }, \
> - { VM_FAULT_HWPOISON_LARGE, "HWPOISON_LARGE" }, \
> - { VM_FAULT_SIGSEGV, "SIGSEGV" }, \
> - { VM_FAULT_NOPAGE, "NOPAGE" }, \
> - { VM_FAULT_LOCKED, "LOCKED" }, \
> - { VM_FAULT_RETRY, "RETRY" }, \
> - { VM_FAULT_FALLBACK, "FALLBACK" }, \
> - { VM_FAULT_DONE_COW, "DONE_COW" }, \
> - { VM_FAULT_NEEDDSYNC, "NEEDDSYNC" }, \
> - { VM_FAULT_COMPLETED, "COMPLETED" }
> +#define VM_FAULT_RESULT_TRACE \
> + { (__force u32)VM_FAULT_OOM, "OOM" }, \
> + { (__force u32)VM_FAULT_SIGBUS, "SIGBUS" }, \
> + { (__force u32)VM_FAULT_MAJOR, "MAJOR" }, \
> + { (__force u32)VM_FAULT_HWPOISON, "HWPOISON" }, \
> + { (__force u32)VM_FAULT_HWPOISON_LARGE, "HWPOISON_LARGE" }, \
> + { (__force u32)VM_FAULT_SIGSEGV, "SIGSEGV" }, \
> + { (__force u32)VM_FAULT_NOPAGE, "NOPAGE" }, \
> + { (__force u32)VM_FAULT_LOCKED, "LOCKED" }, \
> + { (__force u32)VM_FAULT_RETRY, "RETRY" }, \
> + { (__force u32)VM_FAULT_FALLBACK, "FALLBACK" }, \
> + { (__force u32)VM_FAULT_DONE_COW, "DONE_COW" }, \
> + { (__force u32)VM_FAULT_NEEDDSYNC, "NEEDDSYNC" }, \
> + { (__force u32)VM_FAULT_COMPLETED, "COMPLETED" }
>
> struct vm_special_mapping {
> const char *name; /* The name, e.g. "[vdso]". */
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-08-07 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 17:13 [PATCH] mm: Make VM_FAULT_RESULT_TRACE compatible with sparse Bart Van Assche
2026-08-07 17:21 ` Lorenzo Stoakes (ARM) [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=anYSxm7GHV-bymDQ@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.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