From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org,
tj@kernel.org, linux-fscrypt@vger.kernel.org,
willy@infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption
Date: Mon, 06 Feb 2023 03:40:19 +0000 [thread overview]
Message-ID: <167565481939.5323.10753252080244168478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230203010239.216421-1-ebiggers@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 2 Feb 2023 17:02:39 -0800 you wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> When writing a page from an encrypted file that is using
> filesystem-layer encryption (not inline encryption), f2fs encrypts the
> pagecache page into a bounce page, then writes the bounce page.
>
> It also passes the bounce page to wbc_account_cgroup_owner(). That's
> incorrect, because the bounce page is a newly allocated temporary page
> that doesn't have the memory cgroup of the original pagecache page.
> This makes wbc_account_cgroup_owner() not account the I/O to the owner
> of the pagecache page as it should.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix cgroup writeback accounting with fs-layer encryption
https://git.kernel.org/jaegeuk/f2fs/c/844545c51a5b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-06 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 1:02 [PATCH] f2fs: fix cgroup writeback accounting with fs-layer encryption Eric Biggers
2023-02-03 8:54 ` [f2fs-dev] " Chao Yu
2023-02-03 18:20 ` Tejun Heo
2023-02-06 3:40 ` patchwork-bot+f2fs [this message]
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=167565481939.5323.10753252080244168478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=willy@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).