From: andre.przywara@arm.com (Andre Przywara)
To: linux-arm-kernel@lists.infradead.org
Subject: BPF crash with 3.18-rc1 on arm64 Juno hardware
Date: Fri, 24 Oct 2014 11:34:51 +0100 [thread overview]
Message-ID: <544A2B4B.3050207@arm.com> (raw)
In-Reply-To: <20141024103158.GB1955@localhost>
Hi,
On 24/10/14 11:31, Catalin Marinas wrote:
> On Thu, Oct 23, 2014 at 06:23:49PM +0100, Z Lim wrote:
>> On Thu, Oct 23, 2014 at 10:00 AM, Andre Przywara <andre.przywara@arm.com> wrote:
>>> I see a crash with 3.18-rc1 on a Juno board related to bpf_jit (see dump
>>> below). Userland tries to carry on afterwards, but eventually hangs in
>>> RCU stalls.
>>> The kernel has just CONFIG_BPF_JIT enabled, I guess Ubuntu enables this
>>> automatically if detected.
>>
>> When net-next and arm64-next merged in mainline, a silent failure is
>> introduced due to new enhancements in net/bpf.
>> This was actually uncovered before 3.18 merge window, and Daniel's
>> patch to fix this was discussed here [1].
>> I see that Catalin has queued up this patch in fixes/core [2].
>
> Indeed. Pull request to Linus will go out later today.
Indeed this patch fixes it for me.
Thanks to both of you!
Cheers,
Andre.
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
prev parent reply other threads:[~2014-10-24 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 17:00 BPF crash with 3.18-rc1 on arm64 Juno hardware Andre Przywara
2014-10-23 17:23 ` Z Lim
2014-10-24 10:31 ` Catalin Marinas
2014-10-24 10:34 ` Andre Przywara [this message]
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=544A2B4B.3050207@arm.com \
--to=andre.przywara@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).