From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/xe/xe_devcoredump: Check NULL before dereferencing
Date: Thu, 21 Mar 2024 15:42:07 -0400 [thread overview]
Message-ID: <ZfyNj45WtMMztLsH@intel.com> (raw)
In-Reply-To: <20240320052239.3249222-1-himal.prasad.ghimiray@intel.com>
On Wed, Mar 20, 2024 at 10:52:39AM +0530, Himal Prasad Ghimiray wrote:
> Dereference 'coredump' to access 'xe_devcoredump_snapshot' only if
> 'coredump' is not NULL,
>
> v2
> - Fix commit messages.
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_devcoredump.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c
> index 0fcd30680323..83a1f3cd37cf 100644
> --- a/drivers/gpu/drm/xe/xe_devcoredump.c
> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c
> @@ -74,17 +74,20 @@ static ssize_t xe_devcoredump_read(char *buffer, loff_t offset,
> size_t count, void *data, size_t datalen)
> {
> struct xe_devcoredump *coredump = data;
> + if (!coredump)
> + return -ENODATA;
> +
> struct xe_device *xe = coredump_to_xe(coredump);
> + /* Our device is gone already... */
> + if (!xe)
> + return -ENODEV;
> +
> struct xe_devcoredump_snapshot *ss = &coredump->snapshot;
> struct drm_printer p;
> struct drm_print_iterator iter;
> struct timespec64 ts;
> int i;
>
> - /* Our device is gone already... */
> - if (!data || !coredump_to_xe(coredump))
> - return -ENODEV;
> -
> /* Ensure delayed work is captured before continuing */
> flush_work(&ss->work);
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-03-21 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 5:22 [PATCH v2] drm/xe/xe_devcoredump: Check NULL before dereferencing Himal Prasad Ghimiray
2024-03-20 5:51 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-20 5:51 ` ✓ CI.checkpatch: " Patchwork
2024-03-20 5:52 ` ✓ CI.KUnit: " Patchwork
2024-03-20 6:03 ` ✓ CI.Build: " Patchwork
2024-03-20 6:06 ` ✓ CI.Hooks: " Patchwork
2024-03-20 6:07 ` ✓ CI.checksparse: " Patchwork
2024-03-20 6:31 ` ✓ CI.BAT: " Patchwork
2024-03-21 19:42 ` Rodrigo Vivi [this message]
2024-03-21 19:45 ` [PATCH v2] " Souza, Jose
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=ZfyNj45WtMMztLsH@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox