From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Borislav Petkov <bp@alien8.de>, Hugh Dickins <hughd@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCH 0/2] Reintroduce picky __compound_tail_refcounted()
Date: Tue, 28 Apr 2015 19:24:56 +0300 [thread overview]
Message-ID: <1430238298-80442-1-git-send-email-kirill.shutemov@linux.intel.com> (raw)
Hi Andrew,
My patch 8d63d99a5dfb which was merged during 4.1 merge window caused
regression:
page:ffffea0010a15040 count:0 mapcount:1 mapping: (null) index:0x0
flags: 0x8000000000008014(referenced|dirty|tail)
page dumped because: VM_BUG_ON_PAGE(page_mapcount(page) != 0)
------------[ cut here ]------------
kernel BUG at mm/swap.c:134!
The patch was reverted by Linus.
This VM_BUG_ON_PAGE() is bogus. The first patch explains why the assert is
wrong and removes it. The second re-introduces original patch.
Kirill A. Shutemov (2):
mm: drop bogus VM_BUG_ON_PAGE assert in put_page() codepath
mm: avoid tail page refcounting on non-THP compound pages
include/linux/mm.h | 2 +-
mm/swap.c | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
--
2.1.4
--
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 reply other threads:[~2015-04-28 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 16:24 Kirill A. Shutemov [this message]
2015-04-28 16:24 ` [PATCH 1/2] mm: drop bogus VM_BUG_ON_PAGE assert in put_page() codepath Kirill A. Shutemov
2015-04-28 16:24 ` [PATCH 2/2] mm: avoid tail page refcounting on non-THP compound pages Kirill A. Shutemov
2015-05-05 7:29 ` [PATCH 0/2] Reintroduce picky __compound_tail_refcounted() Kirill A. Shutemov
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=1430238298-80442-1-git-send-email-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).