From: Chao Yu <chao2.yu@samsung.com>
To: "'Jaegeuk Kim'" <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 3/3] f2fs: use lock_buffer when changing superblock
Date: Wed, 09 Dec 2015 14:10:03 +0800 [thread overview]
Message-ID: <015101d13248$58a641e0$09f2c5a0$@samsung.com> (raw)
In-Reply-To: <1449528805-89661-3-git-send-email-jaegeuk@kernel.org>
Hi Jaegeuk,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Tuesday, December 08, 2015 6:53 AM
> To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> linux-f2fs-devel@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 3/3] f2fs: use lock_buffer when changing superblock
>
> When modifying sb contents, we need to use lock its buffer.
How about applying the rule to _undo_ flow after f2fs_commit_super failed?
Thanks,
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/file.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index a018ed3..a16dfe9 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -1591,7 +1591,9 @@ static int f2fs_ioc_get_encryption_pwsalt(struct file *filp, unsigned
> long arg)
> return err;
>
> /* update superblock with uuid */
> + lock_buffer(sbi->raw_super_buf);
> generate_random_uuid(sbi->raw_super->encrypt_pw_salt);
> + unlock_buffer(sbi->raw_super_buf);
>
> err = f2fs_commit_super(sbi, false);
>
> --
> 2.4.9 (Apple Git-60)
>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> 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:[~2015-12-09 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 22:53 [PATCH 1/3] f2fs: enhance the bit operation for SSR Jaegeuk Kim
2015-12-07 22:53 ` [PATCH 2/3] f2fs: refactor f2fs_commit_super Jaegeuk Kim
2015-12-09 6:08 ` [f2fs-dev] " Chao Yu
2015-12-07 22:53 ` [PATCH 3/3] f2fs: use lock_buffer when changing superblock Jaegeuk Kim
2015-12-09 6:10 ` Chao Yu [this message]
2015-12-09 17:54 ` [f2fs-dev] [PATCH 3/3 v2] " Jaegeuk Kim
2015-12-09 6:06 ` [f2fs-dev] [PATCH 1/3] f2fs: enhance the bit operation for SSR Chao Yu
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='015101d13248$58a641e0$09f2c5a0$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome