> After running for about 24 hours, I now encountered another panic. This time
> it
> is caused by an out of memory situation. Although the trace shows action in
> the
> filesystem code I'm posting it here because I cannot isolate the error and
> maybe it is caused by our NULL pointer bug or by t
On Wed, Sep 12, 2018 at 10:50:46AM +0200, Steffen Klassert wrote:
> On Tue, Sep 11, 2018 at 09:02:48PM +0200, Tobias Hommel wrote:
> > > > Subject: [PATCH RFC] xfrm: Fix NULL pointer dereference when
> > > > skb_dst_force
> > > > clears the dst_entry.
>
e xfrm code don't expect this to happen, so we crash with
> > a NULL pointer dereference in this case. Fix it by checking
> > skb_dst(skb) for NULL after skb_dst_force() and drop the packet
> > in cast the dst_entry was cleared.
> >
> > Fixes: 222d7dbd258d (&q
On Mon, Sep 10, 2018 at 08:37:39AM +0200, Steffen Klassert wrote:
...
> The other thing I wonder about is why Tobias bisected this to
>
> commit b838d5e1c5b6e57b10ec8af2268824041e3ea911
> ipv4: mark DST_NOGC and remove the operation of dst_free()
>
> from 'Jun 17 2017' and not to
>
> commit 222d
Hey guys,
I finally got some time to do a bisect and we narrowed the problem down to:
b838d5e1c5b6e57b10ec8af2268824041e3ea911 is the first bad commit
commit b838d5e1c5b6e57b10ec8af2268824041e3ea911
Author: Wei Wang
Date: Sat Jun 17 10:42:32 2017 -0700
ipv4: mark DST_NOGC and remove the o
On Fri, Jun 08, 2018 at 10:41:37AM +0200, Kristian Evensen wrote:
> Hi,
>
> On Wed, Jun 6, 2018 at 6:03 PM, Tobias Hommel
> wrote:
> > Sorry no progress until now, I currently do not get time to have a deeper
> > look
> > into that. We're back to 4.1.6 ri
Hi,
On Wed, Jun 06, 2018 at 12:41:53PM +0200, Kristian Evensen wrote:
> Hi,
>
> I am experiencing the same issue on a PC Engines APU2 running kernel
> 4.14.34, both with and without hardware encryption. With hw.
> encryption, the crash occurs within 2-4 hours. Without hw. encryption,
> it takes 7
On Wed, Jan 24, 2018 at 10:59:21AM +0100, Steffen Klassert wrote:
> On Fri, Jan 19, 2018 at 03:45:46PM +0100, Tobias Hommel wrote:
> >
> > I tried to strip down the system configuration and was able to reproduce the
> > problem with a minimal configuration:
> > *
On Wed, Jan 10, 2018 at 08:30:38AM +0100, Steffen Klassert wrote:
> On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote:
> >
> > I copied the config from my 4.14.12 sources to a fresh 4.13.16 source tree,
> > ran
> > `make olddefconfig` and built a new kerne
On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote:
> On Tue, Jan 09, 2018 at 10:26:24AM +0100, Steffen Klassert wrote:
> > On Tue, Jan 09, 2018 at 10:06:51AM +0100, Tobias Hommel wrote:
> > > >
> > > > You have CONFIG_INET_ESP_OFFLOAD enabled, this
On Tue, Jan 09, 2018 at 09:19:39AM +0100, Steffen Klassert wrote:
> On Mon, Jan 08, 2018 at 02:53:48PM +0100, Tobias Hommel wrote:
>
> ...
>
> > [ 439.095554] BUG: unable to handle kernel NULL pointer dereference at
> > 0020
> > [ 439.1036
On Fri, Jan 05, 2018 at 09:55:23PM +, Tobias Hommel wrote:
> On Sat, Jan 06, 2018 at 12:27:11AM +0300, Ozgur wrote:
> >
> >
> > 06.01.2018, 00:20, "Tobias Hommel" :
> > > Hi,
> >
> > Hi Tobias,
> >
> > > I'm running i
On Fri, Jan 05, 2018 at 09:51:16PM +, Holger Hoffstätte wrote:
> On Fri, 05 Jan 2018 22:13:23 +0100, Tobias Hommel wrote:
>
> > Hi,
> >
> > I'm running into a NULL pointer dereference after updating from Linux 4.1.6
> > to
> > 4.14.11 (see kernel l
On Sat, Jan 06, 2018 at 12:27:11AM +0300, Ozgur wrote:
>
>
> 06.01.2018, 00:20, "Tobias Hommel" :
> > Hi,
>
> Hi Tobias,
>
> > I'm running into a NULL pointer dereference after updating from Linux 4.1.6
> > to
> > 4.14.11 (see kerne
701479] CR2: 0020
[ 7998.704799] ---[ end trace 0544b1946919baad ]---
[ 7998.709442] Kernel panic - not syncing: Fatal exception in interrupt
[ 7998.715918] Kernel Offset: 0x1100 from 0x8100 (relocation
range: 0x8000-0xbfff)
Best regards,
Tobias Hommel
15 matches
Mail list logo
