From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/3] xfs: rework quotaoff to avoid log deadlock
Date: Tue, 6 Apr 2021 10:42:35 -0400 [thread overview]
Message-ID: <20210406144238.814558-1-bfoster@redhat.com> (raw)
This series reworks the quotaoff algorithm to eliminate a log
reservation deadlock vector. v2 is primarily a rebase/repost of v1.
Note that this conflicts with the recently posted append ioend cleanup,
but this series is still based on for-next. I can post another rebased
series if either of these progress.
Brian
v2:
- Rebased to for-next.
v1: https://lore.kernel.org/linux-xfs/20201001150310.141467-1-bfoster@redhat.com/
Brian Foster (3):
xfs: skip dquot reservations if quota is inactive
xfs: transaction subsystem quiesce mechanism
xfs: rework quotaoff logging to avoid log deadlock on active fs
fs/xfs/xfs_aops.c | 2 +
fs/xfs/xfs_mount.h | 3 +
fs/xfs/xfs_qm_syscalls.c | 133 +++++++++++++++++++--------------------
fs/xfs/xfs_super.c | 8 +++
fs/xfs/xfs_trans.c | 4 +-
fs/xfs/xfs_trans.h | 20 ++++++
fs/xfs/xfs_trans_dquot.c | 22 +++----
7 files changed, 111 insertions(+), 81 deletions(-)
--
2.26.3
next reply other threads:[~2021-04-06 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 14:42 Brian Foster [this message]
2021-04-06 14:42 ` [PATCH v2 1/3] xfs: skip dquot reservations if quota is inactive Brian Foster
2021-04-07 7:58 ` Christoph Hellwig
2021-04-07 15:51 ` Darrick J. Wong
2021-04-06 14:42 ` [PATCH v2 2/3] xfs: transaction subsystem quiesce mechanism Brian Foster
2021-04-07 8:00 ` Christoph Hellwig
2021-04-07 11:36 ` Brian Foster
2021-04-07 13:24 ` Christoph Hellwig
2021-04-07 15:50 ` Darrick J. Wong
2021-04-06 14:42 ` [PATCH v2 3/3] xfs: rework quotaoff logging to avoid log deadlock on active fs Brian Foster
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=20210406144238.814558-1-bfoster@redhat.com \
--to=bfoster@redhat.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 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).