From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Vyukov <dvyukov@google.com>, Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Hailong Liu <liu.hailong6@zte.com.cn>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Arm + KASAN + syzbot
Date: Thu, 11 Mar 2021 14:09:04 +0000 [thread overview]
Message-ID: <20210311140904.GJ1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkda1pJpMif6Xt2JHseYQP6NWDmwwgm9pVCPnSAoeARTT9Q@mail.gmail.com>
On Thu, Mar 11, 2021 at 02:55:54PM +0100, Linus Walleij wrote:
> On Thu, Mar 11, 2021 at 11:54 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> > The instance has KASAN disabled because Go binaries don't run on KASAN kernel:
> > https://lore.kernel.org/linux-arm-kernel/CACT4Y+YdJoNTqnBSELcEbcbVsKBtJfYUc7_GSXbUQfAJN3JyRg@mail.gmail.com/
>
> I am still puzzled by this, but I still have the open question about how much
> memory the Go runtime really use. I am suspecting quite a lot, and the
> ARM32 instance isn't on par with any contemporary server or desktop
> when it comes to memory, it has ~2GB for a userspace program, after
> that bad things will happen: the machine will start thrashing.
I believe grafana is a Go binary - I run this in a VM with only 1G
of memory and no swap along with apache. It's happy enough.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
grafana 1122 0.0 5.9 920344 60484 ? Ssl Feb18 28:31 /usr/sbin/grafana-server --config=/etc/grafana/grafana.ini ...
So, I suspect it's basically KASAN upsetting Go somehow that then
causes the memory usage to spiral out of control.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-11 14:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 16:31 Arm + KASAN + syzbot Dmitry Vyukov
2021-01-19 8:36 ` Krzysztof Kozlowski
2021-01-19 8:46 ` Linus Walleij
2021-01-19 10:04 ` Dmitry Vyukov
2021-01-19 10:17 ` Linus Walleij
2021-01-19 10:23 ` Dmitry Vyukov
2021-01-19 10:28 ` Linus Walleij
2021-01-19 10:53 ` Dmitry Vyukov
2021-01-19 11:05 ` Dmitry Vyukov
2021-01-19 11:13 ` Russell King - ARM Linux admin
2021-01-19 11:17 ` Dmitry Vyukov
2021-01-19 11:43 ` Russell King - ARM Linux admin
2021-01-19 12:05 ` Dmitry Vyukov
2021-01-19 12:36 ` Russell King - ARM Linux admin
2021-01-19 18:57 ` Dmitry Vyukov
2021-01-19 19:48 ` Russell King - ARM Linux admin
2021-01-21 13:14 ` Russell King - ARM Linux admin
2021-01-21 13:49 ` Dmitry Vyukov
2021-01-21 14:04 ` Arnd Bergmann
2021-01-21 13:59 ` Dmitry Vyukov
2021-01-21 14:52 ` Linus Walleij
2021-01-26 21:24 ` Dmitry Vyukov
2021-01-27 8:24 ` Linus Walleij
2021-01-27 9:39 ` Dmitry Vyukov
2021-01-27 9:57 ` Linus Walleij
2021-01-27 10:12 ` Dmitry Vyukov
2021-01-27 10:19 ` Russell King - ARM Linux admin
2021-03-11 10:54 ` Dmitry Vyukov
2021-03-11 13:42 ` Russell King - ARM Linux admin
2021-03-11 18:05 ` Dmitry Vyukov
2021-03-11 13:55 ` Linus Walleij
2021-03-11 14:09 ` Russell King - ARM Linux admin [this message]
2021-03-11 14:37 ` Linus Walleij
2021-03-11 14:55 ` Arnd Bergmann
2021-03-11 18:08 ` Dmitry Vyukov
2021-03-15 14:01 ` Linus Walleij
2021-03-15 19:03 ` Russell King - ARM Linux admin
2021-01-19 13:22 ` Linus Walleij
2021-01-19 8:41 ` Linus Walleij
2021-01-19 8:43 ` Linus Walleij
2021-01-19 10:18 ` Dmitry Vyukov
2021-01-19 10:27 ` Linus Walleij
2021-01-19 10:36 ` Dmitry Vyukov
2021-01-19 10:03 ` Mark Rutland
2021-01-19 10:34 ` Dmitry Vyukov
2021-01-19 10:55 ` Russell King - ARM Linux admin
2021-01-19 13:00 ` Mark Rutland
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=20210311140904.GJ1463@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liu.hailong6@zte.com.cn \
--cc=syzkaller@googlegroups.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 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.