From mboxrd@z Thu Jan 1 00:00:00 1970 From: keescook@chromium.org (Kees Cook) Date: Mon, 22 May 2017 21:27:57 -0700 Subject: arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit In-Reply-To: References: <20170510.212952.1440495072777358778.davem@davemloft.net> <20170510.215218.2185526627014393313.davem@davemloft.net> <591A07A1.1030006@iogearbox.net> <5922E11C.4070307@iogearbox.net> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, May 22, 2017 at 7:58 PM, Shubham Bansal wrote: > On testing the eBPF JIT with CONFIG_FRAME_POINTER I got the following > crash for non jitted testcase. It's just a softlockup WARN, not a crash, and I think it'd to be expected given the large runtime test_bpf reports: > [ 72.032494] test_bpf: #267 BPF_MAXINSNS: Call heavy transformations > jited:0 1112799 > [ 92.304815] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! > [insmod:104] > ... > [ 93.835343] 1065840 PASS https://www.kernel.org/doc/Documentation/lockup-watchdogs.txt You can raise the softlockup time-out by changing the number of seconds here: /proc/sys/kernel/watchdog_thresh I think the softlockup is counting the entire runtime of the bpf_tests run, so if it takes 30 seconds to run, put at least 15 into /proc/sys/kernel/watchdog_thresh -Kees -- Kees Cook Pixel Security