From: Stefan Wahren <stefan.wahren@i2se.com> To: Daniel Borkmann <daniel@iogearbox.net> Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org, Marc Haber <mh+netdev@zugschlus.de>, Russell King - ARM Linux <linux@armlinux.org.uk>, Peter Robinson <pbrobinson@gmail.com>, labbott@redhat.com, linux-arm-kernel@lists.infradead.org Subject: Re: [offlist] Re: Crash in netlink/sk_filter_trim_cap on ARMv7 on 4.18rc1 Date: Fri, 17 Aug 2018 20:51:29 +0200 (CEST) [thread overview] Message-ID: <1425110527.374417.1534531889127@email.1und1.de> (raw) In-Reply-To: <adf49ea9-09a3-80f8-8c85-a62d028e21a3@iogearbox.net> Hi Daniel, > Daniel Borkmann <daniel@iogearbox.net> hat am 17. August 2018 um 20:30 geschrieben: > > > On 08/17/2018 06:17 PM, Russell King - ARM Linux wrote: > > On Fri, Aug 17, 2018 at 02:40:19PM +0200, Daniel Borkmann wrote: > >> I'd have one potential bug suspicion, for the 4.18 one you were trying, > >> could you run with the below patch to see whether it would help? > > > > I think this is almost certainly the problem - looking at the history, > > it seems that the "-4" was assumed to be part of the scratch stuff in > > commit 38ca93060163 ("bpf, arm32: save 4 bytes of unneeded stack space") > > but it isn't - it's because "off" of zero refers to the top word in the > > stack (iow at STACK_SIZE-4). > > Yeah agree, my thinking as well (albeit bit late, sigh, sorry about that). > Waiting for Peter to get back with results for definite confirmation. Your > rework in 1c35ba122d4a ("ARM: net: bpf: use negative numbers for stacked > registers") and 96cced4e774a ("ARM: net: bpf: access eBPF scratch space using > ARM FP register") fixes this in mainline, so unless I'm missing something this > would only need a stand-alone fix for 4.18/stable which I can cook up and > submit then. i was able to reproduce this issue on RPi 3 with Linux 4.18.1 + multi_v7_defconfig and the following config changes: --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -2,7 +2,10 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_CGROUPS=y +CONFIG_CGROUP_BPF=y CONFIG_BLK_DEV_INITRD=y +CONFIG_BPF_SYSCALL=y +CONFIG_BPF_JIT_ALWAYS_ON=y CONFIG_EMBEDDED=y CONFIG_PERF_EVENTS=y CONFIG_MODULES=y @@ -153,6 +156,8 @@ CONFIG_IPV6_MIP6=m CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_NET_DSA=m +CONFIG_BPF_JIT=y +CONFIG_BPF_STREAM_PARSER=y CONFIG_CAN=y CONFIG_CAN_AT91=m CONFIG_CAN_FLEXCAN=m After applying the "-4" patch the oopses doesn't appear during boot anymore. Stefan > > Thanks, > Daniel > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: stefan.wahren@i2se.com (Stefan Wahren) To: linux-arm-kernel@lists.infradead.org Subject: [offlist] Re: Crash in netlink/sk_filter_trim_cap on ARMv7 on 4.18rc1 Date: Fri, 17 Aug 2018 20:51:29 +0200 (CEST) [thread overview] Message-ID: <1425110527.374417.1534531889127@email.1und1.de> (raw) In-Reply-To: <adf49ea9-09a3-80f8-8c85-a62d028e21a3@iogearbox.net> Hi Daniel, > Daniel Borkmann <daniel@iogearbox.net> hat am 17. August 2018 um 20:30 geschrieben: > > > On 08/17/2018 06:17 PM, Russell King - ARM Linux wrote: > > On Fri, Aug 17, 2018 at 02:40:19PM +0200, Daniel Borkmann wrote: > >> I'd have one potential bug suspicion, for the 4.18 one you were trying, > >> could you run with the below patch to see whether it would help? > > > > I think this is almost certainly the problem - looking at the history, > > it seems that the "-4" was assumed to be part of the scratch stuff in > > commit 38ca93060163 ("bpf, arm32: save 4 bytes of unneeded stack space") > > but it isn't - it's because "off" of zero refers to the top word in the > > stack (iow at STACK_SIZE-4). > > Yeah agree, my thinking as well (albeit bit late, sigh, sorry about that). > Waiting for Peter to get back with results for definite confirmation. Your > rework in 1c35ba122d4a ("ARM: net: bpf: use negative numbers for stacked > registers") and 96cced4e774a ("ARM: net: bpf: access eBPF scratch space using > ARM FP register") fixes this in mainline, so unless I'm missing something this > would only need a stand-alone fix for 4.18/stable which I can cook up and > submit then. i was able to reproduce this issue on RPi 3 with Linux 4.18.1 + multi_v7_defconfig and the following config changes: --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -2,7 +2,10 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_CGROUPS=y +CONFIG_CGROUP_BPF=y CONFIG_BLK_DEV_INITRD=y +CONFIG_BPF_SYSCALL=y +CONFIG_BPF_JIT_ALWAYS_ON=y CONFIG_EMBEDDED=y CONFIG_PERF_EVENTS=y CONFIG_MODULES=y @@ -153,6 +156,8 @@ CONFIG_IPV6_MIP6=m CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_NET_DSA=m +CONFIG_BPF_JIT=y +CONFIG_BPF_STREAM_PARSER=y CONFIG_CAN=y CONFIG_CAN_AT91=m CONFIG_CAN_FLEXCAN=m After applying the "-4" patch the oopses doesn't appear during boot anymore. Stefan > > Thanks, > Daniel > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-08-17 18:51 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-22 11:19 Crash in netlink/sk_filter_trim_cap on ARMv7 on 4.18rc1 Peter Robinson 2018-06-22 11:19 ` Peter Robinson 2018-06-22 12:55 ` Eric Dumazet 2018-06-22 12:55 ` Eric Dumazet 2018-06-24 9:24 ` Peter Robinson 2018-06-24 9:24 ` Peter Robinson 2018-06-25 8:48 ` Daniel Borkmann 2018-06-25 8:48 ` Daniel Borkmann 2018-06-25 12:03 ` Peter Robinson 2018-06-25 12:03 ` Peter Robinson [not found] ` <ad98d60c-bd60-b495-c4bd-507fc29c8bcd@iogearbox.net> [not found] ` <CALeDE9PBZWJBp8KB0mB4zoNXqscmzxWzz+LnuqRA-z4t1e9T8g@mail.gmail.com> 2018-06-25 16:41 ` [offlist] " Peter Robinson 2018-06-25 16:41 ` Peter Robinson 2018-06-26 12:23 ` Peter Robinson 2018-06-26 12:23 ` Peter Robinson 2018-06-26 12:52 ` Daniel Borkmann 2018-06-26 12:52 ` Daniel Borkmann 2018-07-04 7:33 ` Peter Robinson 2018-07-04 7:33 ` Peter Robinson 2018-07-04 23:10 ` Daniel Borkmann 2018-07-04 23:10 ` Daniel Borkmann 2018-07-04 23:41 ` Russell King - ARM Linux 2018-07-04 23:41 ` Russell King - ARM Linux 2018-07-05 7:31 ` Russell King - ARM Linux 2018-07-05 7:31 ` Russell King - ARM Linux 2018-07-05 7:46 ` Daniel Borkmann 2018-07-05 7:46 ` Daniel Borkmann 2018-08-16 20:35 ` Marc Haber 2018-08-16 20:35 ` Marc Haber 2018-08-16 22:58 ` Russell King - ARM Linux 2018-08-16 22:58 ` Russell King - ARM Linux 2018-08-17 12:25 ` Peter Robinson 2018-08-17 12:25 ` Peter Robinson 2018-08-17 12:40 ` Daniel Borkmann 2018-08-17 12:40 ` Daniel Borkmann 2018-08-17 14:32 ` Peter Robinson 2018-08-17 14:32 ` Peter Robinson 2018-08-17 16:17 ` Russell King - ARM Linux 2018-08-17 16:17 ` Russell King - ARM Linux 2018-08-17 18:30 ` Daniel Borkmann 2018-08-17 18:30 ` Daniel Borkmann 2018-08-17 18:51 ` Stefan Wahren [this message] 2018-08-17 18:51 ` Stefan Wahren 2018-08-17 21:15 ` Peter Robinson 2018-08-17 21:15 ` Peter Robinson 2018-08-17 21:13 ` Peter Robinson 2018-08-17 21:13 ` Peter Robinson 2018-08-17 22:06 ` Daniel Borkmann 2018-08-17 22:06 ` Daniel Borkmann 2018-08-17 21:12 ` Peter Robinson 2018-08-17 21:12 ` Peter Robinson
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=1425110527.374417.1534531889127@email.1und1.de \ --to=stefan.wahren@i2se.com \ --cc=daniel@iogearbox.net \ --cc=eric.dumazet@gmail.com \ --cc=labbott@redhat.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux@armlinux.org.uk \ --cc=mh+netdev@zugschlus.de \ --cc=netdev@vger.kernel.org \ --cc=pbrobinson@gmail.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: linkBe 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.