On Thu, Aug 06 2020 at 9:21pm -0400,
Sagi Grimberg <sagi@xxxxxxxxxxx> wrote:
> Hey Mike,
>
> >>The point is: blk_path_error() has nothing to do with NVMe errors.
> >>This is dm-multipath logic stuck in the middle of the NVMe error
> >>handling code.
> >
> >No, it is a means to have multiple subsystems (to this point both SCSI
> >and NVMe) doing the correct thing when translating subsystem specific
> >error codes to BLK_STS codes.
>
> Not exactly, don't find any use of this in scsi. The purpose is to make
> sure that nvme and dm speak the same language.
SCSI doesn't need to do additional work to train a multipath layer
because dm-multipath _is_ SCSI's multipathing in Linux.
So ensuring SCSI properly classifies its error codes happens as a
side-effect of ensuring continued multipath functionality.
Hannes introduced all these differentiated error codes in block core
because of SCSI. NVMe is meant to build on the infrastructure that was
established.
> >If you, or others you name drop below, understood the point we wouldn't
> >be having this conversation. You'd accept the point of blk_path_error()
> >to be valid and required codification of what constitutes a retryable
> >path error for the Linux block layer.
>
> This incident is a case where the specific nvme status was designed
> to retry on the same path respecting the controller retry delay.
> And because nvme used blk_path_error at the time it caused us to use a
> non-retryable status to get around that. Granted, no one had
> dm-multipath in mind.
>
> So in a sense, there is consensus on changing patch 35038bffa87da
> _because_ nvme no longer uses blk_path_error. Otherwise it would break.
"break" meaning it would do failover instead of the more optimal local
retry to the same controller.
I see. Wish the header for commit 35038bffa87da touched on this even a
little bit ;)
But AFAICT the patch I provided doesn't compromise proper local retry --
as long as we first fix nvme_error_status() to return a retryable
BLK_STS for NVME_SC_CMD_INTERRUPTED -- which I assumed as a prereq.
Think of blk_path_error() as a more coarse-grained "is this retryable or
a hard failure?" check. So for NVME_SC_CMD_INTERRUPTED,
nvme_error_status() _should_ respond with something retryable (I'd
prefer BLK_STS_RESOURCE to be honest).
And then nvme_failover_req() is finer-grained; by returning false it now
allows short-circuiting failover and reverting back to NVMe's normal
controller based error recovery -- which it does for
NVME_SC_CMD_INTERRUPTED due to "default" case in nvme_failover_req().
And then the previous nvme_error_status() classification of retryable
BLK_STS obviously never gets returned up the IO stack; it gets thrown
away.
> >Any BLK_STS mapping of NVMe specific error codes would need to not screw
> >up by categorizing a retryable error as non-retryable (and vice-versa).
>
> But it is a special type of retryable. There is nothing that fits the
> semantics of the current behavior.
I agree. But that's fine actually.
And this issue is the poster-child for why properly supporting a duality
of driver-level vs upper level multipathing capabilities is pretty much
impossible unless a clean design factors out the different error classes
-- and local error retry is handled before punting to higher level
failover retry. Think if NVMe were to adopt a bit more disciplined
"local then failover" error handling it all gets easier.
This local retry _is_ NVMe specific. NVMe should just own retrying on
the same controller no matter what (I'll hope that such retry has
awareness to not retry indefinitely though!). And this has nothing to
do with multipathing, so the logic to handle it shouldn't be trapped in
nvme_failover_req().
I think NVMe can easily fix this by having an earlier stage of checking,
e.g. nvme_local_retry_req(), that shortcircuits ever getting to
higher-level multipathing consideration (be it native NVMe or DM
multipathing) for cases like NVME_SC_CMD_INTERRUPTED.
To be clear: the "default" case of nvme_failover_req() that returns
false to fallback to NVMe's "local" normal NVMe error handling -- that
can stay.. but a more explicit handling of cases like
NVME_SC_CMD_INTERRUPTED should be added to a nvme_local_retry_req()
check that happens before nvme_failover_req() in nvme_complete_rq().
This is where a patch will speak a thousand words... maybe ;)
> >Again, assuming proper testing, commit 35038bffa87 wouldn't have made it
> >upstream if NVMe still used blk_path_error().
>
> Agree.
>
> >Yes, your commit 764e9332098c0 needlessly removed NVMe's use of
> >blk_path_error(). If you're saying it wasn't needless please explain
> >why.
> >
> >> Fixes: 764e9332098c0 ("nvme-multipath: do not reset on unknown status")
> >> Cc: stable@xxxxxxxxxxxxxxxx
> >> Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>
> >> ---
> >> drivers/nvme/host/core.c | 9 +++++++--
> >> 1 file changed, 7 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> >> index 6585d57112ad..072f629da4d8 100644
> >> --- a/drivers/nvme/host/core.c
> >> +++ b/drivers/nvme/host/core.c
> >> @@ -290,8 +290,13 @@ void nvme_complete_rq(struct request *req)
> >> nvme_req(req)->ctrl->comp_seen = true;
> >>
> >> if (unlikely(status != BLK_STS_OK && nvme_req_needs_retry(req))) {
> >> - if ((req->cmd_flags & REQ_NVME_MPATH) && nvme_failover_req(req))
> >> - return;
> >> + if (blk_path_error(status)) {
> >> + if (req->cmd_flags & REQ_NVME_MPATH) {
> >> + if (nvme_failover_req(req))
> >> + return;
> >> + /* fallthru to normal error handling */
> >> + }
> >> + }
> >>
> >>This would basically undo the patch Hannes, Christoph, and I put together in
> >>commit 764e9332098c0. This patch greatly simplified and improved the
> >>whole nvme_complete_rq() code path, and I don't support undoing that change.
> >
> >Please elaborate on how I've undone anything?
>
> I think you're right, this hasn't undone the patch from John, but it
> breaks NVME_SC_CMD_INTERRUPTED error handling behavior.
Yes, again we'd need to first fix nvme_error_status() to return a
retryable BLK_STS for NVME_SC_CMD_INTERRUPTED -- which I assumed as a
prereq.
> >The only thing I may have done is forced NVMe to take more care about
> >properly translating its NVME_SC to BLK_STS in nvme_error_status().
> >Which is a good thing.
>
> I don't think there is an issue here of mistakenly converting an nvme
> status code to a wrong block status code. This conversion is there
> because there is no block status that give us the semantics we need
> which is apparently specific to nvme.
>
> I personally don't mind restoring blk_path_error to nvme, I don't
> particularly feel strong about it either. But for sure blk_path_error
> needs to first provide the semantics needed for NVME_SC_CMD_INTERRUPTED.
Hopefully it doesn't. As I discuss above with my "I think NVMe can
easily fix". NVMe should trap this class of "local" retryable error
_before_ going on to check if higher-level failover is needed. If it
does that: problem solved for both NVMe and DM multipathing. (could be
missing something though, I'll try to craft a patch later today to shake
it out).
> ...
>
> >Anyway, no new BLK_STS is needed at this point. More discipline with
> >how NVMe's error handling is changed is.
>
> Please read the above.
I agree we'd need a new BLK_STS only if NVMe cannot be made to trap
NVME_SC_CMD_INTERRUPTED for local retry _before_ considering path
failover.
> >If NVMe wants to ensure its
> >interface isn't broken regularly it _should_ use blk_path_error() to
> >validate future nvme_error_status() changes. Miscategorizing NVMe
> >errors to upper layers is a bug -- not open for debate.
>
> Again, don't agree is a Miscategorization nor a bug, its just something
> that is NVMe specific.
Right I understand.
Think it safe to assume these types of details are why Christoph wanted
to avoid the notion of native NVMe and DM multipathing having
compatible error handling. There was some wisdom with that position
(especially with native NVMe goals in mind). But if things are tweaked
slightly then both camps _can_ be made happy.
There just needs to be a willingness to work through the details,
defensiveness needs to be shed on both sides, so constructive
review/consideration of problems can happen. Think that has already
happened here with our exchange. I'm open to investing effort here if
others are up for humoring my attempt to explore fixing the issues in a
mutually beneficial way. What's the worst that can happen? My simple
patches might continue to be ignored? ;)
Mike
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
