From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>,
amd-gfx@lists.freedesktop.org, linux-mm@kvack.org,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Jann Horn" <jannh@google.com>,
"Pedro Falcato" <pfalcato@suse.de>
Subject: Re: [PATCH v3 1/3] tools/testing/vma/vma_internal.h: provide fatal_signal_pending
Date: Mon, 5 Jan 2026 12:18:59 +0000 [thread overview]
Message-ID: <18f7f4ff-67f8-4a39-b6c4-893bfbed4955@lucifer.local> (raw)
In-Reply-To: <45dd9b02-7867-6e5a-4a64-02c4d43c9b68@redhat.com>
On Sun, Jan 04, 2026 at 10:15:36PM +0100, Mikulas Patocka wrote:
> Provide a dummy function fatal_signal_pending, because it will be used in
> the following patch in the function mm_take_all_locks.
>
> This commit avoids a test failure when the following patch will be apllied.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable@vger.kernel.org
No, please don't cc stable. Also don't cc stable without a Fixes tag.
This isn't backportable given you now need to backport to 5.10, 5.15, 6.1, 6.6,
6.12, 6.17.
I'm not sure how Andrew deals with a mix of Cc: stable and not-cc-stable patches
in a series, think he generally doesn't like, but I'm not sure how exactly we
are supposed to express order here otherwise. Andrew?
>
> ---
> tools/testing/vma/vma_internal.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: mm/tools/testing/vma/vma_internal.h
> ===================================================================
> --- mm.orig/tools/testing/vma/vma_internal.h 2026-01-04 21:19:10.000000000 +0100
> +++ mm/tools/testing/vma/vma_internal.h 2026-01-04 21:19:10.000000000 +0100
> @@ -1364,6 +1364,11 @@ static inline bool signal_pending(void *
> return false;
> }
>
> +static inline bool fatal_signal_pending(void *p)
> +{
> + return false;
> +}
> +
> static inline bool is_file_hugepages(struct file *file)
> {
> return false;
>
>
Thanks, Lorenzo
next prev parent reply other threads:[~2026-01-05 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 21:15 Mikulas Patocka
2026-01-05 12:18 ` Lorenzo Stoakes [this message]
2026-01-05 15:06 ` David Hildenbrand (Red Hat)
2026-01-05 15:36 ` Lorenzo Stoakes
2026-01-05 15:47 ` David Hildenbrand (Red Hat)
2026-01-05 16:07 ` Lorenzo Stoakes
2026-01-05 23:21 ` Andrew Morton
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=18f7f4ff-67f8-4a39-b6c4-893bfbed4955@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=mpatocka@redhat.com \
--cc=pfalcato@suse.de \
--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