All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	 Alexander Potapenko <glider@google.com>,
	Marco Elver <elver@google.com>
Cc: syzbot <syzbot+6b36bab98e240873fd5a@syzkaller.appspotmail.com>,
	bp@alien8.de,  dave.hansen@linux.intel.com, hpa@zytor.com,
	jmattson@google.com,  joro@8bytes.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,  llvm@lists.linux.dev,
	mingo@redhat.com, seanjc@google.com,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	vkuznets@redhat.com,  wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] upstream build error (17)
Date: Wed, 6 Apr 2022 11:26:45 -0700	[thread overview]
Message-ID: <CAKwvOd=-4S1nV=qa3CGNPTAMOv9fGYZsh8hQPXDH1MpowYDX=w@mail.gmail.com> (raw)
In-Reply-To: <7108f263-5cda-d91d-792b-d3f18b63c6d7@redhat.com>

On Wed, Apr 6, 2022 at 10:33 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 4/6/22 18:20, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    3e732ebf7316 Merge tag 'for_linus' of git://git.kernel.org..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10ca0687700000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=eba855fbe3373b4f
> > dashboard link: https://syzkaller.appspot.com/bug?extid=6b36bab98e240873fd5a
> > compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+6b36bab98e240873fd5a@syzkaller.appspotmail.com
> >
> > arch/x86/kvm/emulate.c:3332:5: error: stack frame size (2552) exceeds limit (2048) in function 'emulator_task_switch' [-Werror,-Wframe-larger-than]
> > drivers/block/loop.c:1524:12: error: stack frame size (2648) exceeds limit (2048) in function 'lo_ioctl' [-Werror,-Wframe-larger-than]
>
> I spot-checked these two and the stack frame is just 144 and 320 bytes
> respectively on a normal compile.  This is probably just the effect of
> some of the sanitizer options.

Yep.
$ wget -q https://syzkaller.appspot.com/x/.config\?x\=eba855fbe3373b4f
-O - | grep CONFIG_KASAN=y
CONFIG_KASAN=y
https://github.com/ClangBuiltLinux/linux/issues/39 (our oldest still-open issue)
-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2022-04-06 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 16:20 [syzbot] upstream build error (17) syzbot
2022-04-06 17:33 ` Paolo Bonzini
2022-04-06 18:26   ` Nick Desaulniers [this message]
2022-04-07  7:18     ` 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='CAKwvOd=-4S1nV=qa3CGNPTAMOv9fGYZsh8hQPXDH1MpowYDX=w@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=syzbot+6b36bab98e240873fd5a@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.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.