linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+1cd571a672400ef3a930@syzkaller.appspotmail.com>
Cc: dmitry.kasatkin@gmail.com, ebpqwerty472123@gmail.com,
	eric.snowberg@oracle.com, hughd@google.com, jmorris@namei.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-security-module@vger.kernel.org,
	paul@paul-moore.com, roberto.sassu@huawei.com, serge@hallyn.com,
	stephen.smalley.work@gmail.com, syzkaller-bugs@googlegroups.com,
	zohar@linux.ibm.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@kernel.org
Subject: Re: [syzbot] [integrity?] [lsm?] possible deadlock in process_measurement (4)
Date: Sat, 28 Sep 2024 06:56:20 -0700	[thread overview]
Message-ID: <20240928065620.7abadb2d8552f03d785c77c9@linux-foundation.org> (raw)
In-Reply-To: <66f7b10e.050a0220.46d20.0036.GAE@google.com>

On Sat, 28 Sep 2024 00:32:30 -0700 syzbot <syzbot+1cd571a672400ef3a930@syzkaller.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@gmail.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?



  reply	other threads:[~2024-09-28 13:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28  7:32 [syzbot] [integrity?] [lsm?] possible deadlock in process_measurement (4) syzbot
2024-09-28 13:56 ` Andrew Morton [this message]
2024-09-28 18:07 ` Shu Han
2024-10-03  3:09   ` Paul Moore
2024-10-03  7:35     ` Shu Han
2024-10-07 15:31     ` Roberto Sassu
2024-10-07 16:35       ` Paul Moore
2024-10-07 16:49         ` Roberto Sassu
2024-10-07 16:58           ` Paul Moore
2024-10-09 16:23             ` Roberto Sassu
2024-10-09 19:05               ` syzbot
2024-10-18 14:55               ` Roberto Sassu
2024-10-18 15:23                 ` 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=20240928065620.7abadb2d8552f03d785c77c9@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=ebpqwerty472123@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=jmorris@namei.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.com \
    --cc=serge@hallyn.com \
    --cc=stable@kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    --cc=syzbot+1cd571a672400ef3a930@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).