All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Pelletier <plr.vincent@gmail.com>
To: target-devel@vger.kernel.org
Subject: Re: BUG in slab_free after iSCSI login timeout
Date: Sun, 12 Aug 2018 04:01:26 +0000	[thread overview]
Message-ID: <20180812040126.6f54f705@gmail.com> (raw)
In-Reply-To: <20180811093655.42922d8e@gmail.com>

On Sun, 12 Aug 2018 03:51:40 +0000, Vincent Pelletier
<plr.vincent@gmail.com> wrote:
>   This said, I was surprised by "free" output listing only a bit
>   above 3GB of ram total:
>   $ free -m
>                 total        used        free      shared  buff/cache   available
>   Mem:           3310         250        2867           5         192        2847
>   Swap:          5015           0        5015
>   Would it be an effect of KASAN ?
>   I also found the following line in dmesg:
>   [    0.000000] Memory: 3099784K/4088348K available (14348K kernel code, 4532K rwdata, 5400K rodata, 1840K init, 9112K bss, 988564K reserved, 0K cma-reserved)
>   Checking pre-KASAN boots it was:
>   [    0.000000] Memory: 3657884K/4088348K available (10252K kernel code, 1210K rwdata, 3216K rodata, 1548K init, 656K bss, 430464K reserved, 0K cma-reserved)

Answering my own question after a bit of RTFM: KASAN uses 1 byte to
track 8 bytes, so monitoring 4GB takes 512MB, so it indeed explains the
vast majority of the difference in reserved memory.
-- 
Vincent Pelletier

  parent reply	other threads:[~2018-08-12  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11  9:36 BUG in slab_free after iSCSI login timeout Vincent Pelletier
2018-08-11 22:50 ` Bart Van Assche
2018-08-12  2:55 ` Vincent Pelletier
2018-08-12  3:51 ` Vincent Pelletier
2018-08-12  4:01 ` Vincent Pelletier [this message]
2018-08-13 19:48 ` Mike Christie
2018-08-13 21:42 ` Mike Christie
2018-08-13 22:54 ` Mike Christie

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=20180812040126.6f54f705@gmail.com \
    --to=plr.vincent@gmail.com \
    --cc=target-devel@vger.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 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.