From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Rob Clark <robclark@freedesktop.org>,
dri-devel@lists.freedesktop.org,
Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH libdrm 2/2] xf86drmMode: smoke-test the atomic API
Date: Mon, 7 Sep 2015 16:06:41 +0300 [thread overview]
Message-ID: <20150907130641.GZ29811@intel.com> (raw)
In-Reply-To: <1441619586-12098-2-git-send-email-emil.l.velikov@gmail.com>
On Mon, Sep 07, 2015 at 10:53:06AM +0100, Emil Velikov wrote:
> As going through the modetest patches for atomic support I've noticed
> that if we pass NULL for the drmModeAtomicReqPtr argument we'll crash.
>
> So let's handle things appropriately if the user forgot to check the
> return value of drmModeAtomicAlloc and drmModeAtomicDuplicate or made a
> typo somewhere along the way.
I'm not sure hand-holding the user to such an extent is actually useful.
OTOH I guess one NULL check per function call isn't all that expensive
either.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Rob Clark <robclark@freedesktop.org>
> Cc: Daniel Stone <daniels@collabora.com>
> Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
> ---
> xf86drmMode.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/xf86drmMode.c b/xf86drmMode.c
> index 23800dd..ab6b519 100644
> --- a/xf86drmMode.c
> +++ b/xf86drmMode.c
> @@ -1189,6 +1189,9 @@ drmModeAtomicReqPtr drmModeAtomicDuplicate(drmModeAtomicReqPtr old)
> {
> drmModeAtomicReqPtr new;
>
> + if (!old)
> + return NULL;
> +
> new = drmMalloc(sizeof *new);
> if (!new)
> return NULL;
> @@ -1213,6 +1216,9 @@ drmModeAtomicReqPtr drmModeAtomicDuplicate(drmModeAtomicReqPtr old)
>
> int drmModeAtomicMerge(drmModeAtomicReqPtr base, drmModeAtomicReqPtr augment)
> {
> + if (!base)
> + return -EINVAL;
> +
> if (!augment || augment->cursor == 0)
> return 0;
>
> @@ -1239,12 +1245,15 @@ int drmModeAtomicMerge(drmModeAtomicReqPtr base, drmModeAtomicReqPtr augment)
>
> int drmModeAtomicGetCursor(drmModeAtomicReqPtr req)
> {
> + if (!req)
> + return -EINVAL;
> return req->cursor;
> }
>
> void drmModeAtomicSetCursor(drmModeAtomicReqPtr req, int cursor)
> {
> - req->cursor = cursor;
> + if (req)
> + req->cursor = cursor;
> }
>
> int drmModeAtomicAddProperty(drmModeAtomicReqPtr req,
> @@ -1252,6 +1261,9 @@ int drmModeAtomicAddProperty(drmModeAtomicReqPtr req,
> uint32_t property_id,
> uint64_t value)
> {
> + if (!req)
> + return -EINVAL;
> +
> if (req->cursor >= req->size_items) {
> drmModeAtomicReqItemPtr new;
>
> @@ -1309,6 +1321,9 @@ int drmModeAtomicCommit(int fd, drmModeAtomicReqPtr req, uint32_t flags,
> int obj_idx = -1;
> int ret = -1;
>
> + if (!req)
> + return -EINVAL;
> +
> if (req->cursor == 0)
> return 0;
>
> --
> 2.5.0
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-07 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 9:53 [PATCH libdrm 1/2] automake: set --enable-valgrind during make distcheck Emil Velikov
2015-09-07 9:53 ` [PATCH libdrm 2/2] xf86drmMode: smoke-test the atomic API Emil Velikov
2015-09-07 13:06 ` Ville Syrjälä [this message]
2015-09-10 11:10 ` Emil Velikov
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=20150907130641.GZ29811@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=robclark@freedesktop.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.