From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/testing/selftests: fix gup_longterm for unknown fs
Date: Tue, 6 Jan 2026 18:37:50 +0000 [thread overview]
Message-ID: <09292ea1-e722-4897-b42a-dda517ddd02e@lucifer.local> (raw)
In-Reply-To: <56b7d3e2-fcfa-42c2-988f-907086f031d1@sirena.org.uk>
On Tue, Jan 06, 2026 at 05:29:51PM +0000, Mark Brown wrote:
> On Tue, Jan 06, 2026 at 09:28:36AM -0800, Andrew Morton wrote:
> > On Tue, 6 Jan 2026 15:45:47 +0000 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
>
> > > Commit 66bce7afbaca ("selftests/mm: fix test result reporting in
> > > gup_longterm") introduced a small bug causing unknown filesystems to always
> > > result in a test failure.
>
> > > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > > Fixes: 66bce7afbaca ("selftests/mm: fix test result reporting in gup_longterm")
>
> > -stable users might want this?
>
> I think so.
Yeh I did wonder if we'd want that, and I think you confirmed Mark that people
do potentially run tests on stable kernels? Or I can't remember :)
Anyway if so then sure. I think this should be an easy automagic-backport
anyway!
Cheers, Lorenzo
next prev parent reply other threads:[~2026-01-06 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:45 Lorenzo Stoakes
2026-01-06 17:28 ` Andrew Morton
2026-01-06 17:29 ` Mark Brown
2026-01-06 18:37 ` Lorenzo Stoakes [this message]
2026-01-06 18:40 ` David Hildenbrand (Red Hat)
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=09292ea1-e722-4897-b42a-dda517ddd02e@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.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