From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Borislav Petkov <bp@alien8.de>, Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
x86-ml <x86@kernel.org>, linux-mm <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: kernel BUG at mm/swap.c:134! - page dumped because: VM_BUG_ON_PAGE(page_mapcount(page) != 0)
Date: Mon, 20 Apr 2015 00:02:00 +0000 [thread overview]
Message-ID: <20150420000200.GC10725@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <CA+55aFxLjBFUPYFJDGo236Ubdxy9s32gZ9VU43PA3RCkxJxdbw@mail.gmail.com>
On Sat, Apr 18, 2015 at 06:12:56PM -0400, Linus Torvalds wrote:
> On Sat, Apr 18, 2015 at 5:59 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Sat, Apr 18, 2015 at 5:56 PM, Kirill A. Shutemov
> > <kirill@shutemov.name> wrote:
> >>
> >> Andrea has already seen the bug and pointed to 8d63d99a5dfb as possible
> >> cause. I don't see why the commit could broke anything, but it worth
> >> trying to revert and test.
> >
> > Ahh, yes, that does look like a more likely culprit.
>
> That said, I do think we should likely also do that
>
> WARN_ON_ONCE(PageHuge(page));
>
> in __put_compound_page() rather than just silently saying "no refcount
> changes for this magical case that shouldn't even happen". If it
> shouldn't happen, then we should warn about it, not try to ":handle"
> some case that shouldn't happen and shouldn't matter.
__put_compound_page() can be called for PageHuge, so I don't think that adding
WARN_ON_ONCE(PageHuge) is good (, which makes every hugetlb user see the warning
once in every boot.)
What I thought when I suggested this code was that __page_cache_release() seems
not to be intended for hugetlb, but I'm not sure.
__put_compound_page() does work without this !PageHuge check which is only for
potential change in __put_compound_page().
So if everyone thinks that __put_compound_page() is stable and will never change
in the future, this !PageHuge check is totally unnecessary.
> Let's not play games in this area. This code has been stable for many
> years, why are we suddenly doing random things here? There's something
> to be said for "if it ain't broke..", and there's *definitely* a lot
> to be said for "let's not complicate this even more".
OK, so could you please try simply reverting 822fc61367f0 ?
Thanks,
Naoya Horiguchi
--
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>
prev parent reply other threads:[~2015-04-20 0:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150418205656.GA7972@pd.tnic>
2015-04-18 21:27 ` Linus Torvalds
2015-04-18 21:56 ` Kirill A. Shutemov
2015-04-18 21:59 ` Linus Torvalds
2015-04-18 22:08 ` Borislav Petkov
2015-04-18 22:16 ` Borislav Petkov
2015-04-22 13:12 ` Borislav Petkov
2015-04-22 18:33 ` Kirill A. Shutemov
2015-04-22 18:40 ` Borislav Petkov
2015-04-22 18:43 ` Kirill A. Shutemov
2015-04-22 19:18 ` Borislav Petkov
2015-04-22 19:26 ` Linus Torvalds
2015-04-23 16:23 ` Andrea Arcangeli
2015-04-24 21:42 ` Kirill A. Shutemov
2015-04-27 16:40 ` Andrea Arcangeli
2015-04-18 22:12 ` Linus Torvalds
2015-04-20 0:02 ` Naoya Horiguchi [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=20150420000200.GC10725@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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