public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+e6e1fe9148cffa18cf97@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in __xfrm_policy_bysel_ctx
Date: Tue, 29 Jan 2019 10:41:44 +0100	[thread overview]
Message-ID: <20190129094144.bln4dnirr5kz3dl4@breakpoint.cc> (raw)
In-Reply-To: <0000000000007b129305809553da@google.com>

syzbot <syzbot+e6e1fe9148cffa18cf97@syzkaller.appspotmail.com> wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    085c4c7dd2b6 net: lmc: remove -I. header search path
> git tree:       net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12347128c00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
> dashboard link: https://syzkaller.appspot.com/bug?extid=e6e1fe9148cffa18cf97
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> 
> Unfortunately, I don't have any reproducer for this crash yet.

net-next doesn't contain the fixes for the rbtree fallout yet, so
this might already be fixed (fingers crossed).

  reply	other threads:[~2019-01-29  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  9:22 general protection fault in __xfrm_policy_bysel_ctx syzbot
2019-01-29  9:41 ` Florian Westphal [this message]
2019-01-30 14:03   ` Dmitry Vyukov
2019-01-30 14:20     ` Florian Westphal
2019-01-30 14:30       ` Dmitry Vyukov
2019-01-31  8:49         ` Dmitry Vyukov

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=20190129094144.bln4dnirr5kz3dl4@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=syzbot+e6e1fe9148cffa18cf97@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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