From: syzbot <syzbot+a6456f6334aa19425886@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ebpqwerty472123@gmail.com,
hughd@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, paul@paul-moore.com,
stephen.smalley.work@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] possible deadlock in upgrade_mmap_lock_carefully
Date: Tue, 01 Oct 2024 21:48:02 -0700 [thread overview]
Message-ID: <66fcd082.050a0220.f28ec.04f1.GAE@google.com> (raw)
In-Reply-To: <66f8846e.050a0220.aab67.000b.GAE@google.com>
syzbot has bisected this issue to:
commit ea7e2d5e49c05e5db1922387b09ca74aa40f46e2
Author: Shu Han <ebpqwerty472123@gmail.com>
Date: Tue Sep 17 09:41:04 2024 +0000
mm: call the security_mmap_file() LSM hook in remap_file_pages()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1530539f980000
start commit: e32cde8d2bd7 Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1730539f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1330539f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=286b31f2cf1c36b5
dashboard link: https://syzkaller.appspot.com/bug?extid=a6456f6334aa19425886
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154e8927980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1244bdd0580000
Reported-by: syzbot+a6456f6334aa19425886@syzkaller.appspotmail.com
Fixes: ea7e2d5e49c0 ("mm: call the security_mmap_file() LSM hook in remap_file_pages()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-02 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 22:34 [syzbot] [mm?] possible deadlock in upgrade_mmap_lock_carefully syzbot
2024-10-01 18:46 ` syzbot
2024-10-02 4:48 ` syzbot [this message]
2024-10-02 12:14 ` Shu Han
2024-10-03 1:32 ` Paul Moore
2024-10-03 1:32 ` syzbot
2024-10-03 2:52 ` Paul Moore
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=66fcd082.050a0220.f28ec.04f1.GAE@google.com \
--to=syzbot+a6456f6334aa19425886@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebpqwerty472123@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul@paul-moore.com \
--cc=stephen.smalley.work@gmail.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.