[LTP] [linux-next:master] [mm] f1295af16a: ltp.madvise11.fail

[Oliver Sang]

hi, Kefeng Wang,

On Thu, Aug 29, 2024 at 04:20:56PM +0800, Kefeng Wang wrote:
> 
> 
> 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 a lot for information! yes, it was fixed.

normally our kernel test bot will check if the issue still exist on latest
tip of the branch. for this case, unfortunately, the check was missed by
accident.

sorry for the noise.


> 
> 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
> >