From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Oscar Salvador <osalvador@suse.de>,
<linux-kernel@vger.kernel.org>, <ltp@lists.linux.it>
Subject: Re: [linux-next:master] [mm] f1295af16a: ltp.madvise11.fail
Date: Thu, 29 Aug 2024 16:20:56 +0800 [thread overview]
Message-ID: <dfeb5f5f-2b21-4b8f-bb8b-7170ef001773@huawei.com> (raw)
In-Reply-To: <202408291314.bdbfa468-oliver.sang@intel.com>
On 2024/8/29 16:13, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "ltp.madvise11.fail" on:
>
> commit: f1295af16abee075de68400c58550cffacc29eb1 ("mm: migrate: add isolate_folio_to_list()")
f1295af16abee075de68400c58550cffacc29eb1 tags/next-20240828~164^2~86
on next-20240828, it was fixed in the next patch,
f1295af16abe mm: migrate: add isolate_folio_to_list()
4e3a04695e25 mm-migrate-add-isolate_folio_to_list-fix // this should fix
the issue.
or please test next-20240829
Thanks.
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: ltp
> version: ltp-x86_64-14c1f76-1_20240824
> with following parameters:
>
> disk: 1HDD
> fs: btrfs
> test: syscalls-01/madvise11
>
>
>
> compiler: gcc-12
> test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202408291314.bdbfa468-oliver.sang@intel.com
>
next prev parent reply other threads:[~2024-08-29 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 8:13 kernel test robot
2024-08-29 8:20 ` Kefeng Wang [this message]
2024-08-30 8:21 ` Oliver Sang
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=dfeb5f5f-2b21-4b8f-bb8b-7170ef001773@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=nao.horiguchi@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=osalvador@suse.de \
/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