[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b531d35a-631f-c84c-831d-9ce6cff02436@users.sourceforge.net>
Date: Mon, 2 Jul 2018 10:34:08 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Kees Cook <keescook@...omium.org>, Rob Clark <robdclark@...il.com>,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
linux-arm-msm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>, David Airlie <airlied@...ux.ie>,
Jordan Crouse <jcrouse@...eaurora.org>
Subject: Re: [PATCH] drm/msm/adreno: Remove VLA usage
> @@ -91,12 +93,13 @@ static int zap_shader_load_mdt(struct msm_gpu *gpu, const char *fwname)
> ret = qcom_mdt_load(dev, fw, fwname, GPU_PAS_ID,
> mem_region, mem_phys, mem_size, NULL);
> } else {
> - char newname[strlen("qcom/") + strlen(fwname) + 1];
> + char *newname;
>
> - sprintf(newname, "qcom/%s", fwname);
> + newname = kasprintf(GFP_KERNEL, "qcom/%s", fwname);
>
> ret = qcom_mdt_load(dev, fw, newname, GPU_PAS_ID,
> mem_region, mem_phys, mem_size, NULL);
I have taken another look also at this update suggestion.
Now I wonder why the return value is not checked for the added name construction
in the way as it is specified for the function “adreno_request_fw”.
Will another condition check make sense at this place?
Regards,
Markus
Powered by blists - more mailing lists