public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: "Yan, Zheng" <zyan@redhat.com>, Sage Weil <sage@redhat.com>,
	Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ceph: make kcephfs use errseq_t for writeback error reporting
Date: Tue, 25 Jul 2017 10:50:40 -0400	[thread overview]
Message-ID: <20170725145042.26219-1-jlayton@kernel.org> (raw)

From: Jeff Layton <jlayton@redhat.com>

A couple of small patches to make cephfs use errseq_t for reporting
writeback errors. This ensures that when a writeback error occurs
that it is reported to all file descriptions that were open at the
time. The first patch is what fixes the error reporting.

The second patch (which should probably be considered an RFC) adds a new
fault injection switch for cephfs that makes it throw writeback errors
even when the writes succeed. I have an xfstest that uses this to help
test error handling behavior in cephfs.

Jeff Layton (2):
  ceph: use errseq_t for writeback error reporting
  ceph: pagecache writeback fault injection switch

 fs/ceph/addr.c    | 7 +++++++
 fs/ceph/caps.c    | 2 +-
 fs/ceph/debugfs.c | 8 +++++++-
 fs/ceph/super.h   | 2 ++
 4 files changed, 17 insertions(+), 2 deletions(-)

-- 
2.13.3

             reply	other threads:[~2017-07-25 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 14:50 Jeff Layton [this message]
2017-07-25 14:50 ` [PATCH 1/2] ceph: use errseq_t for writeback error reporting Jeff Layton
2017-07-26 13:09   ` Yan, Zheng
2017-07-25 14:50 ` [PATCH 2/2] ceph: pagecache writeback fault injection switch Jeff Layton
2017-07-26 13:08   ` Yan, Zheng
2017-07-31 12:11     ` Jeff Layton

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=20170725145042.26219-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sage@redhat.com \
    --cc=zyan@redhat.com \
    /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