From: Olaf Hering <olaf@aepfle.de> To: Eric Blake <eblake@redhat.com> Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>, Stefano Stabellini <sstabellini@kernel.org>, "open list:All patches CC here" <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>, "open list:X86" <xen-devel@lists.xensource.com>, Anthony Perard <anthony.perard@citrix.com> Subject: Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges Date: Fri, 18 Nov 2016 18:41:09 +0100 [thread overview] Message-ID: <20161118174108.GF5717@aepfle.de> (raw) In-Reply-To: <42ca6186-ca47-3c63-d2e0-54f2ed9f4be7@redhat.com> [-- Attachment #1: Type: text/plain, Size: 1066 bytes --] On Fri, Nov 18, Eric Blake wrote: > On 11/18/2016 04:24 AM, Olaf Hering wrote: > > + /* Overflowing byte limit? */ > > + if ((sec_start + sec_count) > ((INT64_MAX + INT_MAX) >> BDRV_SECTOR_BITS)) { > This is undefined. INT64_MAX + anything non-negative overflows int64, The expanded value used to be stored into a uint64_t before it was used here. A "cleanup" introduced this error. Thanks for spotting. > If you are trying to detect guests that make a request that would cover > more than INT64_MAX bytes, you can simplify. Besides, for as much > storage as there is out there, I seriously doubt ANYONE will ever have > 2^63 bytes addressable through a single device. Why not just write it as: > > if ((INT64_MAX >> BDRV_SECTOR_BITS) - sec_count < sec_start) { That would always be false I think. I will resubmit with this: if ((sec_start + sec_count) > (INT64_MAX >> BDRV_SECTOR_BITS)) { Regarding the cast for ->req, it has type blkif_request_t, but the pointer needs to be assigned to type blkif_request_discard_t. Olaf [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 163 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de> To: Eric Blake <eblake@redhat.com> Cc: Kevin Wolf <kwolf@redhat.com>, "open list:X86" <xen-devel@lists.xensource.com>, qemu-block@nongnu.org, "open list:All patches CC here" <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>, Stefano Stabellini <sstabellini@kernel.org>, Anthony Perard <anthony.perard@citrix.com> Subject: Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges Date: Fri, 18 Nov 2016 18:41:09 +0100 [thread overview] Message-ID: <20161118174108.GF5717@aepfle.de> (raw) In-Reply-To: <42ca6186-ca47-3c63-d2e0-54f2ed9f4be7@redhat.com> [-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --] On Fri, Nov 18, Eric Blake wrote: > On 11/18/2016 04:24 AM, Olaf Hering wrote: > > + /* Overflowing byte limit? */ > > + if ((sec_start + sec_count) > ((INT64_MAX + INT_MAX) >> BDRV_SECTOR_BITS)) { > This is undefined. INT64_MAX + anything non-negative overflows int64, The expanded value used to be stored into a uint64_t before it was used here. A "cleanup" introduced this error. Thanks for spotting. > If you are trying to detect guests that make a request that would cover > more than INT64_MAX bytes, you can simplify. Besides, for as much > storage as there is out there, I seriously doubt ANYONE will ever have > 2^63 bytes addressable through a single device. Why not just write it as: > > if ((INT64_MAX >> BDRV_SECTOR_BITS) - sec_count < sec_start) { That would always be false I think. I will resubmit with this: if ((sec_start + sec_count) > (INT64_MAX >> BDRV_SECTOR_BITS)) { Regarding the cast for ->req, it has type blkif_request_t, but the pointer needs to be assigned to type blkif_request_discard_t. Olaf [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 163 bytes --] [-- Attachment #2: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-18 17:44 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-18 10:24 [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges Olaf Hering 2016-11-18 10:24 ` Olaf Hering 2016-11-18 10:30 ` [Qemu-devel] " Olaf Hering 2016-11-18 10:30 ` Olaf Hering 2016-11-23 10:49 ` [Qemu-devel] " Olaf Hering 2016-11-23 10:49 ` Olaf Hering 2016-11-23 11:02 ` [Qemu-devel] " Olaf Hering 2016-11-23 11:02 ` Olaf Hering 2016-11-23 18:51 ` [Qemu-devel] " Stefano Stabellini 2016-11-23 18:51 ` Stefano Stabellini 2016-11-18 13:43 ` [Qemu-devel] " Eric Blake 2016-11-18 13:43 ` Eric Blake 2016-11-18 14:19 ` Olaf Hering 2016-11-18 14:19 ` Olaf Hering 2016-11-18 14:35 ` Eric Blake 2016-11-18 14:35 ` Eric Blake 2016-11-18 15:38 ` Kevin Wolf 2016-11-18 15:38 ` Kevin Wolf 2016-11-18 16:39 ` Eric Blake 2016-11-18 16:39 ` Eric Blake 2016-11-18 17:41 ` Olaf Hering [this message] 2016-11-18 17:41 ` Olaf Hering 2016-11-18 18:50 ` Eric Blake 2016-11-18 18:50 ` Eric Blake 2016-11-22 16:12 ` Olaf Hering 2016-11-22 16:12 ` Olaf Hering 2016-11-22 16:32 ` Eric Blake 2016-11-22 16:32 ` Eric Blake 2016-11-22 17:00 ` Olaf Hering 2016-11-22 17:00 ` Olaf Hering 2016-11-22 17:11 ` Eric Blake 2016-11-22 17:11 ` Eric Blake
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=20161118174108.GF5717@aepfle.de \ --to=olaf@aepfle.de \ --cc=anthony.perard@citrix.com \ --cc=eblake@redhat.com \ --cc=kwolf@redhat.com \ --cc=mreitz@redhat.com \ --cc=qemu-block@nongnu.org \ --cc=qemu-devel@nongnu.org \ --cc=sstabellini@kernel.org \ --cc=xen-devel@lists.xensource.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.