From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
Yonggil Song <yonggil.song@samsung.com>
Cc: Seokhwan Kim <sukka.kim@samsung.com>,
"daehojeong@google.com" <daehojeong@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix uninitialized skipped_gc_rwsem
Date: Mon, 13 Mar 2023 14:11:10 +0800 [thread overview]
Message-ID: <67687aed-df8e-4264-57fd-f19dcc36ae10@kernel.org> (raw)
In-Reply-To: <ZAZgf4sbh14sVZMp@google.com>
On 2023/3/7 5:51, Jaegeuk Kim wrote:
> Applied with the below fix.
>
> Fixes: 6f8d4455060d ("f2fs: avoid fi->i_gc_rwsem[WRITE] lock in f2fs_gc"
')' was missed.
>
>> Signed-off-by: Yonggil Song <yonggil.song@samsung.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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-03-13 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230215024850epcms2p22be2cc864d82b44f31c19a7ef28770b6@epcms2p7>
2023-02-16 7:13 ` [f2fs-dev] [PATCH v2] f2fs: fix uninitialized skipped_gc_rwsem Yonggil Song
2023-03-06 21:51 ` Jaegeuk Kim
2023-03-13 6:11 ` Chao Yu [this message]
[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
[not found] <CGME20230215024850epcms2p22be2cc864d82b44f31c19a7ef28770b6@epcms2p4>
2023-02-16 7:44 ` Yonggil Song
2023-02-16 7:46 ` gregkh
2023-03-13 20:20 ` patchwork-bot+f2fs
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=67687aed-df8e-4264-57fd-f19dcc36ae10@kernel.org \
--to=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sukka.kim@samsung.com \
--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 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).