From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Revert of the IO stat fix
Date: Mon, 25 Oct 2010 00:03:52 +0200 [thread overview]
Message-ID: <1287957832.24074.19.camel@maxim-laptop> (raw)
In-Reply-To: <4CC49A4B.8010300@fusionio.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
On Sun, 2010-10-24 at 22:42 +0200, Jens Axboe wrote:
> On 2010-10-24 22:35, Linus Torvalds wrote:
> > On Sun, Oct 24, 2010 at 1:09 PM, Jens Axboe <jaxboe@fusionio.com> wrote:
> >>
> >> The fix for cross-partition merges screwing up disk stats turns out
> >> to be problematic on various levels. Lets revert this one so we have
> >> time to come up with a proper solution for this.
> >
> > Hmm.. I think the reverted patch looks like it really is the right
> > thing to do, so I hate reverting it this early. What were the problems
> > with it?
> >
> > Btw, one thing that seems to be missing in the original commit (which
> > is not necessarily the reason for the trouble, of course), is that
> > elv_rq_merge_ok() seems to not check the partition. As far as I can
> > tell, we should have a
> >
> > if (req->part != bio->bi_bdev->bd_part)
> > return 0;
> >
> > there, no? And you should _not_ set rq->part in "drive_stat_acct()",
> > you should set it from bio->bi_bdev->bd_part when you create the
> > request.
> >
> > (And if it is NULL, just don't do partition accounting at all)
> >
> > Hmm? What am I missing? What were the bugs?
>
> The patch itself is sound, the problems are around the area of it not
> really liking non-elevator devices with the elv_quiesce_start/end()
> parts. I had the below patch for that, but then I could not decide
> whether we were fully safe on queue free after talking to Vivek about
> it.
>
> So that shows up as an oops on removal of mspro for instance, and loop
> throws a fit as well. Coverage of the bug is too large just to let side
> idle for a few days.
Btw I had that bug reproduced 100% for all removeable devices I have.
(xD, ms, usb).
Attached logs for each.
Best regards,
Maxim Levitsky
[-- Attachment #2: logs.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 38268 bytes --]
next prev parent reply other threads:[~2010-10-24 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 20:09 Jens Axboe
2010-10-24 20:35 ` Linus Torvalds
2010-10-24 20:42 ` Jens Axboe
2010-10-24 20:44 ` Jens Axboe
2010-10-24 20:53 ` Linus Torvalds
2010-11-23 10:01 ` Jerome Marchand
2010-11-30 17:01 ` Jerome Marchand
2010-10-24 22:03 ` Maxim Levitsky [this message]
2010-10-25 0:07 ` Linus Torvalds
2010-10-25 0:55 ` Maxim Levitsky
2010-10-25 1:30 ` Maxim Levitsky
2010-10-25 19:24 ` Vivek Goyal
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=1287957832.24074.19.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®