From: Alexander Potapenko <glider@google.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <adech.fo@gmail.com>,
Christoph Lameter <cl@linux.com>,
Dmitriy Vyukov <dvyukov@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v1 1/8] kasan: Change the behavior of kmalloc_large_oob_right test
Date: Mon, 15 Feb 2016 15:05:44 +0100 [thread overview]
Message-ID: <CAG_fn=Uw7PEYADiaYsxQg9-yeHxtu6U82yF0+wVRJu5ZGFN_2w@mail.gmail.com> (raw)
In-Reply-To: <CAG_fn=VN3+otwrjBbut365D=F0YAnow7-OHkNArLAAntBQmYvw@mail.gmail.com>
Turns out I've actually overintellectualized this test.
I've reworked this patch so that kmalloc_pagealloc_oob_right()
allocates a big chunk of memory from the page allocator (and therefore
is enabled only under CONFIG_SLUB).
kmalloc_large_oob_right() now allocates KMALLOC_MAX_CACHE_SIZE - 256
in both SLAB and SLUB modes.
I'll send the updated patch set later today.
On Tue, Feb 2, 2016 at 5:25 PM, Alexander Potapenko <glider@google.com> wrote:
> The intention was to detect the situation in which a new allocator
> appears for which we don't know how it behaves if we allocate more
> than KMALLOC_MAX_CACHE_SIZE.
> I agree this makes little sense and we can just stick to
> CONFIG_SLAB/CONFIG_SLUB cases.
>
> However I think it's better to keep 'size = KMALLOC_MAX_CACHE_SIZE +
> something' to keep this code working in the case the value of
> KMALLOC_MAX_CACHE_SIZE changes.
>
> On Tue, Feb 2, 2016 at 4:29 PM, Andrey Ryabinin <ryabinin.a.a@gmail.com> wrote:
>>
>>
>> On 02/02/2016 08:34 AM, Andrew Morton wrote:
>>> On Wed, 27 Jan 2016 19:25:06 +0100 Alexander Potapenko <glider@google.com> wrote:
>>>
>>>> depending on which allocator (SLAB or SLUB) is being used
>>>>
>>>> ...
>>>>
>>>> --- a/lib/test_kasan.c
>>>> +++ b/lib/test_kasan.c
>>>> @@ -68,7 +68,22 @@ static noinline void __init kmalloc_node_oob_right(void)
>>>> static noinline void __init kmalloc_large_oob_right(void)
>>>> {
>>>> char *ptr;
>>>> - size_t size = KMALLOC_MAX_CACHE_SIZE + 10;
>>>> + size_t size;
>>>> +
>>>> + if (KMALLOC_MAX_CACHE_SIZE == KMALLOC_MAX_SIZE) {
>>>> + /*
>>>> + * We're using the SLAB allocator. Allocate a chunk that fits
>>>> + * into a slab.
>>>> + */
>>>> + size = KMALLOC_MAX_CACHE_SIZE - 256;
>>>> + } else {
>>>> + /*
>>>> + * KMALLOC_MAX_SIZE > KMALLOC_MAX_CACHE_SIZE.
>>>> + * We're using the SLUB allocator. Allocate a chunk that does
>>>> + * not fit into a slab to trigger the page allocator.
>>>> + */
>>>> + size = KMALLOC_MAX_CACHE_SIZE + 10;
>>>> + }
>>>
>>> This seems a weird way of working out whether we're using SLAB or SLUB.
>>>
>>> Can't we use, umm, #ifdef CONFIG_SLAB? If not that then let's cook up
>>> something standardized rather than a weird just-happens-to-work like
>>> this.
>>>
>>
>> Actually it would be simpler to not use KMALLOC_MAX_CACHE_SIZE at all.
>> Simply replace it with 2 or 3 PAGE_SIZEs.
>
>
>
> --
> Alexander Potapenko
> Software Engineer
>
> Google Germany GmbH
> Erika-Mann-Straße, 33
> 80636 München
>
> Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind,
> leiten Sie diese bitte nicht weiter, informieren Sie den
> Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank.
> This e-mail is confidential. If you are not the right addressee please
> do not forward it, please inform the sender, and please erase this
> e-mail including any attachments. Thanks.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind,
leiten Sie diese bitte nicht weiter, informieren Sie den
Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank.
This e-mail is confidential. If you are not the right addressee please
do not forward it, please inform the sender, and please erase this
e-mail including any attachments. Thanks.
--
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 prev parent reply other threads:[~2016-02-15 14:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:25 [PATCH v1 0/8] SLAB support for KASAN Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 1/8] kasan: Change the behavior of kmalloc_large_oob_right test Alexander Potapenko
2016-02-02 5:34 ` Andrew Morton
2016-02-02 15:29 ` Andrey Ryabinin
2016-02-02 16:25 ` Alexander Potapenko
2016-02-15 14:05 ` Alexander Potapenko [this message]
2016-01-27 18:25 ` [PATCH v1 2/8] mm, kasan: SLAB support Alexander Potapenko
2016-01-28 7:44 ` Joonsoo Kim
2016-01-28 12:37 ` Alexander Potapenko
2016-01-28 13:29 ` Alexander Potapenko
2016-02-01 2:15 ` Joonsoo Kim
2016-02-18 12:58 ` Alexander Potapenko
2016-02-19 1:41 ` Joonsoo Kim
2016-02-19 12:57 ` Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 3/8] mm, kasan: Added GFP flags to KASAN API Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 4/8] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections Alexander Potapenko
2016-01-28 14:53 ` Steven Rostedt
2016-01-29 11:33 ` Alexander Potapenko
2016-01-29 11:59 ` Alexander Potapenko
2016-01-29 14:45 ` Steven Rostedt
2016-02-16 15:32 ` Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 5/8] mm, kasan: Stackdepot implementation. Enable stackdepot for SLAB Alexander Potapenko
2016-01-28 7:40 ` Joonsoo Kim
2016-01-28 12:51 ` Alexander Potapenko
2016-01-28 13:27 ` Alexander Potapenko
2016-02-01 2:55 ` Joonsoo Kim
2016-02-16 18:37 ` Alexander Potapenko
2016-02-17 18:29 ` Alexander Potapenko
2016-02-18 8:13 ` Joonsoo Kim
2016-02-18 15:01 ` Alexander Potapenko
2016-02-18 7:58 ` Joonsoo Kim
2016-01-27 18:25 ` [PATCH v1 6/8] kasan: Test fix: Warn if the UAF could not be detected in kmalloc_uaf2 Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 7/8] kasan: Changed kmalloc_large_oob_right, added kmalloc_pagealloc_oob_right Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 8/8] mm: kasan: Initial memory quarantine implementation Alexander Potapenko
2016-02-01 2:47 ` Joonsoo Kim
2016-02-18 14:06 ` Alexander Potapenko
2016-02-19 2:11 ` Joonsoo Kim
2016-02-19 9:19 ` Dmitry Vyukov
2016-02-19 15:43 ` Christoph Lameter
2016-02-23 7:23 ` Joonsoo Kim
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='CAG_fn=Uw7PEYADiaYsxQg9-yeHxtu6U82yF0+wVRJu5ZGFN_2w@mail.gmail.com' \
--to=glider@google.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.org \
--cc=ryabinin.a.a@gmail.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