netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	Marc Haber <mh+netdev@zugschlus.de>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	labbott@redhat.com, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [offlist] Re: Crash in netlink/sk_filter_trim_cap on ARMv7 on 4.18rc1
Date: Fri, 17 Aug 2018 20:30:16 +0200	[thread overview]
Message-ID: <adf49ea9-09a3-80f8-8c85-a62d028e21a3@iogearbox.net> (raw)
In-Reply-To: <20180817161743.GX30658@n2100.armlinux.org.uk>

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.

Thanks,
Daniel

  reply	other threads:[~2018-08-17 21:35 UTC|newest]

Thread overview: 25+ 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 12:55 ` Eric Dumazet
2018-06-24  9:24   ` Peter Robinson
2018-06-25  8:48     ` Daniel Borkmann
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-26 12:23           ` Peter Robinson
2018-06-26 12:52             ` Daniel Borkmann
2018-07-04  7:33               ` Peter Robinson
2018-07-04 23:10                 ` Daniel Borkmann
2018-07-04 23:41                 ` Russell King - ARM Linux
2018-07-05  7:31                   ` Russell King - ARM Linux
2018-07-05  7:46                     ` Daniel Borkmann
2018-08-16 20:35           ` Marc Haber
2018-08-16 22:58             ` Russell King - ARM Linux
2018-08-17 12:25               ` Peter Robinson
2018-08-17 12:40                 ` Daniel Borkmann
2018-08-17 14:32                   ` Peter Robinson
2018-08-17 16:17                   ` Russell King - ARM Linux
2018-08-17 18:30                     ` Daniel Borkmann [this message]
2018-08-17 18:51                       ` Stefan Wahren
2018-08-17 21:15                         ` Peter Robinson
2018-08-17 21:13                       ` Peter Robinson
2018-08-17 22:06                         ` Daniel Borkmann
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=adf49ea9-09a3-80f8-8c85-a62d028e21a3@iogearbox.net \
    --to=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: 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;
as well as URLs for NNTP newsgroup(s).