From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com, bfoster@redhat.com
Subject: [PATCHSET v2 0/3] xfs: preserve inode health reports for longer
Date: Wed, 02 Jun 2021 20:12:35 -0700 [thread overview]
Message-ID: <162268995567.2724138.15163777746481739089.stgit@locust> (raw)
Hi all,
This is a quick series to make sure that inode sickness reports stick
around in memory for some amount of time.
v2: rebase to 5.13-rc4
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=fix-inode-health-reports-5.14
---
fs/xfs/xfs_health.c | 5 +++++
fs/xfs/xfs_icache.c | 29 +++++++++++++++++++++--------
2 files changed, 26 insertions(+), 8 deletions(-)
next reply other threads:[~2021-06-03 3:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 3:12 Darrick J. Wong [this message]
2021-06-03 3:12 ` [PATCH 1/3] xfs: only reset incore inode health state flags when reclaiming an inode Darrick J. Wong
2021-06-03 4:21 ` Dave Chinner
2021-06-03 20:41 ` Darrick J. Wong
2021-06-03 12:22 ` Brian Foster
2021-06-03 20:41 ` Darrick J. Wong
2021-06-03 3:12 ` [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick Darrick J. Wong
2021-06-03 4:34 ` Dave Chinner
2021-06-03 20:49 ` Darrick J. Wong
2021-06-03 12:23 ` Brian Foster
2021-06-03 20:48 ` Darrick J. Wong
2021-06-03 3:12 ` [PATCH 3/3] xfs: don't let background reclaim forget sick inodes Darrick J. Wong
2021-06-03 4:42 ` Dave Chinner
2021-06-03 12:31 ` Brian Foster
2021-06-03 21:30 ` Darrick J. Wong
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=162268995567.2724138.15163777746481739089.stgit@locust \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@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.