From: Arnd Bergmann <arnd@arndb.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: "Dmitry Vyukov" <dvyukov@google.com>,
syzbot <syzbot+0b06ef9b44d00d600183@syzkaller.appspotmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [syzbot] kernel panic: corrupted stack end in openat
Date: Tue, 16 Mar 2021 17:03:28 +0100 [thread overview]
Message-ID: <CAK8P3a3A=TVWWmog=1YsALUhsaSkqReNrao5OTRd5mwyd0pnig@mail.gmail.com> (raw)
In-Reply-To: <20210316155102.GP1463@shell.armlinux.org.uk>
On Tue, Mar 16, 2021 at 4:51 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
> On Tue, Mar 16, 2021 at 04:44:45PM +0100, Arnd Bergmann wrote:
> > On Tue, Mar 16, 2021 at 11:17 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> > > The compiler is gcc version 10.2.1 20210110 (Debian 10.2.1-6)
> >
> > Ok, building with Ubuntu 10.2.1-1ubuntu1 20201207 locally, that's
> > the closest I have installed, and I think the Debian and Ubuntu versions
> > are generally quite close in case of gcc since they are maintained by
> > the same packagers.
>
> ... which shouldn't be a problem - that's just over 1/4 of the stack
> space. Could it be the syzbot's gcc is doing something weird and
> inflating the stack frames?
It's possible, I think that's really unlikely given that it's just Debian's
gcc, which is as close to mainline as the version I was using.
Uwe's DEBUG_STACKOVERFLOW patch from a while ago might
help if this was the problem though:
https://lore.kernel.org/linux-arm-kernel/20200108082913.29710-1-u.kleine-koenig@pengutronix.de/
My best guess is something going wrong in the interrupt
that triggered the preempt_schedule() which ended up calling
task_stack_end_corrupted() in schedule_debug(), as you suggested
earlier.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: "Dmitry Vyukov" <dvyukov@google.com>,
syzbot <syzbot+0b06ef9b44d00d600183@syzkaller.appspotmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [syzbot] kernel panic: corrupted stack end in openat
Date: Tue, 16 Mar 2021 17:03:28 +0100 [thread overview]
Message-ID: <CAK8P3a3A=TVWWmog=1YsALUhsaSkqReNrao5OTRd5mwyd0pnig@mail.gmail.com> (raw)
In-Reply-To: <20210316155102.GP1463@shell.armlinux.org.uk>
On Tue, Mar 16, 2021 at 4:51 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
> On Tue, Mar 16, 2021 at 04:44:45PM +0100, Arnd Bergmann wrote:
> > On Tue, Mar 16, 2021 at 11:17 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> > > The compiler is gcc version 10.2.1 20210110 (Debian 10.2.1-6)
> >
> > Ok, building with Ubuntu 10.2.1-1ubuntu1 20201207 locally, that's
> > the closest I have installed, and I think the Debian and Ubuntu versions
> > are generally quite close in case of gcc since they are maintained by
> > the same packagers.
>
> ... which shouldn't be a problem - that's just over 1/4 of the stack
> space. Could it be the syzbot's gcc is doing something weird and
> inflating the stack frames?
It's possible, I think that's really unlikely given that it's just Debian's
gcc, which is as close to mainline as the version I was using.
Uwe's DEBUG_STACKOVERFLOW patch from a while ago might
help if this was the problem though:
https://lore.kernel.org/linux-arm-kernel/20200108082913.29710-1-u.kleine-koenig@pengutronix.de/
My best guess is something going wrong in the interrupt
that triggered the preempt_schedule() which ended up calling
task_stack_end_corrupted() in schedule_debug(), as you suggested
earlier.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-16 16:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 7:18 [syzbot] kernel panic: corrupted stack end in openat syzbot
2021-03-16 7:18 ` syzbot
2021-03-16 7:59 ` Dmitry Vyukov
2021-03-16 7:59 ` Dmitry Vyukov
2021-03-16 7:59 ` Dmitry Vyukov
2021-03-16 9:24 ` Russell King - ARM Linux admin
2021-03-16 9:24 ` Russell King - ARM Linux admin
2021-03-16 9:51 ` Dmitry Vyukov
2021-03-16 9:51 ` Dmitry Vyukov
2021-03-16 9:51 ` Dmitry Vyukov
2021-03-16 10:02 ` Arnd Bergmann
2021-03-16 10:02 ` Arnd Bergmann
2021-03-16 10:02 ` Arnd Bergmann
2021-03-16 10:17 ` Dmitry Vyukov
2021-03-16 10:17 ` Dmitry Vyukov
2021-03-16 10:17 ` Dmitry Vyukov
2021-03-16 15:44 ` Arnd Bergmann
2021-03-16 15:44 ` Arnd Bergmann
2021-03-16 15:44 ` Arnd Bergmann
2021-03-16 15:51 ` Russell King - ARM Linux admin
2021-03-16 15:51 ` Russell King - ARM Linux admin
2021-03-16 16:03 ` Dmitry Vyukov
2021-03-16 16:03 ` Dmitry Vyukov
2021-03-16 16:03 ` Dmitry Vyukov
2021-03-16 16:03 ` Arnd Bergmann [this message]
2021-03-16 16:03 ` Arnd Bergmann
2021-03-16 16:13 ` Dmitry Vyukov
2021-03-16 16:13 ` Dmitry Vyukov
2021-03-16 16:28 ` Arnd Bergmann
2021-03-16 16:28 ` Arnd Bergmann
2021-03-17 7:47 ` Dmitry Vyukov
2021-03-17 7:47 ` Dmitry Vyukov
2021-03-17 8:31 ` Arnd Bergmann
2021-03-17 8:31 ` Arnd Bergmann
2021-03-17 8:50 ` Dmitry Vyukov
2021-03-17 8:50 ` Dmitry Vyukov
2021-03-16 10:37 ` Ard Biesheuvel
2021-03-16 10:37 ` Ard Biesheuvel
2021-03-16 10:37 ` Ard Biesheuvel
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='CAK8P3a3A=TVWWmog=1YsALUhsaSkqReNrao5OTRd5mwyd0pnig@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=syzbot+0b06ef9b44d00d600183@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.