Re: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Qian Cai <cai@xxxxxx>
Subject: Re: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390
From: Hugh Dickins <hughd@xxxxxxxxxx>
Date: Sun, 11 Oct 2020 13:23:12 -0700 (PDT)
Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, heiko.carstens@xxxxxxxxxx, borntraeger@xxxxxxxxxx, darrick.wong@xxxxxxxxxx, kirill@xxxxxxxxxxxxx, peterx@xxxxxxxxxx, yang.shi@xxxxxxxxxxxxxxxxx, hch@xxxxxx, linux-kernel@xxxxxxxxxxxxxxx, songliubraving@xxxxxx
In-reply-to: <20200617031906.GA5065@lca.pw>
References: <20200616013309.GB815@lca.pw> <20200616014859.GY8681@bombadil.infradead.org> <20200617031906.GA5065@lca.pw>
User-agent: Alpine 2.11 (LSU 23 2013-08-11)

Adding a note to update this thread: the v5.9 tree now has
033b5d775511 ("mm/khugepaged: fix filemap page_to_pgoff(page) != offset")
which fixes this VM_BUG_ON_PAGE (or data corruption) when CONFIG_NUMA
is not set: we are hoping that may have have been the problem here.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390
  - From: Qian Cai
- Re: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390
  - From: Matthew Wilcox
- Re: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390
  - From: Qian Cai

Prev by Date: Re: [PATCH v2 09/17] mm: Add unsafe_follow_pfn
Next by Date: Re: [PATCH v2 09/17] mm: Add unsafe_follow_pfn
Previous by thread: Re: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset) on s390
Next by thread: Re: [PATCH 00/25] mm: Page fault accounting cleanups
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite Info] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Linux Media] [Device Mapper]