From: Dan Carpenter <dan.carpenter@oracle.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [patch] igbvf: integer overflow in igbvf_change_mtu()
Date: Thu, 22 Oct 2015 22:57:10 +0300 [thread overview]
Message-ID: <20151022195710.GY7289@mwanda> (raw)
In-Reply-To: <5628CE06.4070601@bfs.de>
Yeah, there is an integer overflow before we check but so far as I can
see it is harmless. The kernel is full of harmless integer overflows.
I sort of feel like this is the simplest way to write it and the other
ways feel over engineered and unweildy.
Care to propose a patch, though?
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] igbvf: integer overflow in igbvf_change_mtu()
Date: Thu, 22 Oct 2015 19:57:10 +0000 [thread overview]
Message-ID: <20151022195710.GY7289@mwanda> (raw)
In-Reply-To: <20151022091013.GC9202@mwanda>
Yeah, there is an integer overflow before we check but so far as I can
see it is harmless. The kernel is full of harmless integer overflows.
I sort of feel like this is the simplest way to write it and the other
ways feel over engineered and unweildy.
Care to propose a patch, though?
regards,
dan carpenter
next prev parent reply other threads:[~2015-10-22 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 9:10 [Intel-wired-lan] [patch] igbvf: integer overflow in igbvf_change_mtu() Dan Carpenter
2015-10-22 9:10 ` Dan Carpenter
2015-10-22 11:52 ` [Intel-wired-lan] " walter harms
2015-10-22 11:52 ` walter harms
2015-10-22 19:57 ` Dan Carpenter [this message]
2015-10-22 19:57 ` Dan Carpenter
2015-10-23 8:16 ` [Intel-wired-lan] " Dan Carpenter
2015-10-23 8:16 ` Dan Carpenter
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=20151022195710.GY7289@mwanda \
--to=dan.carpenter@oracle.com \
--cc=intel-wired-lan@osuosl.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 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.