public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: "Darrick J . Wong" <djwong@kernel.org>
Cc: Dave Chinner <david@fromorbit.com>,
	Brian Foster <bfoster@redhat.com>, Christoph Hellwig <hch@lst.de>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Adam Manzanares <a.manzanares@samsung.com>,
	linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 5.10 CANDIDATE 0/7] xfs stable candidate patches for 5.10.y (part 3)
Date: Mon,  6 Jun 2022 19:05:30 +0300	[thread overview]
Message-ID: <20220606160537.689915-1-amir73il@gmail.com> (raw)

Hi all!

This is the 3rd part of a collection of stable patch candidates that
I collected from xfs releases v5.11..v5.18.

Part #1 is already in 5.10.120 and part #2 has been posted to stable.

The patches in this part are from circa v5.12..v5.13.

They have been soaking in kdevops for over a week with no regressions
from baseline observed.

There are four user visible fixes in this part, one patch for dependency
("rename variable mp") and two patches to improve testability of LTS.

Specifically, I selected the fix ("use current->journal_info for
detecting transaction recursion") after I got a false positive assert
while testing LTS kernel with XFS_DEBUG and at another incident, it
helped me triage a regression that would have been harder to trace
back to the offending code otherwise.

It is worth noting that one patch from v5.13 did cause a regression
and was removed from the stable candidates queue during early testing -
0fe0bbe00a6f ("xfs: bunmapi has unnecessary AG lock ordering issues").

When I did a post mortem on a patch that I missed for part #2, I started
off on the wrong foot with Dave, so it is important for me to say this:
Although I had wrongly selected this fix, all the information I needed
to make the right decision was in the commit message, I just did not
understand it at the time that I selected the patch.

But when my tests had detected hangs on test xfs/299, that quickly lead
me to the mention of xfs/299 in the commit message and then I understood
that the fix was incorrect without "deferred inode inactivation" series
from 5.13-rc1.

I would like to thank Samsung and Luis for the resources and efforts
that make this work possible.

Your inputs on these stable candidates are most welcome!

Thanks,
Amir.


Anthony Iliopoulos (1):
  xfs: fix xfs_trans slab cache name

Darrick J. Wong (1):
  xfs: fix xfs_reflink_unshare usage of filemap_write_and_wait_range

Dave Chinner (2):
  xfs: use current->journal_info for detecting transaction recursion
  xfs: update superblock counters correctly for !lazysbcount

Gao Xiang (1):
  xfs: ensure xfs_errortag_random_default matches XFS_ERRTAG_MAX

Pavel Reichl (2):
  xfs: rename variable mp to parsing_mp
  xfs: Skip repetitive warnings about mount options

 fs/iomap/buffered-io.c    |   7 ---
 fs/xfs/libxfs/xfs_btree.c |  12 +++-
 fs/xfs/libxfs/xfs_sb.c    |  16 ++++-
 fs/xfs/xfs_aops.c         |  17 +++++-
 fs/xfs/xfs_error.c        |   2 +
 fs/xfs/xfs_reflink.c      |   3 +-
 fs/xfs/xfs_super.c        | 120 +++++++++++++++++++++-----------------
 fs/xfs/xfs_trans.c        |  23 +++-----
 fs/xfs/xfs_trans.h        |  30 ++++++++++
 9 files changed, 148 insertions(+), 82 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-06-06 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 16:05 Amir Goldstein [this message]
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 1/7] xfs: use current->journal_info for detecting transaction recursion Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 2/7] xfs: rename variable mp to parsing_mp Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 3/7] xfs: Skip repetitive warnings about mount options Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 4/7] xfs: ensure xfs_errortag_random_default matches XFS_ERRTAG_MAX Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 5/7] xfs: fix xfs_trans slab cache name Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 6/7] xfs: update superblock counters correctly for !lazysbcount Amir Goldstein
2022-06-06 16:05 ` [PATCH 5.10 CANDIDATE 7/7] xfs: fix xfs_reflink_unshare usage of filemap_write_and_wait_range Amir Goldstein

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=20220606160537.689915-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=a.manzanares@samsung.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@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