From: syzbot <syzbot+a6456f6334aa19425886@syzkaller.appspotmail.com>
To: paul@paul-moore.com
Cc: 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: Wed, 02 Oct 2024 18:32:30 -0700 [thread overview]
Message-ID: <66fdf42e.050a0220.28a3b.01f3.GAE@google.com> (raw)
In-Reply-To: <CAHC9VhSa-2Q5SPXJHfvyHCYXQEFPDQaYcRf82FVB2CH-PHxnFA@mail.gmail.com>
> On Wed, Oct 2, 2024 at 8:14 AM Shu Han <ebpqwerty472123@gmail.com> wrote:
>>
>> It seems to be the same as [1].
>> New LSM hook position for remap_file_pages + IMA = deadlock.
>> The new LSM hook position is added for a bypass caused by
>> no check in remap_file_pages + READ_IMPLIES_EXEC in do_mmap.
>
> Thanks Shu Han, let's mark this as a dup and sort out a fix in the first report.
>
> #syz dup: [syzbot] [integrity?] [lsm?] possible deadlock in
can't find the dup bug
> process_measurement (4)
>
>> I suggest fix it by removing the check and moving READ_IMPLIES_EXEC
>> out of do_mmap[2].
>>
>> Link: https://lore.kernel.org/lkml/20240928065620.7abadb2d8552f03d785c77c9@linux-foundation.org/
>> [1]
>> Link: https://lore.kernel.org/all/20240928180044.50-1-ebpqwerty472123@gmail.com/
>> [2]
>
> --
> paul-moore.com
next prev parent reply other threads:[~2024-10-03 1:32 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
2024-10-02 12:14 ` Shu Han
2024-10-03 1:32 ` Paul Moore
2024-10-03 1:32 ` syzbot [this message]
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=66fdf42e.050a0220.28a3b.01f3.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.