From: Chen Changcheng <chenchangcheng@kylinos.cn>
To: chao@kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
ccc194101@163.com, linux-kernel@vger.kernel.org,
chenchangcheng@kylinos.cn
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix valid block count leak on data block allocation failure
Date: Mon, 3 Aug 2026 15:36:25 +0800 [thread overview]
Message-ID: <20260803073625.218507-1-chenchangcheng@kylinos.cn> (raw)
Hi Chao,
> Needs fixes and Cc stable line?
>
> Reviewed-by: Chao Yu <chao@kernel.org>
Thank you for the review. Yes, I'll add both Fixes and Cc stable tags
and send a v2 shortly.
Thanks
Chen
_______________________________________________
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: Chen Changcheng <chenchangcheng@kylinos.cn>
To: chao@kernel.org
Cc: chenchangcheng@kylinos.cn, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ccc194101@163.com
Subject: Re: [PATCH] f2fs: fix valid block count leak on data block allocation failure
Date: Mon, 3 Aug 2026 15:36:25 +0800 [thread overview]
Message-ID: <20260803073625.218507-1-chenchangcheng@kylinos.cn> (raw)
Hi Chao,
> Needs fixes and Cc stable line?
>
> Reviewed-by: Chao Yu <chao@kernel.org>
Thank you for the review. Yes, I'll add both Fixes and Cc stable tags
and send a v2 shortly.
Thanks
Chen
next reply other threads:[~2026-08-03 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 7:36 Chen Changcheng [this message]
2026-08-03 7:36 ` [PATCH] f2fs: fix valid block count leak on data block allocation failure Chen Changcheng
-- strict thread matches above, loose matches on Subject: below --
2026-07-22 0:54 [f2fs-dev] " Chen Changcheng
2026-08-03 7:11 ` Chao Yu via Linux-f2fs-devel
2026-08-03 7:38 ` Chen Changcheng
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=20260803073625.218507-1-chenchangcheng@kylinos.cn \
--to=chenchangcheng@kylinos.cn \
--cc=ccc194101@163.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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.