From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: syzbot+b591856e0f0139f83023@syzkaller.appspotmail.com,
lkp@intel.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
oe-lkp@lists.linux.dev, akpm@linux-foundation.org,
ltp@lists.linux.it, Edward AD <eadavis@sina.com>
Subject: Re: [LTP] [PATCH] mm: as the same logic with queue_pages_range
Date: Wed, 13 Sep 2023 11:10:10 +0200 [thread overview]
Message-ID: <ZQF8cn4k1qqdYj8x@yuki> (raw)
In-Reply-To: <202309121302.8864096c-oliver.sang@intel.com>
Hi!
> Running tests.......
> <<<test_start>>>
> tag=vma02 stime=1694438526
> cmdline="vma02"
> contacts=""
> analysis=exit
> <<<test_output>>>
> vma02 0 TINFO : pid = 3639 addr = 0x7f5202dd6000
> vma02 0 TINFO : start = 0x7f5202dd6000, end = 0x7f5202dd7000
> vma02 0 TINFO : start = 0x7f5202dd7000, end = 0x7f5202dd8000
> vma02 0 TINFO : start = 0x7f5202dd8000, end = 0x7f5202dd9000
> vma02 1 TFAIL : vma02.c:144: >1 unmerged VMAs.
> incrementing stop
So the test is reproducer for:
commit 9d8cebd4bcd7c3878462fdfda34bbcdeb4df7ef4
Author: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Date: Fri Mar 5 13:41:57 2010 -0800
mm: fix mbind vma merge problem
Strangely, current mbind() doesn't merge vma with neighbor vma although it's possible.
Unfortunately, many vma can reduce performance...
And what the test does is:
- map 3 continous pages
- popluate
- mbind() first page
- mbind() all three pages
- checks that there is only single VMA for the pages after second
mbind()
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: Edward AD <eadavis@sina.com>,
syzbot+b591856e0f0139f83023@syzkaller.appspotmail.com,
lkp@intel.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
oe-lkp@lists.linux.dev, akpm@linux-foundation.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] mm: as the same logic with queue_pages_range
Date: Wed, 13 Sep 2023 11:10:10 +0200 [thread overview]
Message-ID: <ZQF8cn4k1qqdYj8x@yuki> (raw)
In-Reply-To: <202309121302.8864096c-oliver.sang@intel.com>
Hi!
> Running tests.......
> <<<test_start>>>
> tag=vma02 stime=1694438526
> cmdline="vma02"
> contacts=""
> analysis=exit
> <<<test_output>>>
> vma02 0 TINFO : pid = 3639 addr = 0x7f5202dd6000
> vma02 0 TINFO : start = 0x7f5202dd6000, end = 0x7f5202dd7000
> vma02 0 TINFO : start = 0x7f5202dd7000, end = 0x7f5202dd8000
> vma02 0 TINFO : start = 0x7f5202dd8000, end = 0x7f5202dd9000
> vma02 1 TFAIL : vma02.c:144: >1 unmerged VMAs.
> incrementing stop
So the test is reproducer for:
commit 9d8cebd4bcd7c3878462fdfda34bbcdeb4df7ef4
Author: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Date: Fri Mar 5 13:41:57 2010 -0800
mm: fix mbind vma merge problem
Strangely, current mbind() doesn't merge vma with neighbor vma although it's possible.
Unfortunately, many vma can reduce performance...
And what the test does is:
- map 3 continous pages
- popluate
- mbind() first page
- mbind() all three pages
- checks that there is only single VMA for the pages after second
mbind()
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2023-09-13 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 1:03 [syzbot] [mm?] kernel BUG in vma_replace_policy syzbot
2023-09-06 6:19 ` [PATCH] mm: as the same logic with queue_pages_range Edward AD
2023-09-06 12:06 ` Matthew Wilcox
2023-09-12 5:20 ` [LTP] " kernel test robot
2023-09-12 5:20 ` kernel test robot
2023-09-13 9:10 ` Cyril Hrubis [this message]
2023-09-13 9:10 ` [LTP] " Cyril Hrubis
2023-09-14 5:53 ` [LTP] [PATCH] mm: extpand queue_pages_range() to find and lock the vma range Edward AD
2023-09-14 5:53 ` Edward AD
2023-09-08 18:04 ` [syzbot] [mm?] kernel BUG in vma_replace_policy syzbot
2023-09-08 18:04 ` syzbot
2023-09-08 18:04 ` syzbot
2023-09-12 5:30 ` Matthew Wilcox
2023-09-12 6:09 ` syzbot
2023-09-12 14:55 ` Matthew Wilcox
2023-09-12 15:03 ` Suren Baghdasaryan
2023-09-12 16:00 ` Suren Baghdasaryan
2023-09-13 16:05 ` Suren Baghdasaryan
2023-09-13 16:46 ` Suren Baghdasaryan
2023-09-14 18:20 ` Suren Baghdasaryan
2023-09-14 19:09 ` Matthew Wilcox
2023-09-14 20:00 ` Suren Baghdasaryan
2023-09-14 20:53 ` Suren Baghdasaryan
2023-09-14 21:24 ` Matthew Wilcox
2023-09-14 22:21 ` Suren Baghdasaryan
2023-09-15 4:26 ` Hugh Dickins
2023-09-15 16:09 ` Suren Baghdasaryan
2023-09-15 18:05 ` Suren Baghdasaryan
2023-09-16 2:43 ` Hugh Dickins
2023-09-18 21:20 ` Suren Baghdasaryan
2023-09-15 18:26 ` Matthew Wilcox
2023-09-16 2:54 ` Hugh Dickins
2023-09-16 1:35 ` Yang Shi
2023-09-16 3:57 ` Hugh Dickins
2023-09-18 22:34 ` Yang Shi
2023-09-19 0:34 ` Hugh Dickins
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=ZQF8cn4k1qqdYj8x@yuki \
--to=chrubis@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=eadavis@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=syzbot+b591856e0f0139f83023@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.