From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Jan Kara <jack@suse.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
tytso@mit.edu, Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] Cache quota files in the page cache
Date: Sun, 5 Jun 2022 15:38:12 +0100 [thread overview]
Message-ID: <20220605143815.2330891-1-willy@infradead.org> (raw)
I don't really want to be working on this ... I'm a bit outside my zone
of knowledge here, and I'd much rather be working on folio conversions.
It mostly works, but a full xfstests run dies, probably from a memory
leak.
Matthew Wilcox (Oracle) (3):
quota: Prevent memory allocation recursion while holding dq_lock
quota: Support using the page cache for quota files
ext4: Use generic_quota_read()
fs/ext4/super.c | 81 ++++++++++------------------------------
fs/quota/dquot.c | 77 ++++++++++++++++++++++++++++++++++++++
include/linux/fs.h | 2 +
include/linux/quotaops.h | 1 +
4 files changed, 100 insertions(+), 61 deletions(-)
--
2.35.1
next reply other threads:[~2022-06-05 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 14:38 Matthew Wilcox (Oracle) [this message]
2022-06-05 14:38 ` [PATCH 1/3] quota: Prevent memory allocation recursion while holding dq_lock Matthew Wilcox (Oracle)
2022-06-06 8:03 ` Jan Kara
2022-06-06 12:42 ` Matthew Wilcox
2022-06-06 13:08 ` Jan Kara
2022-06-05 14:38 ` [PATCH 2/3] quota: Support using the page cache for quota files Matthew Wilcox (Oracle)
2022-06-06 2:53 ` kernel test robot
2022-06-06 4:05 ` kernel test robot
2022-06-06 4:36 ` kernel test robot
2022-06-05 14:38 ` [PATCH 3/3] ext4: Use generic_quota_read() Matthew Wilcox (Oracle)
2022-06-06 8:38 ` Jan Kara
2022-06-08 1:42 ` Matthew Wilcox
2022-06-08 14:21 ` Jan Kara
2022-06-13 7:59 ` [ext4] fa96490369: WARNING:at_fs/ext4/inode.c:#ext4_invalidate_folio kernel test robot
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=20220605143815.2330891-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).