public inbox for linux-xfs@vger.kernel.org
 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 Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>, Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] xfs: hair on fire fixes for 4.17-rc7
Date: Thu, 31 May 2018 14:15:44 -0700	[thread overview]
Message-ID: <20180531211544.GX12940@magnolia> (raw)

Hi Linus,

This last minute fix prevents writeback error state from persisting past
the end of the in-core inode lifecycle and causing EIO errors to be
reported to userspace when no error has occurred.

This fix for the behavioral regression has been soaking in for-next for
a while, but various fs developers persuaded me to try to get it
upstream for 4.17 because the patch that broke things was introduced in
4.17-rc4.  It merges cleanly with master as of this morning.

(If you prefer I hold it for 4.18 and send it to stable for 4.17.1 as
originally planned, that's fine too.)

--D

The following changes since commit 021ba8e98fe5c6691b3cc3669faafa02403aa211:

  xfs: cap the length of deduplication requests (2018-05-02 09:21:33 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.17-fixes-3

for you to fetch changes up to 829bc787c1a0403e4d886296dd4d90c5f9c1744a:

  fs: clear writeback errors in inode_init_always (2018-05-30 19:43:53 -0700)

----------------------------------------------------------------
Changes since last update:
- Clear out i_mapping error state when we're reinitializing inodes.

----------------------------------------------------------------
Darrick J. Wong (1):
      fs: clear writeback errors in inode_init_always

 fs/inode.c | 1 +
 1 file changed, 1 insertion(+)

                 reply	other threads:[~2018-05-31 21:15 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=20180531211544.GX12940@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 \
    --cc=tytso@mit.edu \
    /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