From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot+16b6ab88e66b34d09014@syzkaller.appspotmail.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Axel Rasmussen <axelrasmussen@google.com>
Cc: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nicolas Saenz Julienne <nsaenzju@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_released
Date: Wed, 3 Jul 2024 07:08:47 +0900 [thread overview]
Message-ID: <98dcfbda-6237-4bf6-bc66-6f31cf12f678@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <0000000000002be09b061c483ea1@google.com>
The local lock itself will be removed by
mm: mmap_lock: replace get_memcg_path_buf() with on-stack buffer
but is there possibility that this bpf program forms an infinite
recursion (kernel stack overflow) bug?
On 2024/07/03 3:54, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: a12978712d90 selftests/bpf: Move ARRAY_SIZE to bpf_misc.h
> git tree: bpf-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=130457fa980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=736daf12bd72e034
> dashboard link: https://syzkaller.appspot.com/bug?extid=16b6ab88e66b34d09014
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=125718be980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14528876980000
next prev parent reply other threads:[~2024-07-02 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 18:54 syzbot
2024-07-02 22:08 ` Tetsuo Handa [this message]
[not found] ` <CAJHvVcjOjOTyrf4K+pTQ30doOx7hqheTExZY6_U+PCcdLigg7g@mail.gmail.com>
2024-07-04 13:21 ` Tetsuo Handa
2024-07-04 20:12 ` Jesper Dangaard Brouer
2024-07-11 14:33 ` Steven Rostedt
2024-08-19 4:40 ` syzbot
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=98dcfbda-6237-4bf6-bc66-6f31cf12f678@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nsaenzju@redhat.com \
--cc=syzbot+16b6ab88e66b34d09014@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox