From: Stefano Brivio <sbrivio@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: syzbot <syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
linux-kernel <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: kernel panic: stack is corrupted in udp4_lib_lookup2
Date: Thu, 3 Jan 2019 21:00:15 +0100 [thread overview]
Message-ID: <20190103210015.56917c3b@redhat.com> (raw)
In-Reply-To: <CAF=yD-L_ZfYDi5874LU54=iJD52P27EabTmHGqXS6t71y7Orxg@mail.gmail.com>
Hi Willem,
On Thu, 3 Jan 2019 13:41:43 -0600
Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
> On Thu, Jan 3, 2019 at 1:39 PM Willem de Bruijn
> <willemdebruijn.kernel@gmail.com> wrote:
> >
> > On Thu, Jan 3, 2019 at 7:07 AM syzbot
> > <syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: 195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern..
> > > git tree: upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=12245d8f400000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=4ad25edc7a33e4ab91e0
> > > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> > >
> > > Unfortunately, I don't have any reproducer for this crash yet.
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com
> > >
> > > protocol 88fb is buggy, dev hsr_slave_1
> > > protocol 88fb is buggy, dev hsr_slave_0
> > > protocol 88fb is buggy, dev hsr_slave_1
> > > FAT-fs (loop0): invalid media value (0x00)
> > > FAT-fs (loop0): Can't find a valid FAT filesystem
> > > Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
> >
> > This sounds similar to the stack corruption fixed recently in commit
> > e7cc082455cb ("udp: Support for error handlers of tunnels ...").
> >
> > That fix is for ipv4 gue_err(). ipv6 gue6_err() probably needs the same.
>
> Correction. The fix is 11789039da ("fou: prevent unbounded recursion
> in GUE error handler")
Yes, I looked into this, the fix for that issue is on the tree tested by
syzbot, and I think this is unrelated, also because KASan should say
something before we hit that.
By the way, do you happen to know if I objects from kernels tested by
syzbot are stored anywhere? It would be helpful to know for sure what's
at udp4_lib_lookup2+0x7ea.
--
Stefano
next prev parent reply other threads:[~2019-01-03 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 13:07 kernel panic: stack is corrupted in udp4_lib_lookup2 syzbot
2019-01-03 19:39 ` Willem de Bruijn
2019-01-03 19:41 ` Willem de Bruijn
2019-01-03 20:00 ` Stefano Brivio [this message]
2019-01-03 20:01 ` Eric Dumazet
2019-01-03 20:07 ` Stefano Brivio
2019-01-03 21:15 ` Willem de Bruijn
2019-01-03 21:54 ` Stefano Brivio
2019-01-04 10:32 ` Dmitry Vyukov
2019-01-04 10:34 ` Dmitry Vyukov
2019-01-04 10:54 ` Stefano Brivio
2019-01-04 11:05 ` Dmitry Vyukov
2019-01-04 17:14 ` Stefano Brivio
2019-01-04 17:24 ` Willem de Bruijn
2019-01-04 17:50 ` Stefano Brivio
2019-01-04 17:26 ` Dmitry Vyukov
2019-01-04 18:05 ` Stefano Brivio
2019-01-07 9:04 ` 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=20190103210015.56917c3b@redhat.com \
--to=sbrivio@redhat.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.