linux-kernel - Re: [PATCH v3 01/12] mm: dump_page(): better diagnostics for compound pages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 3 Feb 2020 11:51:11 -0800
From:   John Hubbard <jhubbard@...dia.com>
To:     "Kirill A. Shutemov" <kirill@...temov.name>
CC:     Andrew Morton <akpm@...ux-foundation.org>,
        Al Viro <viro@...iv.linux.org.uk>,
        Christoph Hellwig <hch@...radead.org>,
        Dan Williams <dan.j.williams@...el.com>,
        Dave Chinner <david@...morbit.com>,
        Ira Weiny <ira.weiny@...el.com>, Jan Kara <jack@...e.cz>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Jonathan Corbet <corbet@....net>,
        Jérôme Glisse <jglisse@...hat.com>,
        Michal Hocko <mhocko@...e.com>,
        Mike Kravetz <mike.kravetz@...cle.com>,
        Shuah Khan <shuah@...nel.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        Matthew Wilcox <willy@...radead.org>,
        <linux-doc@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
        <linux-kselftest@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
        <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
        "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH v3 01/12] mm: dump_page(): better diagnostics for compound
 pages

On 2/3/20 5:16 AM, Kirill A. Shutemov wrote:
> On Fri, Jan 31, 2020 at 07:40:18PM -0800, John Hubbard wrote:
>> A compound page collects the refcount in the head page, while leaving
>> the refcount of each tail page at zero. Therefore, when debugging a
>> problem that involves compound pages, it's best to have diagnostics that
>> reflect that situation. However, dump_page() is oblivious to these
>> points.
>>
>> Change dump_page() as follows:
>>
>> 1) For tail pages, print relevant head page information: refcount, in
>>    particular. But only do this if the page is not corrupted so badly
>>    that the pointer to the head page is all wrong.
>>
>> 2) Do a separate check to catch any (rare) cases of the tail page's
>>    refcount being non-zero, and issue a separate, clear pr_warn() if
>>    that ever happens.
>>
>> Suggested-by: Matthew Wilcox <willy@...radead.org>
>> Suggested-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
>> Signed-off-by: John Hubbard <jhubbard@...dia.com>
> 
> Acked-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>

Thanks for looking through all of these!

> 
> Few nit-picks below.
> 
>> ---
>>  mm/debug.c | 34 ++++++++++++++++++++++++++++------
>>  1 file changed, 28 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/debug.c b/mm/debug.c
>> index ecccd9f17801..beb1c59d784b 100644
>> --- a/mm/debug.c
>> +++ b/mm/debug.c
>> @@ -42,6 +42,32 @@ const struct trace_print_flags vmaflag_names[] = {
>>  	{0, NULL}
>>  };
>>  
>> +static void __dump_tail_page(struct page *page, int mapcount)
>> +{
>> +	struct page *head = compound_head(page);
>> +
>> +	if ((page < head) || (page >= head + MAX_ORDER_NR_PAGES)) {
> 
> I'm not sure if we want to use compound_nr() here instead of
> MAX_ORDER_NR_PAGES. Do you have any reasonaing about it?


Yes: compound_nr(page) reads from the struct page, whereas MAX_ORDER_NR_PAGES
is an independent, immutable limit. When checking a struct page for corruption,
it's ideal to avoid relying on data within the struct page, as compound_nr()
would have to do.


> 
>> +		/*
>> +		 * Page is hopelessly corrupted, so limit any reporting to
>> +		 * information about the page itself. Do not attempt to look at
>> +		 * the head page.
>> +		 */
>> +		pr_warn("page:%px refcount:%d mapcount:%d mapping:%px "
>> +			"index:%#lx (corrupted tail page case)\n",
>> +			page, page_ref_count(page), mapcount, page->mapping,
>> +			page_to_pgoff(page));
>> +	} else {
>> +		pr_warn("page:%px compound refcount:%d mapcount:%d mapping:%px "
>> +			"index:%#lx compound_mapcount:%d\n",
>> +			page, page_ref_count(head), mapcount, head->mapping,
>> +			page_to_pgoff(head), compound_mapcount(page));
>> +	}
>> +
>> +	if (page_ref_count(page) != 0)
>> +		pr_warn("page:%px PROBLEM: non-zero refcount (==%d) on this "
>> +			"tail page\n", page, page_ref_count(page));
> 
> Wrap into {}, please.


Fixed, thanks.


thanks,
-- 
John Hubbard
NVIDIA