From: Dmitry Vyukov <dvyukov@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Eric B Munson <emunson@akamai.com>,
David Rientjes <rientjes@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Jeff Vander Stoep <jeffv@google.com>,
Alexander Kuleshov <kuleshovmail@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Hugh Dickins <hughd@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: BUG_ON(!PageLocked(page)) in munlock_vma_page/migrate_pages/__block_write_begin
Date: Tue, 15 Dec 2015 21:08:46 +0100 [thread overview]
Message-ID: <CACT4Y+ZCxQgJma5zDuLtHz4RXZGQEgDLwax+McS6iM8BnXsUhA@mail.gmail.com> (raw)
In-Reply-To: <20151215194213.GA15672@cmpxchg.org>
On Tue, Dec 15, 2015 at 8:42 PM, Johannes Weiner <hannes@cmpxchg.org> wrote:
> Hi Dmitry,
>
> On Tue, Dec 15, 2015 at 08:23:34PM +0100, Dmitry Vyukov wrote:
>>I am seeing lots of similar BUGs in different functions all pointing
>> to BUG_ON(!PageLocked(page)). I reproduced them on several recent
>> commits, including stock 6764e5ebd5c62236d082f9ae030674467d0b2779 (Dec
>> 9) with no changes on top and no KASAN/etc.
>
> This should be fixed in newer kernels with this commit:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfd01f026058a59a513f8a365b439a0681b803af
Testing with this patch now. Thanks!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-12-15 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 19:23 Dmitry Vyukov
2015-12-15 19:42 ` Johannes Weiner
2015-12-15 20:08 ` Dmitry Vyukov [this message]
2015-12-17 12:53 ` Dmitry Vyukov
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=CACT4Y+ZCxQgJma5zDuLtHz4RXZGQEgDLwax+McS6iM8BnXsUhA@mail.gmail.com \
--to=dvyukov@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=emunson@akamai.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jeffv@google.com \
--cc=kcc@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=vbabka@suse.cz \
/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