From: Christoph Hellwig <hch@infradead.org>
To: Shaohua Li <shli@fb.com>
Cc: linux-raid@vger.kernel.org, Kernel-team@fb.com,
songliubraving@fb.com, dan.j.williams@intel.com, neilb@suse.de
Subject: Re: [PATCH 3/3] raid5-cache: IO error handling
Date: Sun, 4 Oct 2015 07:44:40 -0700 [thread overview]
Message-ID: <20151004144440.GA19124@infradead.org> (raw)
In-Reply-To: <e9c915cf18d81f76e122a2533baeb68c56186d8f.1443653794.git.shli@fb.com>
On Wed, Sep 30, 2015 at 04:15:40PM -0700, Shaohua Li wrote:
> There are 3 places the raid5-cache dispatches IO. The discard IO error
> doesn't matter, so we ignore it. The superblock write IO error can be
> handled in MD core. The remaining are log write and flush. When the IO
> error happens, we simply fail all raid disks and continue the stripe
> state machine. The MD/raid5 core can handle it (for example, mark all
> disks faulty, report bio error and so on).
This introduces a use after free, which will always report an I/O error
when SLAB poisoning is enabled. The following patch needs to be folded
into it to fix that:
diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
index 430ce5c..8d93af1 100644
--- a/drivers/md/raid5-cache.c
+++ b/drivers/md/raid5-cache.c
@@ -239,11 +239,11 @@ static void r5l_log_endio(struct bio *bio)
struct r5l_log *log = io->log;
unsigned long flags;
- bio_put(bio);
-
if (bio->bi_error)
r5l_log_io_error(log);
+ bio_put(bio);
+
if (!atomic_dec_and_test(&io->pending_io))
return;
prev parent reply other threads:[~2015-10-04 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 23:15 [PATCH 0/3] raid5-cache fixes Shaohua Li
2015-09-30 23:15 ` [PATCH 1/3] raid5-cache: add trim support for log Shaohua Li
2015-10-01 4:41 ` Neil Brown
2015-09-30 23:15 ` [PATCH 2/3] md: don't export log device Shaohua Li
2015-10-01 4:45 ` Neil Brown
2015-09-30 23:15 ` [PATCH 3/3] raid5-cache: IO error handling Shaohua Li
2015-10-01 4:50 ` Neil Brown
2015-10-04 14:44 ` Christoph Hellwig [this message]
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=20151004144440.GA19124@infradead.org \
--to=hch@infradead.org \
--cc=Kernel-team@fb.com \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@fb.com \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).