From: Randy Dunlap <rdunlap@infradead.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse problem with Linux kernel v5.5
Date: Thu, 6 Feb 2020 10:25:39 -0800 [thread overview]
Message-ID: <3b68ba4b-f16a-8404-4e07-27788ebbfce3@infradead.org> (raw)
In-Reply-To: <20200206114619.bfszxgs6jmdgroo6@ltop.local>
On 2/6/20 3:46 AM, Luc Van Oostenryck wrote:
> On Thu, Feb 06, 2020 at 07:18:45AM +0000, Linus Torvalds wrote:
>> On Thu, Feb 6, 2020 at 4:49 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> Also, what is errno 137? (0x89)
>>
>> I think that's just "killed by signal 9" (the high bit is "killed by
>> signal", the low bits are the signal number).
oh. thanks.
(seems like I asked about something similar around 15 years ago
but now I don't recall it :)
>> SIGKILL - oom? What does 'dmesg' say? Maybe there's some exponential
>> memory use triggered by something in that bpf_sk_storage file..
All of the oom-killer instances list sphinx-build as running, and I often
have OOM problems using it (make htmldocs), so that may be a factor.
This morning sparse is handling bpf_sk_storage.c OK (no sphinx-build running).
But I can post the dmesg output if you want to see it.
> Hi Randy,
> What config are you using?
I'm using allmodconfig.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-02-06 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 4:49 sparse problem with Linux kernel v5.5 Randy Dunlap
2020-02-06 4:58 ` Randy Dunlap
2020-02-06 7:18 ` Linus Torvalds
2020-02-06 11:46 ` Luc Van Oostenryck
2020-02-06 18:25 ` Randy Dunlap [this message]
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=3b68ba4b-f16a-8404-4e07-27788ebbfce3@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