From: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
To: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org,
"Luis Henriques (SUSE)" <luis.henriques@linux.dev>
Subject: [PATCH e2fsprogs v3 0/4] quota-related e2fsck fixes and tests
Date: Fri, 5 Apr 2024 15:24:01 +0100 [thread overview]
Message-ID: <20240405142405.12312-1-luis.henriques@linux.dev> (raw)
Hi!
Changes since v2:
Added deallocate_inode() documentation, as suggested by Andreas Dilger
(and using text he provided).
And, for reference, here's the cover-letter from v2:
I'm (re)sending two fixes to e2fsck that are related with quota handling.
The fixes are the first two patches, the other two are test cases for these
fixes.
As I mentioned in v1, the issues were found using fstests ext4/014 and
ext4/019. And the only thing in this series that changed from v1 was the
first test ("tests: new test to check quota after directory optimization"),
which is now using a much simplified version of the testcase.
Note that, since the first two patches didn't change, they have already a
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
which I'm not including in the patches themselves. Should I? Or is that
better left for the maintainer (eventually) applying them?
Cheers,
--
Luis
Luis Henriques (SUSE) (4):
e2fsck: update quota accounting after directory optimization
e2fsck: update quota when deallocating a bad inode
tests: new test to check quota after directory optimization
tests: new test to check quota after a bad inode deallocation
e2fsck/pass2.c | 43 ++++++++++++++++++------
e2fsck/rehash.c | 27 +++++++++++----
tests/f_quota_deallocate_inode/expect.1 | 18 ++++++++++
tests/f_quota_deallocate_inode/expect.2 | 7 ++++
tests/f_quota_deallocate_inode/image.gz | Bin 0 -> 11594 bytes
tests/f_quota_deallocate_inode/name | 1 +
tests/f_quota_shrinkdir/expect.1 | 18 ++++++++++
tests/f_quota_shrinkdir/expect.2 | 7 ++++
tests/f_quota_shrinkdir/image.gz | Bin 0 -> 10761 bytes
tests/f_quota_shrinkdir/name | 1 +
10 files changed, 105 insertions(+), 17 deletions(-)
create mode 100644 tests/f_quota_deallocate_inode/expect.1
create mode 100644 tests/f_quota_deallocate_inode/expect.2
create mode 100644 tests/f_quota_deallocate_inode/image.gz
create mode 100644 tests/f_quota_deallocate_inode/name
create mode 100644 tests/f_quota_shrinkdir/expect.1
create mode 100644 tests/f_quota_shrinkdir/expect.2
create mode 100644 tests/f_quota_shrinkdir/image.gz
create mode 100644 tests/f_quota_shrinkdir/name
next reply other threads:[~2024-04-05 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 14:24 Luis Henriques (SUSE) [this message]
2024-04-05 14:24 ` [PATCH v3 1/4] e2fsck: update quota accounting after directory optimization Luis Henriques (SUSE)
2024-04-05 14:24 ` [PATCH v3 2/4] e2fsck: update quota when deallocating a bad inode Luis Henriques (SUSE)
2024-04-05 14:24 ` [PATCH v3 3/4] tests: new test to check quota after directory optimization Luis Henriques (SUSE)
2024-04-05 14:24 ` [PATCH v3 4/4] tests: new test to check quota after a bad inode deallocation Luis Henriques (SUSE)
2024-04-17 2:03 ` [PATCH e2fsprogs v3 0/4] quota-related e2fsck fixes and tests 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=20240405142405.12312-1-luis.henriques@linux.dev \
--to=luis.henriques@linux.dev \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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 read-only IMAP folder(s) and NNTP newsgroup(s).