From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+9d04b061c581795e18ce@syzkaller.appspotmail.com>
Cc: jaegeuk@kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [fscrypt?] possible deadlock in find_and_lock_process_key
Date: Mon, 27 Nov 2023 14:16:05 -0800 [thread overview]
Message-ID: <20231127221605.GB1463@sol.localdomain> (raw)
In-Reply-To: <0000000000002aa189060b147268@google.com>
On Sun, Nov 26, 2023 at 12:58:22PM -0800, syzbot wrote:
> -> #3 (&type->lock_class#5){++++}-{3:3}:
> down_read+0x9a/0x330 kernel/locking/rwsem.c:1526
> find_and_lock_process_key+0x97/0x390 fs/crypto/keysetup_v1.c:112
> fscrypt_setup_v1_file_key_via_subscribed_keyrings+0x115/0x2d0 fs/crypto/keysetup_v1.c:310
> setup_file_encryption_key fs/crypto/keysetup.c:485 [inline]
> fscrypt_setup_encryption_info+0xb69/0x1080 fs/crypto/keysetup.c:590
> fscrypt_get_encryption_info+0x3d1/0x4b0 fs/crypto/keysetup.c:675
> fscrypt_setup_filename+0x238/0xd80 fs/crypto/fname.c:458
> ext4_fname_setup_filename+0xa3/0x250 fs/ext4/crypto.c:28
> ext4_add_entry+0x32b/0xe40 fs/ext4/namei.c:2403
> ext4_rename+0x165e/0x2880 fs/ext4/namei.c:3932
> ext4_rename2+0x1bc/0x270 fs/ext4/namei.c:4212
> vfs_rename+0x13e0/0x1c30 fs/namei.c:4844
> do_renameat2+0xc3c/0xdc0 fs/namei.c:4996
> __do_sys_renameat fs/namei.c:5036 [inline]
> __se_sys_renameat fs/namei.c:5033 [inline]
> __x64_sys_renameat+0xc6/0x100 fs/namei.c:5033
> do_syscall_x64 arch/x86/entry/common.c:51 [inline]
> do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
#syz dup: possible deadlock in start_this_handle (4)
See https://lore.kernel.org/linux-fscrypt/Y%2F6aDmrx8Q9ob+Zi@sol.localdomain/
- Eric
prev parent reply other threads:[~2023-11-27 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 20:58 [syzbot] [fscrypt?] possible deadlock in find_and_lock_process_key syzbot
2023-11-27 22:16 ` Eric Biggers [this message]
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=20231127221605.GB1463@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9d04b061c581795e18ce@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).