linux-kernel - Re: [syzbot] [integrity?] [lsm?] possible deadlock in process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240928065620.7abadb2d8552f03d785c77c9@linux-foundation.org>
Date: Sat, 28 Sep 2024 06:56:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: syzbot <syzbot+1cd571a672400ef3a930@...kaller.appspotmail.com>
Cc: dmitry.kasatkin@...il.com, ebpqwerty472123@...il.com,
 eric.snowberg@...cle.com, hughd@...gle.com, jmorris@...ei.org,
 linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, linux-security-module@...r.kernel.org,
 paul@...l-moore.com, roberto.sassu@...wei.com, serge@...lyn.com,
 stephen.smalley.work@...il.com, syzkaller-bugs@...glegroups.com,
 zohar@...ux.ibm.com, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 stable@...nel.org
Subject: Re: [syzbot] [integrity?] [lsm?] possible deadlock in
 process_measurement (4)

On Sat, 28 Sep 2024 00:32:30 -0700 syzbot <syzbot+1cd571a672400ef3a930@...kaller.appspotmail.com> wrote:

> Hello,
> 
> syzbot found the following issue on:

Thanks.

> HEAD commit:    97d8894b6f4c Merge tag 'riscv-for-linus-6.12-mw1' of git:/..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=14138a80580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753
> dashboard link: https://syzkaller.appspot.com/bug?extid=1cd571a672400ef3a930
> 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=118fd2a9980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1038299f980000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/f181c147328d/disk-97d8894b.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b8b0160d9b09/vmlinux-97d8894b.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c5dab0d4f811/bzImage-97d8894b.xz
> 
> The issue was bisected to:
> 
> commit ea7e2d5e49c05e5db1922387b09ca74aa40f46e2
> Author: Shu Han <ebpqwerty472123@...il.com>
> Date:   Tue Sep 17 09:41:04 2024 +0000
> 
>     mm: call the security_mmap_file() LSM hook in remap_file_pages()

That commit has cc:stable.

Can I suggest that you change sysbot so it includes a cc:stable if the
faulty commit had cc:stable?  If Greg agrees that would be useful?