From: Mike Rapoport <rppt@linux.ibm.com>
To: George Kennedy <george.kennedy@oracle.com>
Cc: David Hildenbrand <david@redhat.com>,
Andrey Konovalov <andreyknvl@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Dmitry Vyukov <dvyukov@google.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Will Deacon <will.deacon@arm.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Peter Collingbourne <pcc@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Branislav Rankov <Branislav.Rankov@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Christoph Hellwig <hch@infradead.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Dhaval Giani <dhaval.giani@oracle.com>
Subject: Re: [PATCH] mm, kasan: don't poison boot memory
Date: Thu, 25 Feb 2021 18:07:06 +0200 [thread overview]
Message-ID: <20210225160706.GD1854360@linux.ibm.com> (raw)
In-Reply-To: <bb444ddb-d60d-114f-c2fe-64e5fb34102d@oracle.com>
On Thu, Feb 25, 2021 at 10:22:44AM -0500, George Kennedy wrote:
>
> > > > > On 2/24/2021 5:37 AM, Mike Rapoport wrote:
>
> Applied just your latest patch, but same failure.
>
> I thought there was an earlier comment (which I can't find now) that stated
> that memblock_reserve() wouldn't reserve the page, which is what's needed
> here.
Actually, I think that memblock_reserve() should be just fine, but it seems
I'm missing something in address calculation each time.
What would happen if you stuck
memblock_reserve(0xbe453000, PAGE_SIZE);
say, at the beginning of find_ibft_region()?
> [ 30.308229] iBFT detected..
> [ 30.308796]
> ==================================================================
> [ 30.308890] BUG: KASAN: use-after-free in ibft_init+0x134/0xc33
> [ 30.308890] Read of size 4 at addr ffff8880be453004 by task swapper/0/1
> [ 30.308890]
> [ 30.308890] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.11.0-f9593a0 #12
> [ 30.308890] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> 0.0.0 02/06/2015
> [ 30.308890] Call Trace:
> [ 30.308890] dump_stack+0xdb/0x120
> [ 30.308890] ? ibft_init+0x134/0xc33
> [ 30.308890] print_address_description.constprop.7+0x41/0x60
> [ 30.308890] ? ibft_init+0x134/0xc33
> [ 30.308890] ? ibft_init+0x134/0xc33
> [ 30.308890] kasan_report.cold.10+0x78/0xd1
> [ 30.308890] ? ibft_init+0x134/0xc33
> [ 30.308890] __asan_report_load_n_noabort+0xf/0x20
> [ 30.308890] ibft_init+0x134/0xc33
> [ 30.308890] ? write_comp_data+0x2f/0x90
> [ 30.308890] ? ibft_check_initiator_for+0x159/0x159
> [ 30.308890] ? write_comp_data+0x2f/0x90
> [ 30.308890] ? ibft_check_initiator_for+0x159/0x159
> [ 30.308890] do_one_initcall+0xc4/0x3e0
> [ 30.308890] ? perf_trace_initcall_level+0x3e0/0x3e0
> [ 30.308890] ? unpoison_range+0x14/0x40
> [ 30.308890] ? ____kasan_kmalloc.constprop.5+0x8f/0xc0
> [ 30.308890] ? kernel_init_freeable+0x420/0x652
> [ 30.308890] ? __kasan_kmalloc+0x9/0x10
> [ 30.308890] ? __sanitizer_cov_trace_pc+0x21/0x50
> [ 30.308890] kernel_init_freeable+0x596/0x652
> [ 30.308890] ? console_on_rootfs+0x7d/0x7d
> [ 30.308890] ? __sanitizer_cov_trace_pc+0x21/0x50
> [ 30.308890] ? rest_init+0xf0/0xf0
> [ 30.308890] kernel_init+0x16/0x1d0
> [ 30.308890] ? rest_init+0xf0/0xf0
> [ 30.308890] ret_from_fork+0x22/0x30
> [ 30.308890]
> [ 30.308890] The buggy address belongs to the page:
> [ 30.308890] page:0000000001b7b17c refcount:0 mapcount:0
> mapping:0000000000000000 index:0x1 pfn:0xbe453
> [ 30.308890] flags: 0xfffffc0000000()
> [ 30.308890] raw: 000fffffc0000000 ffffea0002ef9788 ffffea0002f91488
> 0000000000000000
> [ 30.308890] raw: 0000000000000001 0000000000000000 00000000ffffffff
> 0000000000000000
> [ 30.308890] page dumped because: kasan: bad access detected
> [ 30.308890] page_owner tracks the page as freed
> [ 30.308890] page last allocated via order 0, migratetype Movable,
> gfp_mask 0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), pid 204, ts 28121288605
> [ 30.308890] prep_new_page+0xfb/0x140
> [ 30.308890] get_page_from_freelist+0x3503/0x5730
> [ 30.308890] __alloc_pages_nodemask+0x2d8/0x650
> [ 30.308890] alloc_pages_vma+0xe2/0x560
> [ 30.308890] __handle_mm_fault+0x930/0x26c0
> [ 30.308890] handle_mm_fault+0x1f9/0x810
> [ 30.308890] do_user_addr_fault+0x6f7/0xca0
> [ 30.308890] exc_page_fault+0xaf/0x1a0
> [ 30.308890] asm_exc_page_fault+0x1e/0x30
> [ 30.308890] page last free stack trace:
> [ 30.308890] free_pcp_prepare+0x122/0x290
> [ 30.308890] free_unref_page_list+0xe6/0x490
> [ 30.308890] release_pages+0x2ed/0x1270
> [ 30.308890] free_pages_and_swap_cache+0x245/0x2e0
> [ 30.308890] tlb_flush_mmu+0x11e/0x680
> [ 30.308890] tlb_finish_mmu+0xa6/0x3e0
> [ 30.308890] exit_mmap+0x2b3/0x540
> [ 30.308890] mmput+0x11d/0x450
> [ 30.308890] do_exit+0xaa6/0x2d40
> [ 30.308890] do_group_exit+0x128/0x340
> [ 30.308890] __x64_sys_exit_group+0x43/0x50
> [ 30.308890] do_syscall_64+0x37/0x50
> [ 30.308890] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 30.308890]
> [ 30.308890] Memory state around the buggy address:
> [ 30.308890] ffff8880be452f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> [ 30.308890] ffff8880be452f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> [ 30.308890] >ffff8880be453000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> [ 30.308890] ^
> [ 30.308890] ffff8880be453080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> [ 30.308890] ffff8880be453100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> [ 30.308890]
> ==================================================================
>
> George
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-02-25 16:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 20:56 [PATCH] mm, kasan: don't poison boot memory Andrey Konovalov
2021-02-18 8:55 ` David Hildenbrand
2021-02-18 19:40 ` Andrey Konovalov
2021-02-18 19:46 ` David Hildenbrand
2021-02-18 20:26 ` Andrey Konovalov
2021-02-19 0:06 ` George Kennedy
2021-02-19 0:09 ` Andrey Konovalov
2021-02-19 16:45 ` George Kennedy
2021-02-19 23:04 ` George Kennedy
2021-02-22 9:52 ` David Hildenbrand
2021-02-22 15:13 ` George Kennedy
2021-02-22 16:13 ` David Hildenbrand
2021-02-22 16:39 ` David Hildenbrand
2021-02-22 17:40 ` Konrad Rzeszutek Wilk
2021-02-22 18:45 ` Mike Rapoport
2021-02-22 18:42 ` George Kennedy
2021-02-22 21:55 ` Mike Rapoport
[not found] ` <9773282a-2854-25a4-9faa-9da5dd34e371@oracle.com>
2021-02-23 10:33 ` Mike Rapoport
[not found] ` <3ef9892f-d657-207f-d4cf-111f98dcb55c@oracle.com>
2021-02-23 15:47 ` Mike Rapoport
2021-02-23 18:05 ` George Kennedy
2021-02-23 20:09 ` Mike Rapoport
2021-02-23 21:16 ` George Kennedy
2021-02-23 21:32 ` Mike Rapoport
2021-02-23 21:46 ` George Kennedy
2021-02-24 10:37 ` Mike Rapoport
2021-02-24 14:22 ` George Kennedy
2021-02-25 8:53 ` Mike Rapoport
2021-02-25 12:38 ` George Kennedy
2021-02-25 14:57 ` Mike Rapoport
2021-02-25 15:22 ` George Kennedy
2021-02-25 16:06 ` George Kennedy
2021-02-25 16:07 ` Mike Rapoport [this message]
2021-02-25 16:31 ` George Kennedy
2021-02-25 17:23 ` David Hildenbrand
2021-02-25 17:41 ` Mike Rapoport
2021-02-25 17:50 ` Mike Rapoport
2021-02-25 17:33 ` George Kennedy
2021-02-26 1:19 ` George Kennedy
2021-02-26 11:17 ` Mike Rapoport
2021-02-26 16:16 ` George Kennedy
2021-02-28 18:08 ` Mike Rapoport
2021-03-01 14:29 ` George Kennedy
2021-03-02 1:20 ` George Kennedy
2021-03-02 9:57 ` Mike Rapoport
2021-02-23 21:26 ` George Kennedy
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=20210225160706.GD1854360@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=Branislav.Rankov@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=dhaval.giani@oracle.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=george.kennedy@oracle.com \
--cc=glider@google.com \
--cc=hch@infradead.org \
--cc=kasan-dev@googlegroups.com \
--cc=kevin.brodsky@arm.com \
--cc=konrad@darnok.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.com \
/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).