linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	david@fromorbit.com, linux-kernel@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: small fixes (2) for 5.9
Date: Sat, 5 Sep 2020 08:52:43 -0700	[thread overview]
Message-ID: <20200905155243.GB7955@magnolia> (raw)

Hi Linus,

Please pull this single fix for a broken metadata verifier.  The branch
merges cleanly with upstream as of a few minutes ago, so please let me
know if anything strange happens.

--D

The following changes since commit 125eac243806e021f33a1fdea3687eccbb9f7636:

  xfs: initialize the shortform attr header padding entry (2020-08-27 08:01:31 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.9-fixes-2

for you to fetch changes up to d0c20d38af135b2b4b90aa59df7878ef0c8fbef4:

  xfs: fix xfs_bmap_validate_extent_raw when checking attr fork of rt files (2020-09-03 08:33:50 -0700)

----------------------------------------------------------------
Fixes (2) for 5.9:
- Fix a broken metadata verifier that would incorrectly validate attr
fork extents of a realtime file against the realtime volume.

----------------------------------------------------------------
Darrick J. Wong (1):
      xfs: fix xfs_bmap_validate_extent_raw when checking attr fork of rt files

 fs/xfs/libxfs/xfs_bmap.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2020-09-05 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 15:52 Darrick J. Wong [this message]
2020-09-05 17:18 ` [GIT PULL] xfs: small fixes (2) for 5.9 pr-tracker-bot

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=20200905155243.GB7955@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.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).