From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [patch] drbd: silence underflow warning in read_in_block()
Date: Wed, 7 May 2014 12:22:19 +0200 [thread overview]
Message-ID: <20140507102219.GE32422@soda.linbit> (raw)
In-Reply-To: <20140506112832.GA25561@mwanda>
On Tue, May 06, 2014 at 02:28:32PM +0300, Dan Carpenter wrote:
> My static checker warns that "data_size" could be negative and underflow
> the limit check. The code looks suspicious but I don't know if it is a
> real bug.
"real life" bug only if you manage to receive corrupted data.
The maximum sent payload is DRBD_BIO_MAX_SIZE
which is an architecture independend constant (1U << 20).
Patch is correct, but while at it, we should revisit all "int data_size",
and make them all unsigned int...
Lars
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/block/drbd/drbd_receiver.c b/drivers/block/drbd/drbd_receiver.c
> index b6c8aaf..15daf86d 100644
> --- a/drivers/block/drbd/drbd_receiver.c
> +++ b/drivers/block/drbd/drbd_receiver.c
> @@ -1528,7 +1528,7 @@ read_in_block(struct drbd_peer_device *peer_device, u64 id, sector_t sector,
> struct drbd_peer_request *peer_req;
> struct page *page;
> int dgs, ds, err;
> - int data_size = pi->size;
> + unsigned int data_size = pi->size;
> void *dig_in = peer_device->connection->int_dig_in;
> void *dig_vv = peer_device->connection->int_dig_vv;
> unsigned long *data;
prev parent reply other threads:[~2014-05-07 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:28 [patch] drbd: silence underflow warning in read_in_block() Dan Carpenter
2014-05-06 11:28 ` Dan Carpenter
2014-05-06 11:28 ` [Drbd-dev] " Dan Carpenter
2014-05-07 10:22 ` Lars Ellenberg [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=20140507102219.GE32422@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.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: link
Be 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.