From: valdis.kletnieks@vt.edu
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Punit Agrawal <punit.agrawal@arm.com>,
Steve Capper <steve.capper@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrei Vagin <avagin@gmail.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: linux-next: BUG: Bad page state in process ip6tables-save pfn:1499f4
Date: Tue, 27 Jun 2017 14:39:53 -0400 [thread overview]
Message-ID: <8643.1498588793@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20170627163734.6js4jkwkwlz6xwir@black.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Tue, 27 Jun 2017 19:37:34 +0300, "Kirill A. Shutemov" said:
> > > commit c3aab7b2d4e8434d53bc81770442c14ccf0794a8
> > > Merge: 849c34f 93a7379
> > > Author: Stephen Rothwell
> > > Date: Fri Jun 23 16:40:07 2017 +1000
> > >
> > > Merge branch 'akpm-current/current'
> >
> > Hm is it really the merge of mmotm itself and not one of the patches in
> > mmotm?
> > Anyway smells like THP, adding Kirill.
>
> Okay, it took a while to figure it out.
>
> The bug is in patch "mm, gup: ensure real head page is ref-counted when
> using hugepages". We should look for a head *before* the loop. Otherwise
> 'page' may point to the first page beyond the compound page.
>
> The patch below should help.
Confirmed that fixes the BUGs that I was hitting.
Tested-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
prev parent reply other threads:[~2017-06-27 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 6:21 linux-next: BUG: Bad page state in process ip6tables-save pfn:1499f4 Andrei Vagin
2017-06-24 0:17 ` Andrei Vagin
2017-06-24 15:08 ` Andrei Vagin
2017-06-27 7:18 ` Vlastimil Babka
2017-06-27 16:37 ` Kirill A. Shutemov
2017-06-27 16:53 ` Punit Agrawal
2017-06-27 17:04 ` Kirill A. Shutemov
2017-06-28 11:32 ` Punit Agrawal
2017-06-27 18:24 ` Andrei Vagin
2017-06-27 18:39 ` valdis.kletnieks [this message]
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=8643.1498588793@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=gorcunov@openvz.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=punit.agrawal@arm.com \
--cc=sfr@canb.auug.org.au \
--cc=steve.capper@arm.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;
as well as URLs for NNTP newsgroup(s).