[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <VI1PR08MB31676B21476225B49EAA8B47832F0@VI1PR08MB3167.eurprd08.prod.outlook.com>
Date: Thu, 11 Apr 2019 11:01:57 +0000
From: Guillaume Gardet <Guillaume.Gardet@....com>
To: Marc Zyngier <Marc.Zyngier@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Matthias Brugger <mbrugger@...e.com>,
Yousaf Kaukab <yousaf.kaukab@...e.com>
Subject: RE: OOPS in nf_getsockopt
> -----Original Message-----
> From: netdev-owner@...r.kernel.org <netdev-owner@...r.kernel.org>
> On Behalf Of Marc Zyngier
> Sent: 11 April 2019 11:02
> To: Guillaume Gardet <Guillaume.Gardet@....com>;
> netdev@...r.kernel.org
> Cc: Matthias Brugger <mbrugger@...e.com>; Yousaf Kaukab
> <yousaf.kaukab@...e.com>
> Subject: Re: OOPS in nf_getsockopt
>
> On 11/04/2019 09:18, Guillaume Gardet wrote:
> > Hi,
> >
> > With kernel 5.0 and 5.1-rc4, we encounter OOPS in nf_getsockopt on
> aarch64 (on Raspberry Pi3 and qemu).
> > This can be triggered with podman or iptables/ip6tables.
> > The easiest way to reproduce is with 'iptables -F output' and it will trigger
> this bug about 50% of the times.
> >
> > It seems to be similar to
> > https://www.spinics.net/lists/netdev/msg520391.html
> >
> > This bug has been reported here:
> > https://bugzilla.suse.com/show_bug.cgi?id=1131864
> > And the decoded trace is available here:
> > https://bugzilla.suse.com/attachment.cgi?id=802527
>
> This isn't a properly decoded trace, as last time I checked the AArch64 ISA
> had nothing to do with x86.
Indeed, here is the right version: https://bugzilla.suse.com/attachment.cgi?id=802632
Guillaume
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.
Powered by blists - more mailing lists