From: Randy Dunlap <rdunlap@infradead.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: sparse problem with Linux kernel v5.5
Date: Wed, 5 Feb 2020 20:49:20 -0800 [thread overview]
Message-ID: <6ee65b69-9ffc-78c6-66b7-3ce586687d74@infradead.org> (raw)
sparse is v0.6.1.
On kernel v5.5, I can't get past an error on net/core/bpf_sk_storage.c.
Also, what is errno 137? (0x89)
CHECK ../net/core/bpf_sk_storage.c
/bin/sh: line 1: 26442 Killed sparse -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ -Wbitwise -Wno-return-void -Wno-unknown-attribute -D__x86_64__ --arch=x86_64 -mlittle-endian -m64 -Wp,-MD,net/core/.bpf_sk_storage.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/7/include -I../arch/x86/include -I./arch/x86/include/generated -I../include -I./include -I../arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I../include/uapi -I./include/generated/uapi -include ../include/linux/kconfig.h -include ../include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -fno-reorder-blocks -fno-ipa-cp-clone -fno-partial-inlining -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-var-tracking-assignments -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -flive-patching=inline-clone -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fsanitize=kernel-address -fasan-shadow-offset=0xdffffc0000000000 --param asan-globals=1 --param asan-instrumentation-with-call-threshold=0 --param asan-stack=1 -fsanitize-coverage=trace-pc -I ../net/core -I ./net/core -DKBUILD_MODFILE='"net/core/bpf_sk_storage"' -DKBUILD_BASENAME='"bpf_sk_storage"' -DKBUILD_MODNAME='"bpf_sk_storage"' ../net/core/bpf_sk_storage.c
make[3]: *** [../scripts/Makefile.build:268: net/core/bpf_sk_storage.o] Error 137
Yes, pid 26442 (Killed) was sparse.
My laptop has 8GB of RAM (x86_64).
I have hit this error 3x, so I would say that it is easily reproducible (for me).
Any ideas/suggestions?
thanks.
--
~Randy
next reply other threads:[~2020-02-06 4:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 4:49 Randy Dunlap [this message]
2020-02-06 4:58 ` sparse problem with Linux kernel v5.5 Randy Dunlap
2020-02-06 7:18 ` Linus Torvalds
2020-02-06 11:46 ` Luc Van Oostenryck
2020-02-06 18:25 ` Randy Dunlap
2020-02-06 20:06 ` Luc Van Oostenryck
2020-02-06 23:47 ` Linus Torvalds
2020-02-07 0:34 ` Martin KaFai Lau
2020-02-07 10:35 ` Luc Van Oostenryck
2020-02-07 6:34 ` Uwe Kleine-König
2020-02-07 8:29 ` Martin KaFai Lau
2020-02-07 11:34 ` Uwe Kleine-König
2020-02-07 12:43 ` Luc Van Oostenryck
2020-02-07 10:31 ` Luc Van Oostenryck
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=6ee65b69-9ffc-78c6-66b7-3ce586687d74@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=torvalds@linux-foundation.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