All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+73d662376f16e2a7336d@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: upstream boot error: UBSAN: null-ptr-deref in corrupted
Date: Fri, 18 Dec 2020 11:47:12 -0800	[thread overview]
Message-ID: <202012181131.A231B861@keescook> (raw)
In-Reply-To: <CACT4Y+a2itFzrrE63s0E0zEYzWRhg3eRy+zUishW2dqYrywsnw@mail.gmail.com>

On Thu, Dec 17, 2020 at 11:38:30AM +0100, Dmitry Vyukov wrote:
> On Thu, Dec 17, 2020 at 11:14 AM syzbot
> <syzbot+73d662376f16e2a7336d@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    accefff5 Merge tag 'arm-soc-omap-genpd-5.11' of git://git...
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14567b7f500000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=1e6efc730c219bd4
> > dashboard link: https://syzkaller.appspot.com/bug?extid=73d662376f16e2a7336d
> > compiler:       clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+73d662376f16e2a7336d@syzkaller.appspotmail.com
> 
> +Kees
> 
> Not sure if it's related to UBSAN or not, but we didn't used to get
> empty stack traces.
> Either way syzbot can't boot the upstream kernel anymore.

_none_ of them? :(

Are you able to see which UBSAN config is tweaking this?

-- 
Kees Cook

  reply	other threads:[~2020-12-18 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 10:14 upstream boot error: UBSAN: null-ptr-deref in corrupted syzbot
2020-12-17 10:38 ` Dmitry Vyukov
2020-12-18 19:47   ` Kees Cook [this message]
2020-12-19  9:48     ` 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=202012181131.A231B861@keescook \
    --to=keescook@chromium.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+73d662376f16e2a7336d@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 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.