Re: [syzbot] kernel panic: corrupted stack end in openat
From: Dmitry Vyukov <dvyukov@google.com>
Date: 2021-03-16 09:52:20
Also in:
linux-mm, lkml
On Tue, Mar 16, 2021 at 10:24 AM Russell King - ARM Linux admin [off-list ref] wrote:
On Tue, Mar 16, 2021 at 08:59:17AM +0100, Dmitry Vyukov wrote:quoted
On Tue, Mar 16, 2021 at 8:18 AM syzbot [off-list ref] wrote:quoted
Hello, syzbot found the following issue on: HEAD commit: 1e28eed1 Linux 5.12-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=167535e6d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=e0cee1f53de33ca3 dashboard link: https://syzkaller.appspot.com/bug?extid=0b06ef9b44d00d600183 userspace arch: arm Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0b06ef9b44d00d600183@syzkaller.appspotmail.com+arm32 maintainer I think this is a real stack overflow on arm32, the stack is indeed deep.There's no way to know for sure because there's no indication of the stack pointer in this, so we don't know how much space remains. Therefore we don't know whether this is something in the dumped path, or an interrupt causing it.
Agree, to know for sure we would need support for VMAP_STACK. But do we really need to know it? If it's an interrupt on top, it does not make any difference? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel