From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] block: fix sector comparism in multiwrite_req_compare
Date: Wed, 19 May 2010 20:53:10 +0200 [thread overview]
Message-ID: <20100519185309.GA27591@lst.de> (raw)
The difference between the start sectors of two requests can be larger
than the size of the "int" type, which can lead to a not correctly
sorted multiwrite array and thus spurious I/O errors and filesystem
corruption due to incorrect request merges.
So instead of doing the cute sector arithmetics trick spell out the
exact comparisms.
Spotted by Kevin Wolf based on a testcase from Michael Tokarev.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: qemu/block.c
===================================================================
--- qemu.orig/block.c 2010-05-19 17:08:24.970255636 +0200
+++ qemu/block.c 2010-05-19 17:17:34.227006021 +0200
@@ -1933,7 +1933,19 @@ static void multiwrite_cb(void *opaque,
static int multiwrite_req_compare(const void *a, const void *b)
{
- return (((BlockRequest*) a)->sector - ((BlockRequest*) b)->sector);
+ const BlockRequest *req1 = a, *req2 = b;
+
+ /*
+ * Note that we can't simply subtract req2->sector from req1->sector
+ * here as that could overflow the return value.
+ */
+ if (req1->sector > req2->sector) {
+ return 1;
+ } else if (req1->sector < req2->sector) {
+ return -1;
+ } else {
+ return 0;
+ }
}
/*
next reply other threads:[~2010-05-19 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 18:53 Christoph Hellwig [this message]
2010-05-19 19:26 ` [Qemu-devel] Re: [PATCH] block: fix sector comparism in multiwrite_req_compare Michael Tokarev
2010-05-19 19:38 ` Christoph Hellwig
2010-05-19 19:42 ` Michael Tokarev
2010-05-19 21:09 ` Kevin Wolf
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=20100519185309.GA27591@lst.de \
--to=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).