From: David Hildenbrand <david@redhat.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Andrew Morton <akpm@linux-foundation.org>,
Simona Vetter <simona.vetter@ffwll.ch>,
Alistair Popple <apopple@nvidia.com>, Alex Shi <alexs@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Dave Airlie <airlied@gmail.com>, Jann Horn <jannh@google.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Jerome Glisse <jglisse@redhat.com>,
John Hubbard <jhubbard@nvidia.com>,
Jonathan Corbet <corbet@lwn.net>,
Karol Herbst <kherbst@redhat.com>,
Liam Howlett <liam.howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Lyude <lyude@redhat.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Peter Xu <peterx@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
SeongJae Park <sj@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Yanteng Si <si.yanteng@linux.dev>,
Barry Song <v-songbaohua@oppo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ltp@lists.linux.it
Subject: Re: [akpm-mm:mm-stable] [mm] c25465eb76: ltp.swapon03.fail
Date: Mon, 24 Mar 2025 12:53:55 +0100 [thread overview]
Message-ID: <73bea938-15a2-4b4a-8d31-0db9f9c476e0@redhat.com> (raw)
In-Reply-To: <202503241635.4c94156d-lkp@intel.com>
On 24.03.25 09:49, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "ltp.swapon03.fail" on:
>
> commit: c25465eb7630ffcadaab29c1010071512f8c9621 ("mm: use single SWP_DEVICE_EXCLUSIVE entry type")
> https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-stable
>
>
> in testcase: ltp
> version: ltp-x86_64-042eff32a-1_20250322
> with following parameters:
>
> disk: 1HDD
> fs: btrfs
> test: syscalls-04/swapon03
>
>
>
> config: x86_64-rhel-9.4-ltp
> compiler: gcc-12
> test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory
LTP needs fixing.
tst_max_swapfiles() detects the number of supported swapfiles by parsing
the kernel config, expecting that with CONFIG_DEVICE_PRIVATE we'd use 4
on newer kernels.
Now it's "3", and consequently we support one more swapfile which the
test cannot deal with (expecting a failure)
So, all good from a kernel perspective.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-03-24 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 8:49 kernel test robot
2025-03-24 11:53 ` David Hildenbrand [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=73bea938-15a2-4b4a-8d31-0db9f9c476e0@redhat.com \
--to=david@redhat.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=apopple@nvidia.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=jannh@google.com \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=kherbst@redhat.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=ltp@lists.linux.it \
--cc=lyude@redhat.com \
--cc=mhiramat@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=oliver.sang@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=simona.vetter@ffwll.ch \
--cc=sj@kernel.org \
--cc=v-songbaohua@oppo.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