From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+4793f6096d174c90b4f7@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid potential deadlock
Date: Fri, 16 Dec 2022 12:42:02 -0800 [thread overview]
Message-ID: <Y5zYGsBZDZ9101zU@sol.localdomain> (raw)
In-Reply-To: <20221216155000.3204-1-chao@kernel.org>
On Fri, Dec 16, 2022 at 11:50:00PM +0800, Chao Yu wrote:
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index cad4bdd6f097..4bc98dbe8292 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -2336,6 +2336,7 @@ static int f2fs_ioc_get_encryption_pwsalt(struct file *filp, unsigned long arg)
> {
> struct inode *inode = file_inode(filp);
> struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> + u8 encrypt_pw_salt[16];
> int err;
>
> if (!f2fs_sb_has_encrypt(sbi))
> @@ -2360,12 +2361,14 @@ static int f2fs_ioc_get_encryption_pwsalt(struct file *filp, unsigned long arg)
> goto out_err;
> }
> got_it:
> - if (copy_to_user((__u8 __user *)arg, sbi->raw_super->encrypt_pw_salt,
> - 16))
> - err = -EFAULT;
> + memcpy(encrypt_pw_salt, sbi->raw_super->encrypt_pw_salt, 16);
> out_err:
> f2fs_up_write(&sbi->sb_lock);
> mnt_drop_write_file(filp);
> +
> + if (!err && copy_to_user((__u8 __user *)arg, encrypt_pw_salt, 16))
> + err = -EFAULT;
> +
> return err;
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2022-12-16 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 15:50 Chao Yu
2022-12-16 20:42 ` Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-14 11:47 Chao Yu
2025-11-11 22:50 ` [f2fs-dev] " patchwork-bot+f2fs
2022-01-27 5:44 Chao Yu
2022-01-27 21:59 ` Jaegeuk Kim
2022-01-28 1:43 ` Chao Yu
2022-01-29 0:37 ` Jaegeuk Kim
2022-01-29 1:48 ` Chao Yu
2022-02-03 1:51 ` Jaegeuk Kim
2022-02-03 14:57 ` Chao Yu
2022-02-25 3:02 ` [f2fs-dev] " Chao Yu
2022-03-02 3:32 ` Chao Yu
2022-03-02 5:26 ` Jaegeuk Kim
2022-03-02 8:14 ` Chao Yu
2022-03-02 19:45 ` Jaegeuk Kim
2022-03-03 2:32 ` Chao Yu
2022-03-03 21:30 ` Jaegeuk Kim
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=Y5zYGsBZDZ9101zU@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+4793f6096d174c90b4f7@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®