From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
device-mapper development <dm-devel@redhat.com>,
linux-raid@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [dm-devel] [PATCH] block: add a bi_error field to struct bio
Date: Thu, 04 Jun 2015 05:53:43 -0400 [thread overview]
Message-ID: <yq1vbf3re8o.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1433338959-24808-2-git-send-email-hch@lst.de> (Christoph Hellwig's message of "Wed, 3 Jun 2015 15:42:39 +0200")
>>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:
Christoph> The first one has the drawback of only communicating a single
Christoph> possible error (-EIO), and the second one has the drawback of
Christoph> not beeing persistent when bios are queued up, and are not
Christoph> passed along from child to parent bio in the ever more
Christoph> popular chaining scenario.
Christoph> So add a new bi_error field to store an errno value directly
Christoph> in struct bio and remove the existing mechanisms to clean all
Christoph> this up.
Having the error status separate from the bio has been a major headache.
I am entirely in favor of this patch.
It was a big chunk of changes to read through but I did not spot any
obvious problems or polarity reversals. It would be nice to get the
respective fs/md/target driver folks to check their portions, though.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2015-06-04 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 13:42 [RFC] add a bi_error field Christoph Hellwig
[not found] ` <1433338959-24808-2-git-send-email-hch@lst.de>
2015-06-04 9:53 ` Martin K. Petersen [this message]
2015-06-04 15:31 ` block: add a bi_error field to struct bio Mike Snitzer
2015-06-10 8:11 ` Christoph Hellwig
2015-06-10 15:26 ` Mike Snitzer
2015-06-10 16:01 ` Mike Snitzer
2015-06-10 16:04 ` Christoph Hellwig
2015-06-10 16:50 ` Mike Snitzer
2015-06-10 18:29 ` anup modak
2015-06-11 7:53 ` Christoph Hellwig
2015-06-11 7:59 ` Christoph Hellwig
2015-06-10 2:50 ` [dm-devel] [PATCH] " Neil Brown
2015-06-10 8:45 ` Christoph Hellwig
2015-06-11 7:59 ` [RFC] add a bi_error field Liu Bo
2015-06-11 8:05 ` Liu Bo
2015-06-11 8:08 ` Christoph Hellwig
2015-06-11 9:42 ` Liu Bo
-- strict thread matches above, loose matches on Subject: below --
2015-07-20 13:29 add a bi_error field to struct bio V3 Christoph Hellwig
[not found] ` <1437398977-8492-2-git-send-email-hch@lst.de>
2015-07-21 8:19 ` [dm-devel] [PATCH] block: add a bi_error field to struct bio Hannes Reinecke
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=yq1vbf3re8o.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.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).