From: Song Liu <songliubraving@fb.com>
To: Matthew Wilcox <willy@infradead.org>,
Denis Lisov <dennis.lissov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Bug 206569] BUG at mm/filemap.c:2529: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset)
Date: Tue, 19 May 2020 00:52:48 +0000 [thread overview]
Message-ID: <BDFF8E67-E7FD-42A9-AAE5-B58122488F1C@fb.com> (raw)
In-Reply-To: <20200501180513.GB29705@bombadil.infradead.org>
> On May 1, 2020, at 11:05 AM, Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Feb 26, 2020 at 10:44:29PM +0000, Song Liu wrote:
>> On my VM, I saw khugepaged put .text of python binary in 2MB pages.
>> This is caused by khugepaged_always() == true in hugepage_vma_check().
>> I guess this means the bug exists w/o CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS,
>> but CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS makes it easier to trigger.
>>
>> However, I haven't got luck to repro this issue.
>
> I fixed something as part of the large pages work which might have also
> fixed this problem. However, you have CONFIG_DEBUG_VM enabled, so it
> would have actually triggered the bug.
>
> http://git.infradead.org/users/willy/linux-dax.git/commitdiff/2f864b6c27caa737ccfe65a86972f6b73a66a095
>
> I don't think anything else I've changed will fix this bug, whatever it is ;-(
I am testing with 5.5.3. However, I still got no luck here. :(
I haven't figured out how to build KDE in Gentoo. I tried to build kernel,
many many times, without repro of the issue.
Denis, could you please share some information about your test system:
1. # of CPUs;
2. size of RAM;
3. size of swap, if any;
4. .config file of the kernel that repros the issue.
Thanks,
Song
next prev parent reply other threads:[~2020-05-19 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-206569-27@https.bugzilla.kernel.org/>
[not found] ` <bug-206569-27-Tvdf5Wtr8t@https.bugzilla.kernel.org/>
2020-02-19 22:46 ` Andrew Morton
2020-02-20 0:25 ` Matthew Wilcox
2020-02-20 0:37 ` Yang Shi
2020-02-20 1:21 ` Matthew Wilcox
2020-02-20 23:56 ` Denis Lisov
2020-02-21 1:26 ` Song Liu
2020-02-21 8:57 ` Denis Lisov
2020-02-26 22:44 ` Song Liu
2020-05-01 18:05 ` Matthew Wilcox
2020-05-19 0:52 ` Song Liu [this message]
2020-10-11 20:21 ` 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=BDFF8E67-E7FD-42A9-AAE5-B58122488F1C@fb.com \
--to=songliubraving@fb.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dennis.lissov@gmail.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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