From: Chao Yu <chao@kernel.org>
To: Lizhi Xu <lizhi.xu@windriver.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix deadlock in f2f2_add_dentry
Date: Fri, 25 Aug 2023 18:41:38 +0800 [thread overview]
Message-ID: <517380b7-77e6-3b79-5156-234b51dbb104@kernel.org> (raw)
In-Reply-To: <20230825053732.3098387-1-lizhi.xu@windriver.com>
On 2023/8/25 13:37, Lizhi Xu wrote:
> There are two paths:
> 1. f2fs_add_dentry->f2fs_down_read->f2fs_add_inline_entry->down_write->
> up_write->f2fs_up_read
> 2. f2fs_add_dentry->f2fs_add_regular_entry->down_write->
> f2fs_init_inode_metadata->f2fs_down_read->f2fs_up_read->up_write
>
> Force order lock to read->write.
Hi Lizhi,
Thanks for the fix.
Can you please check below patch? it has fixed reported issue.
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=5c13e2388bf3426fd69a89eb46e50469e9624e56
Feedback from syzbot:
https://lore.kernel.org/linux-f2fs-devel/0000000000001ba17a0603b5871e@google.com/
>
> Signed-off-by: Lizhi Xu <lizhi.xu@windriver.com>
> Reported-and-tested-by: syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com
> ---
> fs/f2fs/dir.c | 4 +---
> fs/f2fs/inline.c | 2 ++
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
> index d635c58cf5a3..022dc02c1390 100644
> --- a/fs/f2fs/dir.c
> +++ b/fs/f2fs/dir.c
> @@ -736,12 +736,12 @@ int f2fs_add_regular_entry(struct inode *dir, const struct f2fs_filename *fname,
> f2fs_wait_on_page_writeback(dentry_page, DATA, true, true);
>
> if (inode) {
> - f2fs_down_write(&F2FS_I(inode)->i_sem);
> page = f2fs_init_inode_metadata(inode, dir, fname, NULL);
> if (IS_ERR(page)) {
> err = PTR_ERR(page);
> goto fail;
> }
> + f2fs_down_write(&F2FS_I(inode)->i_sem);
> }
>
> make_dentry_ptr_block(NULL, &d, dentry_blk);
> @@ -780,9 +780,7 @@ int f2fs_add_dentry(struct inode *dir, const struct f2fs_filename *fname,
> * Should get i_xattr_sem to keep the lock order:
> * i_xattr_sem -> inode_page lock used by f2fs_setxattr.
> */
> - f2fs_down_read(&F2FS_I(dir)->i_xattr_sem);
> err = f2fs_add_inline_entry(dir, fname, inode, ino, mode);
> - f2fs_up_read(&F2FS_I(dir)->i_xattr_sem);
> }
> if (err == -EAGAIN)
> err = f2fs_add_regular_entry(dir, fname, inode, ino, mode);
> diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
> index 4638fee16a91..7618b383c2b7 100644
> --- a/fs/f2fs/inline.c
> +++ b/fs/f2fs/inline.c
> @@ -628,10 +628,12 @@ int f2fs_add_inline_entry(struct inode *dir, const struct f2fs_filename *fname,
> if (IS_ERR(ipage))
> return PTR_ERR(ipage);
>
> + f2fs_down_read(&F2FS_I(dir)->i_xattr_sem);
> inline_dentry = inline_data_addr(dir, ipage);
> make_dentry_ptr_inline(dir, &d, inline_dentry);
>
> bit_pos = f2fs_room_for_filename(d.bitmap, slots, d.max);
> + f2fs_up_read(&F2FS_I(dir)->i_xattr_sem);
> if (bit_pos >= d.max) {
> err = do_convert_inline_dir(dir, ipage, inline_dentry);
> if (err)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-08-25 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:55 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-08-24 15:55 ` syzbot
2023-08-25 1:08 ` Chao Yu
2023-08-25 1:47 ` syzbot
2023-08-25 5:37 ` [f2fs-dev] [PATCH] f2fs: fix deadlock in f2f2_add_dentry Lizhi Xu via Linux-f2fs-devel
2023-08-25 10:41 ` Chao Yu [this message]
2023-08-26 2:58 ` Lizhi Xu via Linux-f2fs-devel
2023-09-06 12:56 ` Tetsuo Handa
2023-10-26 6:59 ` [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-10-26 9:21 ` Aleksandr Nogikh via Linux-f2fs-devel
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=517380b7-77e6-3b79-5156-234b51dbb104@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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).