From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>, Tejun Heo <tj@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption
Date: Tue, 7 Mar 2023 11:52:20 -0800 [thread overview]
Message-ID: <ZAeV9Bl5gnmbjh/F@sol.localdomain> (raw)
In-Reply-To: <Y91QNz+U/MGs9cPc@slm.duckdns.org>
On Fri, Feb 03, 2023 at 08:19:35AM -1000, Tejun Heo wrote:
> On Thu, Feb 02, 2023 at 04:55:03PM -0800, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > When writing a page from an encrypted file that is using
> > filesystem-layer encryption (not inline encryption), ext4 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.
> >
> > Fix this by always passing the pagecache page to
> > wbc_account_cgroup_owner().
> >
> > Fixes: 001e4a8775f6 ("ext4: implement cgroup writeback support")
> > Cc: stable@vger.kernel.org
> > Reported-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Acked-by: Tejun Heo <tj@kernel.org>
>
> Thanks.
This patch hasn't been applied yet. Ted, I was hoping you would take it through
the ext4 tree. Can you do so when you have a chance?
- Eric
next prev parent reply other threads:[~2023-03-07 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 0:55 [PATCH] ext4: fix cgroup writeback accounting with fs-layer encryption Eric Biggers
2023-02-03 18:19 ` Tejun Heo
2023-03-07 19:52 ` Eric Biggers [this message]
2023-03-08 4:33 ` Theodore Ts'o
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=ZAeV9Bl5gnmbjh/F@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--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