From: Daniel Axtens <dja@axtens.net>
To: Mark Rutland <mark.rutland@arm.com>
Cc: gor@linux.ibm.com, x86@kernel.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
glider@google.com, luto@kernel.org, aryabinin@virtuozzo.com,
linuxppc-dev@lists.ozlabs.org, dvyukov@google.com
Subject: Re: [PATCH v6 1/5] kasan: support backing vmalloc space with real shadow memory
Date: Tue, 03 Sep 2019 00:32:49 +1000 [thread overview]
Message-ID: <87pnkiu5ta.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <20190902132220.GA9922@lakrids.cambridge.arm.com>
Hi Mark,
>> +static int kasan_depopulate_vmalloc_pte(pte_t *ptep, unsigned long addr,
>> + void *unused)
>> +{
>> + unsigned long page;
>> +
>> + page = (unsigned long)__va(pte_pfn(*ptep) << PAGE_SHIFT);
>> +
>> + spin_lock(&init_mm.page_table_lock);
>> +
>> + if (likely(!pte_none(*ptep))) {
>> + pte_clear(&init_mm, addr, ptep);
>> + free_page(page);
>> + }
>> + spin_unlock(&init_mm.page_table_lock);
>> +
>> + return 0;
>> +}
>
> There needs to be TLB maintenance after unmapping the page, but I don't
> see that happening below.
>
> We need that to ensure that errant accesses don't hit the page we're
> freeing and that new mappings at the same VA don't cause a TLB conflict
> or TLB amalgamation issue.
Darn it, I knew there was something I forgot to do! I thought of that
over the weekend, didn't write it down, and then forgot it when I went
to respin the patches. You're totally right.
>
>> +/*
>> + * Release the backing for the vmalloc region [start, end), which
>> + * lies within the free region [free_region_start, free_region_end).
>> + *
>> + * This can be run lazily, long after the region was freed. It runs
>> + * under vmap_area_lock, so it's not safe to interact with the vmalloc/vmap
>> + * infrastructure.
>> + */
>
> IIUC we aim to only free non-shared shadow by aligning the start
> upwards, and aligning the end downwards. I think it would be worth
> mentioning that explicitly in the comment since otherwise it's not
> obvious how we handle races between alloc/free.
>
Oh, I will need to think through that more carefully.
I think the vmap_area_lock protects us against alloc/free races. I think
alignment operates at least somewhat as you've described, and while it
is important for correctness, I'm not sure I'd say it prevented races? I
will double check my understanding of vmap_area_lock, and I agree the
comment needs to be much clearer.
Once again, thanks for your patience and thoughtful review.
Regards,
Daniel
> Thanks,
> Mark.
>
>> +void kasan_release_vmalloc(unsigned long start, unsigned long end,
>> + unsigned long free_region_start,
>> + unsigned long free_region_end)
>> +{
>> + void *shadow_start, *shadow_end;
>> + unsigned long region_start, region_end;
>> +
>> + /* we start with shadow entirely covered by this region */
>> + region_start = ALIGN(start, PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE);
>> + region_end = ALIGN_DOWN(end, PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE);
>> +
>> + /*
>> + * We don't want to extend the region we release to the entire free
>> + * region, as the free region might cover huge chunks of vmalloc space
>> + * where we never allocated anything. We just want to see if we can
>> + * extend the [start, end) range: if start or end fall part way through
>> + * a shadow page, we want to check if we can free that entire page.
>> + */
>> +
>> + free_region_start = ALIGN(free_region_start,
>> + PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE);
>> +
>> + if (start != region_start &&
>> + free_region_start < region_start)
>> + region_start -= PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE;
>> +
>> + free_region_end = ALIGN_DOWN(free_region_end,
>> + PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE);
>> +
>> + if (end != region_end &&
>> + free_region_end > region_end)
>> + region_end += PAGE_SIZE * KASAN_SHADOW_SCALE_SIZE;
>> +
>> + shadow_start = kasan_mem_to_shadow((void *)region_start);
>> + shadow_end = kasan_mem_to_shadow((void *)region_end);
>> +
>> + if (shadow_end > shadow_start)
>> + apply_to_page_range(&init_mm, (unsigned long)shadow_start,
>> + (unsigned long)(shadow_end - shadow_start),
>> + kasan_depopulate_vmalloc_pte, NULL);
>> +}
next prev parent reply other threads:[~2019-09-02 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:20 [PATCH v6 0/5] kasan: support backing vmalloc space with real shadow memory Daniel Axtens
2019-09-02 11:20 ` [PATCH v6 1/5] " Daniel Axtens
2019-09-02 13:22 ` Mark Rutland
2019-09-02 14:32 ` Daniel Axtens [this message]
2019-09-02 14:54 ` Mark Rutland
2019-09-02 11:20 ` [PATCH v6 2/5] kasan: add test for vmalloc Daniel Axtens
2019-09-02 11:20 ` [PATCH v6 3/5] fork: support VMAP_STACK with KASAN_VMALLOC Daniel Axtens
2019-09-02 11:20 ` [PATCH v6 4/5] x86/kasan: support KASAN_VMALLOC Daniel Axtens
2019-09-02 11:20 ` [PATCH v6 5/5] kasan debug: track pages allocated for vmalloc shadow Daniel Axtens
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=87pnkiu5ta.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens.net \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).