linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: 4.18 fixes, part 3
Date: Fri, 3 Aug 2018 22:17:18 -0700	[thread overview]
Message-ID: <20180804051718.GY30972@magnolia> (raw)

Hi Linus,

Here's one more patch for 4.18 to fix a coding error in the iomap_bmap
function introduced in -rc1.

This series has been run through a full xfstests run during the week and
through a quick xfstests run against this morning's master, with no
major failures reported.

--D

The following changes since commit d4a34e16555708bab5b67e679a95f055d8ef9882:

  xfs: properly handle free inodes in extent hint validators (2018-07-24 11:34:52 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.18-fixes-5

for you to fetch changes up to 79b3dbe4adb3420e74cf755b4beb5d2b43d5928d:

  fs: fix iomap_bmap position calculation (2018-08-02 13:09:27 -0700)

----------------------------------------------------------------
Changes since last update:
- Fix incorrect shifting in the iomap bmap functions.

----------------------------------------------------------------
Eric Sandeen (1):
      fs: fix iomap_bmap position calculation

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

                 reply	other threads:[~2018-08-04  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180804051718.GY30972@magnolia \
    --to=djwong@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).