From: patchwork-bot+f2fs@kernel.org
To: Yonggil Song <yonggil.song@samsung.com>
Cc: daehojeong@google.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix uninitialized skipped_gc_rwsem
Date: Mon, 13 Mar 2023 20:20:18 +0000 [thread overview]
Message-ID: <167873881815.1608.4070724001980966812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230216074427epcms2p49a3d71b08d356530b40e34e750cc2366@epcms2p4>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 16 Feb 2023 16:44:27 +0900 you wrote:
> When f2fs skipped a gc round during victim migration, there was a bug which
> would skip all upcoming gc rounds unconditionally because skipped_gc_rwsem
> was not initialized. It fixes the bug by correctly initializing the
> skipped_gc_rwsem inside the gc loop.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yonggil Song <yonggil.song@samsung.com>
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix uninitialized skipped_gc_rwsem
https://git.kernel.org/jaegeuk/f2fs/c/196036c45f8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Yonggil Song <yonggil.song@samsung.com>
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, daehojeong@google.com,
gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix uninitialized skipped_gc_rwsem
Date: Mon, 13 Mar 2023 20:20:18 +0000 [thread overview]
Message-ID: <167873881815.1608.4070724001980966812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230216074427epcms2p49a3d71b08d356530b40e34e750cc2366@epcms2p4>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 16 Feb 2023 16:44:27 +0900 you wrote:
> When f2fs skipped a gc round during victim migration, there was a bug which
> would skip all upcoming gc rounds unconditionally because skipped_gc_rwsem
> was not initialized. It fixes the bug by correctly initializing the
> skipped_gc_rwsem inside the gc loop.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yonggil Song <yonggil.song@samsung.com>
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix uninitialized skipped_gc_rwsem
https://git.kernel.org/jaegeuk/f2fs/c/196036c45f8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-13 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230215024850epcms2p22be2cc864d82b44f31c19a7ef28770b6@epcms2p4>
2023-02-16 7:44 ` [f2fs-dev] [PATCH v2] f2fs: fix uninitialized skipped_gc_rwsem Yonggil Song
2023-02-16 7:44 ` Yonggil Song
2023-02-16 7:46 ` [f2fs-dev] " gregkh
2023-02-16 7:46 ` gregkh
2023-03-13 20:20 ` patchwork-bot+f2fs [this message]
2023-03-13 20:20 ` [f2fs-dev] " patchwork-bot+f2fs
[not found] <CGME20230215024850epcms2p22be2cc864d82b44f31c19a7ef28770b6@epcms2p7>
2023-02-16 7:13 ` Yonggil Song
2023-03-06 21:51 ` Jaegeuk Kim
2023-03-13 6:11 ` Chao Yu
[not found] <CGME20230215024850epcms2p22be2cc864d82b44f31c19a7ef28770b6@epcms2p3>
2023-02-16 2:57 ` Yonggil Song
2023-02-16 7:01 ` Miko Larsson
2023-02-16 7:28 ` Yonggil Song
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=167873881815.1608.4070724001980966812.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=daehojeong@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonggil.song@samsung.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.