From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Alexander Potapenko <glider@google.com>,
dvyukov@google.com, kcc@google.com, adech.fo@gmail.com,
cl@linux.com, akpm@linux-foundation.org, rostedt@goodmis.org,
js1304@gmail.com, iamjoonsoo.kim@lge.com,
kuthonuzo.luruo@hpe.com
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] kasan: avoid overflowing quarantine size on low memory systems
Date: Tue, 2 Aug 2016 13:00:03 +0300 [thread overview]
Message-ID: <57A06F23.9080804@virtuozzo.com> (raw)
In-Reply-To: <1470063563-96266-1-git-send-email-glider@google.com>
On 08/01/2016 05:59 PM, Alexander Potapenko wrote:
> If the total amount of memory assigned to quarantine is less than the
> amount of memory assigned to per-cpu quarantines, |new_quarantine_size|
> may overflow. Instead, set it to zero.
>
Just curious, how did find this?
Overflow is possible if system has more than 32 cpus per GB of memory. AFIAK this quite unusual.
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Fixes: 55834c59098d ("mm: kasan: initial memory quarantine
> implementation")
> Signed-off-by: Alexander Potapenko <glider@google.com>
> ---
> mm/kasan/quarantine.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c
> index 65793f1..416d3b0 100644
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -196,7 +196,7 @@ void quarantine_put(struct kasan_free_meta *info, struct kmem_cache *cache)
>
> void quarantine_reduce(void)
> {
> - size_t new_quarantine_size;
> + size_t new_quarantine_size, percpu_quarantines;
> unsigned long flags;
> struct qlist_head to_free = QLIST_INIT;
> size_t size_to_free = 0;
> @@ -214,7 +214,15 @@ void quarantine_reduce(void)
> */
> new_quarantine_size = (READ_ONCE(totalram_pages) << PAGE_SHIFT) /
> QUARANTINE_FRACTION;
> - new_quarantine_size -= QUARANTINE_PERCPU_SIZE * num_online_cpus();
> + percpu_quarantines = QUARANTINE_PERCPU_SIZE * num_online_cpus();
> + if (new_quarantine_size < percpu_quarantines) {
> + WARN_ONCE(1,
> + "Too little memory, disabling global KASAN quarantine.\n",
> + );
Why WARN? I'd suggest pr_warn_once();
> + new_quarantine_size = 0;
> + } else {
> + new_quarantine_size -= percpu_quarantines;
> + }
> WRITE_ONCE(quarantine_size, new_quarantine_size);
>
> last = global_quarantine.head;
>
--
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 <aryabinin@virtuozzo.com>
To: Alexander Potapenko <glider@google.com>, <dvyukov@google.com>,
<kcc@google.com>, <adech.fo@gmail.com>, <cl@linux.com>,
<akpm@linux-foundation.org>, <rostedt@goodmis.org>,
<js1304@gmail.com>, <iamjoonsoo.kim@lge.com>,
<kuthonuzo.luruo@hpe.com>
Cc: <kasan-dev@googlegroups.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [PATCH] kasan: avoid overflowing quarantine size on low memory systems
Date: Tue, 2 Aug 2016 13:00:03 +0300 [thread overview]
Message-ID: <57A06F23.9080804@virtuozzo.com> (raw)
In-Reply-To: <1470063563-96266-1-git-send-email-glider@google.com>
On 08/01/2016 05:59 PM, Alexander Potapenko wrote:
> If the total amount of memory assigned to quarantine is less than the
> amount of memory assigned to per-cpu quarantines, |new_quarantine_size|
> may overflow. Instead, set it to zero.
>
Just curious, how did find this?
Overflow is possible if system has more than 32 cpus per GB of memory. AFIAK this quite unusual.
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Fixes: 55834c59098d ("mm: kasan: initial memory quarantine
> implementation")
> Signed-off-by: Alexander Potapenko <glider@google.com>
> ---
> mm/kasan/quarantine.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c
> index 65793f1..416d3b0 100644
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -196,7 +196,7 @@ void quarantine_put(struct kasan_free_meta *info, struct kmem_cache *cache)
>
> void quarantine_reduce(void)
> {
> - size_t new_quarantine_size;
> + size_t new_quarantine_size, percpu_quarantines;
> unsigned long flags;
> struct qlist_head to_free = QLIST_INIT;
> size_t size_to_free = 0;
> @@ -214,7 +214,15 @@ void quarantine_reduce(void)
> */
> new_quarantine_size = (READ_ONCE(totalram_pages) << PAGE_SHIFT) /
> QUARANTINE_FRACTION;
> - new_quarantine_size -= QUARANTINE_PERCPU_SIZE * num_online_cpus();
> + percpu_quarantines = QUARANTINE_PERCPU_SIZE * num_online_cpus();
> + if (new_quarantine_size < percpu_quarantines) {
> + WARN_ONCE(1,
> + "Too little memory, disabling global KASAN quarantine.\n",
> + );
Why WARN? I'd suggest pr_warn_once();
> + new_quarantine_size = 0;
> + } else {
> + new_quarantine_size -= percpu_quarantines;
> + }
> WRITE_ONCE(quarantine_size, new_quarantine_size);
>
> last = global_quarantine.head;
>
next prev parent reply other threads:[~2016-08-02 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 14:59 [PATCH] kasan: avoid overflowing quarantine size on low memory systems Alexander Potapenko
2016-08-01 14:59 ` Alexander Potapenko
2016-08-01 20:30 ` Andrew Morton
2016-08-01 20:30 ` Andrew Morton
2016-08-02 10:00 ` Andrey Ryabinin [this message]
2016-08-02 10:00 ` Andrey Ryabinin
2016-08-02 10:05 ` Dmitry Vyukov
2016-08-02 10:05 ` Dmitry Vyukov
2016-08-02 10:07 ` Alexander Potapenko
2016-08-02 10:07 ` Alexander Potapenko
2016-08-02 10:15 ` Dmitry Vyukov
2016-08-02 10:15 ` Dmitry Vyukov
2016-08-02 10:23 ` Andrey Ryabinin
2016-08-02 10:23 ` Andrey Ryabinin
2016-08-02 10:27 ` Alexander Potapenko
2016-08-02 10:27 ` Alexander Potapenko
2016-08-02 10:05 ` Alexander Potapenko
2016-08-02 10:05 ` Alexander Potapenko
2016-08-31 2:39 ` amanda4ray
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=57A06F23.9080804@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=kuthonuzo.luruo@hpe.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.