linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: [bug report] mm, slab/slub: introduce kmalloc-reclaimable caches
Date: Fri, 9 Nov 2018 18:28:44 +0100	[thread overview]
Message-ID: <a6c8eeff-801c-3773-6b96-533f519ef9f4@suse.cz> (raw)
In-Reply-To: <20181109171701.GB8323@unbuntlaptop>

On 11/9/18 6:17 PM, Dan Carpenter wrote:
> Hello Vlastimil Babka,

Hi,

> The patch 1291523f2c1d: "mm, slab/slub: introduce kmalloc-reclaimable
> caches" from Oct 26, 2018, leads to the following static checker
> warning:
> 
> 	./include/linux/slab.h:585 kmalloc_node()
> 	warn: array off by one? 'kmalloc_caches[kmalloc_type(flags)]' '0-3 == 3'

I believe that's a false positive.

> ./include/linux/slab.h
>    298  /*
>    299   * Whenever changing this, take care of that kmalloc_type() and
>    300   * create_kmalloc_caches() still work as intended.
>    301   */
>    302  enum kmalloc_cache_type {
>    303          KMALLOC_NORMAL = 0,
>    304          KMALLOC_RECLAIM,
>    305  #ifdef CONFIG_ZONE_DMA
>    306          KMALLOC_DMA,
>    307  #endif
>    308          NR_KMALLOC_TYPES
> 
> 
> The kmalloc_caches[] array has NR_KMALLOC_TYPES elements.

Yes.

>    309  };
>    310  
>    311  #ifndef CONFIG_SLOB
>    312  extern struct kmem_cache *
>    313  kmalloc_caches[NR_KMALLOC_TYPES][KMALLOC_SHIFT_HIGH + 1];
>    314  
>    315  static __always_inline enum kmalloc_cache_type kmalloc_type(gfp_t flags)
>    316  {
>    317          int is_dma = 0;
>    318          int type_dma = 0;
>    319          int is_reclaimable;
>    320  
>    321  #ifdef CONFIG_ZONE_DMA
>    322          is_dma = !!(flags & __GFP_DMA);
>    323          type_dma = is_dma * KMALLOC_DMA;
>                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> KMALLOC_DMA is the last possible valid index.

Yes, but type_dma gains the value of KMALLOC_DMA only when is_dma is 1.

>    324  #endif
>    325  
>    326          is_reclaimable = !!(flags & __GFP_RECLAIMABLE);
>    327  
>    328          /*
>    329           * If an allocation is both __GFP_DMA and __GFP_RECLAIMABLE, return
>    330           * KMALLOC_DMA and effectively ignore __GFP_RECLAIMABLE
>    331           */
>    332          return type_dma + (is_reclaimable & !is_dma) * KMALLOC_RECLAIM;
>                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> We're adding one to it.

Only when !is_dma is 1, which means then that type_dma is 0. So it's safe.

> This is mm/ so I assume this works,

I'll... take that as a compliment :D

> but it's
> pretty confusing.

Indeed. Static checkers seem to hate my too clever code, so it's already
going away [1]. Maybe your static checker can be improved to evaluate
this better? There's already a gcc bug [2] inspired by the whole thing.

Thanks!
Vlastimil

[1]
https://lore.kernel.org/lkml/cbc1fc52-dc8c-aa38-8f29-22da8bcd91c1@suse.cz/T/#u
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87954

>    333  }
> 
> regards,
> dan carpenter
> 

  reply	other threads:[~2018-11-09 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 17:17 Dan Carpenter
2018-11-09 17:28 ` Vlastimil Babka [this message]
2018-11-13 17:02   ` Dan Carpenter

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=a6c8eeff-801c-3773-6b96-533f519ef9f4@suse.cz \
    --to=vbabka@suse.cz \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-mm@kvack.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