From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Eyal Itkin <eyalit@checkpoint.com>,
dri-devel@lists.freedesktop.org,
Cihangir Akturk <cakturk@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] drm: udl: Properly check framebuffer mmap offsets
Date: Thu, 22 Mar 2018 09:03:00 +0100 [thread overview]
Message-ID: <20180322080300.GA28877@kroah.com> (raw)
In-Reply-To: <20180322065959.GF14155@phenom.ffwll.local>
On Thu, Mar 22, 2018 at 07:59:59AM +0100, Daniel Vetter wrote:
> Does anyone working on overflow-proof integers? That would make a lot of
> this code so much simpler if we could just ask the compiler to carry the
> oferflow bit around for a given expression and then check that and bail
> with -EINVAL.
That would be nice, but no, I don't think that's part of any C standard
work that I have heard of :(
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-22 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 15:45 [PATCH] drm: udl: Properly check framebuffer mmap offsets Greg Kroah-Hartman
2018-03-22 6:59 ` Daniel Vetter
2018-03-22 8:03 ` Greg Kroah-Hartman [this message]
2018-03-22 9:54 ` Daniel Vetter
2018-03-22 9:54 ` Daniel Vetter
2018-03-23 0:14 ` Kees Cook
2018-03-26 8:26 ` Daniel Vetter
2018-03-26 8:26 ` Daniel Vetter
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=20180322080300.GA28877@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=cakturk@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eyalit@checkpoint.com \
--cc=krzk@kernel.org \
--cc=mingo@kernel.org \
--cc=thomas.lendacky@amd.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.