All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Alexander Potapenko <glider@google.com>
Cc: adech.fo@gmail.com, cl@linux.com, dvyukov@google.com,
	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: Tue, 2 Feb 2016 18:29:36 +0300	[thread overview]
Message-ID: <56B0CB60.1080506@gmail.com> (raw)
In-Reply-To: <20160201213427.f428b08d.akpm@linux-foundation.org>



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.

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

WARNING: multiple messages have this Message-ID (diff)
From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Alexander Potapenko <glider@google.com>
Cc: adech.fo@gmail.com, cl@linux.com, dvyukov@google.com,
	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: Tue, 2 Feb 2016 18:29:36 +0300	[thread overview]
Message-ID: <56B0CB60.1080506@gmail.com> (raw)
In-Reply-To: <20160201213427.f428b08d.akpm@linux-foundation.org>



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.

  reply	other threads:[~2016-02-02 15:28 UTC|newest]

Thread overview: 78+ 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 ` Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 1/8] kasan: Change the behavior of kmalloc_large_oob_right test Alexander Potapenko
2016-01-27 18:25   ` Alexander Potapenko
2016-02-02  5:34   ` Andrew Morton
2016-02-02  5:34     ` Andrew Morton
2016-02-02 15:29     ` Andrey Ryabinin [this message]
2016-02-02 15:29       ` Andrey Ryabinin
2016-02-02 16:25       ` Alexander Potapenko
2016-02-02 16:25         ` Alexander Potapenko
2016-02-15 14:05         ` Alexander Potapenko
2016-02-15 14:05           ` Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 2/8] mm, kasan: SLAB support Alexander Potapenko
2016-01-27 18:25   ` Alexander Potapenko
2016-01-28  7:44   ` Joonsoo Kim
2016-01-28  7:44     ` Joonsoo Kim
2016-01-28 12:37     ` Alexander Potapenko
2016-01-28 13:29       ` Alexander Potapenko
2016-01-28 13:29         ` Alexander Potapenko
2016-02-01  2:15         ` Joonsoo Kim
2016-02-01  2:15           ` Joonsoo Kim
2016-02-18 12:58           ` Alexander Potapenko
2016-02-18 12:58             ` Alexander Potapenko
2016-02-19  1:41             ` Joonsoo Kim
2016-02-19  1:41               ` Joonsoo Kim
2016-02-19 12:57               ` Alexander Potapenko
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   ` 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-27 18:25   ` Alexander Potapenko
2016-01-28 14:53   ` Steven Rostedt
2016-01-28 14:53     ` Steven Rostedt
2016-01-29 11:33     ` Alexander Potapenko
2016-01-29 11:33       ` Alexander Potapenko
2016-01-29 11:59       ` Alexander Potapenko
2016-01-29 11:59         ` Alexander Potapenko
2016-01-29 14:45         ` Steven Rostedt
2016-01-29 14:45           ` Steven Rostedt
2016-02-16 15:32           ` Alexander Potapenko
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-27 18:25   ` Alexander Potapenko
2016-01-28  7:40   ` Joonsoo Kim
2016-01-28  7:40     ` Joonsoo Kim
2016-01-28 12:51     ` Alexander Potapenko
2016-01-28 13:27       ` Alexander Potapenko
2016-01-28 13:27         ` Alexander Potapenko
2016-02-01  2:55         ` Joonsoo Kim
2016-02-01  2:55           ` Joonsoo Kim
2016-02-16 18:37           ` Alexander Potapenko
2016-02-16 18:37             ` Alexander Potapenko
2016-02-17 18:29             ` Alexander Potapenko
2016-02-17 18:29               ` Alexander Potapenko
2016-02-18  8:13               ` Joonsoo Kim
2016-02-18  8:13                 ` Joonsoo Kim
2016-02-18 15:01                 ` Alexander Potapenko
2016-02-18 15:01                   ` Alexander Potapenko
2016-02-18  7:58             ` Joonsoo Kim
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   ` 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   ` Alexander Potapenko
2016-01-27 18:25 ` [PATCH v1 8/8] mm: kasan: Initial memory quarantine implementation Alexander Potapenko
2016-01-27 18:25   ` Alexander Potapenko
2016-02-01  2:47   ` Joonsoo Kim
2016-02-01  2:47     ` Joonsoo Kim
2016-02-18 14:06     ` Alexander Potapenko
2016-02-18 14:06       ` Alexander Potapenko
2016-02-19  2:11       ` Joonsoo Kim
2016-02-19  2:11         ` Joonsoo Kim
2016-02-19  9:19         ` Dmitry Vyukov
2016-02-19  9:19           ` Dmitry Vyukov
2016-02-19 15:43           ` Christoph Lameter
2016-02-19 15:43             ` Christoph Lameter
2016-02-23  7:23           ` Joonsoo Kim
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=56B0CB60.1080506@gmail.com \
    --to=ryabinin.a.a@gmail.com \
    --cc=adech.fo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rostedt@goodmis.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.