AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Guchun Chen <guchun.chen@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Fix ENOSYS with better fitting error codes in radeon_gem.c
Date: Thu, 27 Jul 2023 11:30:11 +0200	[thread overview]
Message-ID: <c747870e-dbc4-8802-304e-241069efbdba@amd.com> (raw)
In-Reply-To: <20230726141636.2474263-1-srinivasan.shanmugam@amd.com>

Am 26.07.23 um 16:16 schrieb Srinivasan Shanmugam:
> Replace the error code from 'ENOSYS' to 'EOPNOTSUPP' for unimplemented
> radeon_gem_pread_ioctl & radeon_gem_pwrite_ioctl
>
> Fixes the following:
>
> WARNING: ENOSYS means 'invalid syscall nr' and nothing else.

Mhm, it might be better to just completely remove those.

They also allow an authorized client to spam the system logs.

Christian.

>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
> ---
>   drivers/gpu/drm/radeon/radeon_gem.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_gem.c b/drivers/gpu/drm/radeon/radeon_gem.c
> index d0119c5f7eb3..358d19242f4b 100644
> --- a/drivers/gpu/drm/radeon/radeon_gem.c
> +++ b/drivers/gpu/drm/radeon/radeon_gem.c
> @@ -316,7 +316,7 @@ int radeon_gem_pread_ioctl(struct drm_device *dev, void *data,
>   {
>   	/* TODO: implement */
>   	DRM_ERROR("unimplemented %s\n", __func__);
> -	return -ENOSYS;
> +	return -EOPNOTSUPP;
>   }
>   
>   int radeon_gem_pwrite_ioctl(struct drm_device *dev, void *data,
> @@ -324,7 +324,7 @@ int radeon_gem_pwrite_ioctl(struct drm_device *dev, void *data,
>   {
>   	/* TODO: implement */
>   	DRM_ERROR("unimplemented %s\n", __func__);
> -	return -ENOSYS;
> +	return -EOPNOTSUPP;
>   }
>   
>   int radeon_gem_create_ioctl(struct drm_device *dev, void *data,


      parent reply	other threads:[~2023-07-27  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 14:16 [PATCH] drm/radeon: Fix ENOSYS with better fitting error codes in radeon_gem.c Srinivasan Shanmugam
2023-07-26 18:30 ` Alex Deucher
2023-07-27  9:30 ` Christian König [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=c747870e-dbc4-8802-304e-241069efbdba@amd.com \
    --to=christian.koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=guchun.chen@amd.com \
    --cc=srinivasan.shanmugam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox