From: Jens Axboe <axboe@suse.de>
To: Steven Dake <sdake@mvista.com>
Cc: neilb@cse.unsw.edu.au, Matthew Wilcox <willy@debian.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [PATCH] fixes defect with kernel BUG using multipath on 2.6.0-test5
Date: Sat, 27 Sep 2003 10:33:03 +0200 [thread overview]
Message-ID: <20030927083303.GE3416@suse.de> (raw)
In-Reply-To: <1064622862.4779.38.camel@persist.az.mvista.com>
On Fri, Sep 26 2003, Steven Dake wrote:
> Folks,
> Thanks Matt and Jens for the debug help on the multipath problem. I now
> have a patch (attached) which solves the problem and makes multipath
> work properly. There are two types of "flags" that are used in a block
> io request, bi_flags, and bi_rw. bi_flags is used for flags to the
> block level code, and bi_rw is used for flags to the low level device
> drivers. The code in the multipath driver used the wrong flag in the
> wrong field. In this case, the flag FASTFAIL (value 3) was being set to
> the bi_flags field. FASTFAIL is a hint to the low level driver that it
> should try to fail out quickly. Unfortunately, the value 3 is also
> BIO_SEG_VALID, which is a flag to the block subsystem that the segments
> shouldn't be recalculated. The result was that the wrong field was set,
> telling the block layer not to recalculate the segments resulting in
> phys and hw segments of 0. Not good.
>
> Neil can you send upstream ?
Auch good catch! I'm sorry to say this is actually my fault...
--
Jens Axboe
prev parent reply other threads:[~2003-09-27 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1064541435.4763.51.camel@persist.az.mvista.com>
[not found] ` <20030926121703.GG24824@parcelfarce.linux.theplanet.co.uk>
[not found] ` <20030926122646.GA15415@suse.de>
[not found] ` <1064607249.4779.1.camel@persist.az.mvista.com>
2003-09-27 0:34 ` [PATCH] fixes defect with kernel BUG using multipath on 2.6.0-test5 Steven Dake
2003-09-27 8:33 ` Jens Axboe [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=20030927083303.GE3416@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=sdake@mvista.com \
--cc=willy@debian.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).