All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm: avoid endless recursion in dump_page()
Date: Thu, 22 Sep 2016 13:26:48 +0200	[thread overview]
Message-ID: <5a28daab-6502-3e14-9e12-cd2b7ccc6a9d@suse.cz> (raw)
In-Reply-To: <20160922105532.GB24593@node>

On 09/22/2016 12:55 PM, Kirill A. Shutemov wrote:
> On Wed, Sep 21, 2016 at 04:27:31PM +0200, Vlastimil Babka wrote:
>> On 09/08/2016 10:21 AM, Kirill A. Shutemov wrote:
>> >dump_page() uses page_mapcount() to get mapcount of the page.
>> >page_mapcount() has VM_BUG_ON_PAGE(PageSlab(page)) as mapcount doesn't
>> >make sense for slab pages and the field in struct page used for other
>> >information.
>> >
>> >It leads to recursion if dump_page() called for slub page and DEBUG_VM
>> >is enabled:
>> >
>> >dump_page() -> page_mapcount() -> VM_BUG_ON_PAGE() -> dump_page -> ...
>> >
>> >Let's avoid calling page_mapcount() for slab pages in dump_page().
>>
>> How about instead splitting page_mapcount() so that there is a version
>> without VM_BUG_ON_PAGE()?
>
> Why? page->_mapping is garbage for slab page and might be confusing.
>
> If you want the information from page->_mapping union for slab page to be
> shown during dump_page() we should present in proper way.

Hmm, fair enough.

>
>> >+	int mapcount = PageSlab(page) ? 0 : page_mapcount(page);
>
> From d550530cc40ca2e9d60c84a893901c2dad6e7767 Mon Sep 17 00:00:00 2001
> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
> Date: Thu, 22 Sep 2016 13:52:40 +0300
> Subject: [PATCH] mm: clarify why we avoid page_mapcount() for slab pages in
>  dump_page()
>
> Let's add comment on why we skip page_mapcount() for sl[aou]b pages.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>

Thanks.

Acked-by: Vlastimil Babka <vbabka@suse.cz>

> ---
>  mm/debug.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/mm/debug.c b/mm/debug.c
> index 74c7cae4f683..9feb699c5d25 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -42,6 +42,11 @@ const struct trace_print_flags vmaflag_names[] = {
>
>  void __dump_page(struct page *page, const char *reason)
>  {
> +	/*
> +	 * Avoid VM_BUG_ON() in page_mapcount().
> +	 * page->_mapcount space in struct page is used by sl[aou]b pages to
> +	 * encode own info.
> +	 */
>  	int mapcount = PageSlab(page) ? 0 : page_mapcount(page);
>
>  	pr_emerg("page:%p count:%d mapcount:%d mapping:%p index:%#lx",
>

--
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>

      reply	other threads:[~2016-09-22 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  8:21 [PATCH] mm: avoid endless recursion in dump_page() Kirill A. Shutemov
2016-09-21 14:27 ` Vlastimil Babka
2016-09-22 10:55   ` Kirill A. Shutemov
2016-09-22 11:26     ` Vlastimil Babka [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=5a28daab-6502-3e14-9e12-cd2b7ccc6a9d@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.