public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Leah Rumancik <leah.rumancik@gmail.com>,
	Chandan Babu R <chandan.babu@oracle.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Adam Manzanares <a.manzanares@samsung.com>,
	linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH 5.10 v3 0/7] xfs stable patches for 5.10.y (from v5.13)
Date: Sun,  3 Jul 2022 08:04:49 +0300	[thread overview]
Message-ID: <20220703050456.3222610-1-amir73il@gmail.com> (raw)

Hi Greg,

Following the 5.10.y/5.15.y common series, this is another small
"5.10.y only" update.

I have two more of these (from v5.14 and v5.15) and after that,
5.10.y should be mostly following 5.15.y.

The backports from v5.14 are a little more involved, so the next
"5.10.y only" update is going to take a while longer.

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-07-03  5:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03  5:04 Amir Goldstein [this message]
2022-07-03  5:04 ` [PATCH 5.10 v3 1/7] xfs: use current->journal_info for detecting transaction recursion Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 2/7] xfs: rename variable mp to parsing_mp Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 3/7] xfs: Skip repetitive warnings about mount options Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 4/7] xfs: ensure xfs_errortag_random_default matches XFS_ERRTAG_MAX Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 5/7] xfs: fix xfs_trans slab cache name Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 6/7] xfs: update superblock counters correctly for !lazysbcount Amir Goldstein
2022-07-03  5:04 ` [PATCH 5.10 v3 7/7] xfs: fix xfs_reflink_unshare usage of filemap_write_and_wait_range Amir Goldstein
2022-07-03  5:07 ` [PATCH 5.10 v3 0/7] xfs stable patches for 5.10.y (from v5.13) Amir Goldstein
2022-07-04 14:42 ` Greg Kroah-Hartman

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=20220703050456.3222610-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=a.manzanares@samsung.com \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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