From: Kevin Wolf <mail@kevin-wolf.de>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Michael Tokarev <mjt@tls.msk.ru>,
Christoph Hellwig <hch@lst.de>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] block: fix sector comparism in multiwrite_req_compare
Date: Wed, 19 May 2010 23:09:07 +0200 [thread overview]
Message-ID: <201005192309.08252@kevin-wolf.de> (raw)
In-Reply-To: <4BF43F30.4050109@msgid.tls.msk.ru>
Am Mittwoch, 19. Mai 2010 21:42 schrieb Michael Tokarev:
> 19.05.2010 23:38, Christoph Hellwig wrote:
> > On Wed, May 19, 2010 at 11:26:58PM +0400, Michael Tokarev wrote:
> >> Now the question is if the previous patch by Avi is actually
> >> worth to apply -- I mean this one:
> >> [Qemu-devel] [PATCH +stable] block: don't attempt to merge overlapping
> >> requests
> >
> > No, that was just a hack, it shouldn't be applied.
>
> Actually it's not that obvious. If the actual problem
> here (besides the mis-comparison) is due to missing
> barriers or flushes. Avi asked a good question in that
> thread.
It's obvious that it's a hack. It doesn't fix anything, it just disables a
feature that didn't work. Good for debugging, but not something that you
would like to commit.
It's reasonable to include something like this when we know that something is
broken but we haven't found it yet - but I believe Christoph's patch is the
real fix. If anyone can still find a case that is "fixed" by Avi's patch, I
could be convinced to apply it anyway, but I'd prefer if I didn't have to.
Note that we actually don't have overlapping requests. It just looks like it
because the qsort call doesn't work correctly with the broken comparison
function, so lower sector numbers can come after higher ones.
Kevin
next prev parent reply other threads:[~2010-05-19 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 18:53 [Qemu-devel] [PATCH] block: fix sector comparism in multiwrite_req_compare Christoph Hellwig
2010-05-19 19:26 ` [Qemu-devel] " Michael Tokarev
2010-05-19 19:38 ` Christoph Hellwig
2010-05-19 19:42 ` Michael Tokarev
2010-05-19 21:09 ` Kevin Wolf [this message]
2010-05-20 6:09 ` Avi Kivity
2010-05-20 8:19 ` Kevin Wolf
2010-05-20 8:30 ` Avi Kivity
2010-05-20 8:50 ` Kevin Wolf
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=201005192309.08252@kevin-wolf.de \
--to=mail@kevin-wolf.de \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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).