From: Meelis Roos <mroos@linux.ee>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Networking <netdev@vger.kernel.org>
Subject: Re: bisected: 4.18-rc* regression: x86-32 troubles (with timers?)
Date: Tue, 24 Jul 2018 09:11:29 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1807240756170.11834@math.ut.ee> (raw)
In-Reply-To: <4a48811d-4094-ee4c-33ca-2cf0446a6313@iogearbox.net>
> >> I would be curious as well about that whether revert would make it
> >> work. What's the value of sysctl net.core.bpf_jit_enable ? Does it
> >> change anything if you set it to 0 (only interpreter) or 1 (JIT
> >> enabled). Seems a bit strange to me that bisect ended at this commit
> >> given the issue you have. The JIT itself was also new in this window
> >> fwiw. In any case some more debug info would be great to have.
> >
> > net.core.bpf_jit_enable is 1.
> >
> > Since it breaks bootup, I can not easily change the value at runtime (it
> > would be postfactum). Do you mean changing the
> > CONFIG_BPF_JIT_ALWAYS_ON=y option?
>
> Yeah if you chance it to N, and don't have any fixed /etc/sysctl.conf
> setting, then you'll boot up with interpreter first (net.core.bpf_jit_enable
> as 0). Curious whether that works just fine for you.
Disabled CONFIG_BPF_JIT_ALWAYS_ON on v4.18-rc5 and it works, tested on 2
bootups.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2018-07-24 6:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 11:41 Meelis Roos
2018-07-04 21:02 ` Arnd Bergmann
2018-07-05 9:54 ` Meelis Roos
2018-07-05 11:04 ` Arnd Bergmann
2018-07-15 15:05 ` Meelis Roos
2018-07-15 20:51 ` Arnd Bergmann
2018-07-16 16:49 ` Meelis Roos
2018-07-16 19:00 ` Meelis Roos
2018-07-20 20:56 ` Meelis Roos
2018-07-20 23:01 ` bisected: " Meelis Roos
2018-07-23 16:03 ` Arnd Bergmann
2018-07-23 19:41 ` Daniel Borkmann
2018-07-23 20:34 ` Meelis Roos
2018-07-23 22:04 ` Daniel Borkmann
2018-07-24 4:47 ` Meelis Roos
2018-07-24 18:40 ` Daniel Borkmann
2018-07-24 6:11 ` Meelis Roos [this message]
2018-07-10 9:30 ` Pavel Machek
2018-07-10 9:32 ` Pavel Machek
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=alpine.LRH.2.21.1807240756170.11834@math.ut.ee \
--to=mroos@linux.ee \
--cc=arnd@arndb.de \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome