From: Alan Cox <alan@linux.intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [bug report] staging/atomisp: Add support for the Intel IPU v2
Date: Mon, 20 Mar 2017 14:07:04 +0000 [thread overview]
Message-ID: <1490018824.24765.54.camel@linux.intel.com> (raw)
In-Reply-To: <20170313123445.GA9464@mwanda>
> 674
> 675 /* To avoid owerflows when calling the efivar API */
> 676 if (*out_len > ULONG_MAX)
> ^^^^^^^^^^^^^^^^^^^^
> This is impossible. Was UINT_MAX intended?
I am really not sure. The only case I can imagine is 32bit EFI on a
64bit system, but even then I don't see what the check is about at this
point.
Alan
prev parent reply other threads:[~2017-03-20 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 12:34 [bug report] staging/atomisp: Add support for the Intel IPU v2 Dan Carpenter
2017-03-20 14:07 ` Alan Cox [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=1490018824.24765.54.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-media@vger.kernel.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).