public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Julian Orth <ju.orth@gmail.com>
Cc: "Michel Dänzer" <michel.daenzer@mailbox.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
	"Rob Clark" <robin.clark@oss.qualcomm.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/syncobj: Fix handle <-> fd ioctls with dirty stack
Date: Tue, 3 Mar 2026 18:05:05 +0100	[thread overview]
Message-ID: <55846862-3482-4b01-bf57-2201ce642aab@linux.intel.com> (raw)
In-Reply-To: <CAHijbEXTPSLSADqet1=P1FV6jvoa5yGEprOuYtpQWUq_y5uT2A@mail.gmail.com>

Hey,

Den 2026-03-03 kl. 17:54, skrev Julian Orth:
> On Tue, Mar 3, 2026 at 5:40 PM Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com> wrote:
>>
>> There is precedence in the ioctl, the pad member is checked against zero for the same reason.
> 
> I don't believe that this is comparable. Developers of code developed
> against an older kernel could look at the kernel and see that the pad
> field was checked against zero. They could not see the same for fields
> that didn't exist at the time.
> 
>> The check was there because it is invalid to pass when IMPORT/EXPORT_SYNC_FILE was not set.
>>
>> This is what I would recommend instead:
>>
>> [...]
>>
>> +       if (!(args->flags & DRM_SYNCOBJ_HANDLE_TO_FD_FLAGS_TIMELINE) &&
>> +           !(args->flags & DRM_SYNCOBJ_HANDLE_TO_FD_FLAGS_EXPORT_SYNC_FILE) &&
>> +             args->point)
>> +               return -EINVAL;
> 
> Should it not be
> 
> +       if ((!(args->flags & DRM_SYNCOBJ_HANDLE_TO_FD_FLAGS_TIMELINE) ||
> +           !(args->flags & DRM_SYNCOBJ_HANDLE_TO_FD_FLAGS_EXPORT_SYNC_FILE)) &&
> +             args->point)
> +               return -EINVAL;
Yeah copy paste error. :)

      parent reply	other threads:[~2026-03-03 17:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 12:34 [PATCH] drm/syncobj: Fix handle <-> fd ioctls with dirty stack Julian Orth
2026-03-02 11:27 ` Christian König
2026-03-02 11:54   ` Dmitry Osipenko
2026-03-03 11:17 ` Michel Dänzer
2026-03-03 11:23   ` Julian Orth
2026-03-03 11:38     ` Michel Dänzer
2026-03-03 11:41       ` Julian Orth
2026-03-03 14:53 ` Maarten Lankhorst
2026-03-03 14:59   ` Christian König
2026-03-03 15:15     ` Maarten Lankhorst
2026-03-03 15:21       ` Julian Orth
2026-03-03 17:02         ` Michel Dänzer
2026-03-03 15:29     ` Michel Dänzer
2026-03-03 15:36       ` Julian Orth
2026-03-03 16:40         ` Maarten Lankhorst
2026-03-03 16:54           ` Julian Orth
2026-03-03 17:04             ` Michel Dänzer
2026-03-03 17:11               ` Julian Orth
2026-03-03 17:18                 ` Michel Dänzer
2026-03-03 17:30                   ` Julian Orth
2026-03-03 17:44                     ` Maarten Lankhorst
2026-03-03 18:53                       ` Michel Dänzer
2026-03-03 19:12                         ` Julian Orth
2026-03-04  9:57                           ` Maarten Lankhorst
2026-03-04 11:15                           ` Michel Dänzer
2026-03-04 11:25                             ` Julian Orth
2026-03-04 11:47                               ` Michel Dänzer
2026-03-04 12:32                                 ` Julian Orth
2026-03-04 14:29                                   ` Michel Dänzer
2026-03-04 14:35                                     ` Julian Orth
2026-03-05  9:47                               ` Maarten Lankhorst
2026-03-03 17:40                   ` Maarten Lankhorst
2026-03-03 17:44                     ` Julian Orth
2026-03-03 19:58                       ` David Laight
2026-03-04 10:35                         ` Maarten Lankhorst
2026-03-03 17:05             ` Maarten Lankhorst [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=55846862-3482-4b01-bf57-2201ce642aab@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ju.orth@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel.daenzer@mailbox.org \
    --cc=mripard@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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