From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [RESEND PATCH] drm: Remove obsolete "This is gross" comment
Date: Tue, 26 Sep 2017 14:15:50 -0600 [thread overview]
Message-ID: <20170926201550.GA3729@Haneen> (raw)
In-Reply-To: <20170926052438.mql37gqx2i6sdmwo@phenom.ffwll.local>
On Tue, Sep 26, 2017 at 07:24:38AM +0200, Daniel Vetter wrote:
> On Thu, Sep 21, 2017 at 03:04:24PM -0600, Haneen Mohammed wrote:
> > Remove obsolete comment which was initially added in 2008 to annotate
> > that idr_find() was used before idr_remove() since idr_remove() didn't
> > use to return feedback. The comment now is irrelevant with
> > commit f6cd7daecff5 ("drm: Release driver references to handle before
> > making it available again").
>
> Personally I'd have added a lot more of the research story you've detailed
> in the private mails, just to show the work you've done. But the terse
> version is ok too ofc.
>
> > Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
>
> Applied to drm-misc-next, thanks.
> -Daniel
>
My bad, I was afraid to add too much details as I always read commit
message should be concise that I then ended up with too little.
I will try next time to add the necessary information.
Thank you!
Haneen
> > ---
> > drivers/gpu/drm/drm_gem.c | 9 ---------
> > 1 file changed, 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> > index c55f338..b9bddaa 100644
> > --- a/drivers/gpu/drm/drm_gem.c
> > +++ b/drivers/gpu/drm/drm_gem.c
> > @@ -282,15 +282,6 @@ drm_gem_handle_delete(struct drm_file *filp, u32 handle)
> > {
> > struct drm_gem_object *obj;
> >
> > - /* This is gross. The idr system doesn't let us try a delete and
> > - * return an error code. It just spews if you fail at deleting.
> > - * So, we have to grab a lock around finding the object and then
> > - * doing the delete on it and dropping the refcount, or the user
> > - * could race us to double-decrement the refcount and cause a
> > - * use-after-free later. Given the frequency of our handle lookups,
> > - * we may want to use ida for number allocation and a hash table
> > - * for the pointers, anyway.
> > - */
> > spin_lock(&filp->table_lock);
> >
> > /* Check if we currently have a reference on the object */
> > --
> > 2.7.4
> >
> > --
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170921210424.GA21951%40Haneen.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: gregkh@linuxfoundation.org,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Outreachy kernel] [RESEND PATCH] drm: Remove obsolete "This is gross" comment
Date: Tue, 26 Sep 2017 14:15:50 -0600 [thread overview]
Message-ID: <20170926201550.GA3729@Haneen> (raw)
In-Reply-To: <20170926052438.mql37gqx2i6sdmwo@phenom.ffwll.local>
On Tue, Sep 26, 2017 at 07:24:38AM +0200, Daniel Vetter wrote:
> On Thu, Sep 21, 2017 at 03:04:24PM -0600, Haneen Mohammed wrote:
> > Remove obsolete comment which was initially added in 2008 to annotate
> > that idr_find() was used before idr_remove() since idr_remove() didn't
> > use to return feedback. The comment now is irrelevant with
> > commit f6cd7daecff5 ("drm: Release driver references to handle before
> > making it available again").
>
> Personally I'd have added a lot more of the research story you've detailed
> in the private mails, just to show the work you've done. But the terse
> version is ok too ofc.
>
> > Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
>
> Applied to drm-misc-next, thanks.
> -Daniel
>
My bad, I was afraid to add too much details as I always read commit
message should be concise that I then ended up with too little.
I will try next time to add the necessary information.
Thank you!
Haneen
> > ---
> > drivers/gpu/drm/drm_gem.c | 9 ---------
> > 1 file changed, 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> > index c55f338..b9bddaa 100644
> > --- a/drivers/gpu/drm/drm_gem.c
> > +++ b/drivers/gpu/drm/drm_gem.c
> > @@ -282,15 +282,6 @@ drm_gem_handle_delete(struct drm_file *filp, u32 handle)
> > {
> > struct drm_gem_object *obj;
> >
> > - /* This is gross. The idr system doesn't let us try a delete and
> > - * return an error code. It just spews if you fail at deleting.
> > - * So, we have to grab a lock around finding the object and then
> > - * doing the delete on it and dropping the refcount, or the user
> > - * could race us to double-decrement the refcount and cause a
> > - * use-after-free later. Given the frequency of our handle lookups,
> > - * we may want to use ida for number allocation and a hash table
> > - * for the pointers, anyway.
> > - */
> > spin_lock(&filp->table_lock);
> >
> > /* Check if we currently have a reference on the object */
> > --
> > 2.7.4
> >
> > --
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170921210424.GA21951%40Haneen.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-26 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 21:04 [RESEND PATCH] drm: Remove obsolete "This is gross" comment Haneen Mohammed
2017-09-21 21:04 ` Haneen Mohammed
2017-09-21 21:16 ` [Outreachy kernel] " Julia Lawall
2017-09-21 21:16 ` Julia Lawall
2017-09-21 21:47 ` Haneen Mohammed
2017-09-21 21:47 ` Haneen Mohammed
2017-09-22 5:59 ` Julia Lawall
2017-09-22 5:59 ` Julia Lawall
2017-09-23 2:07 ` Haneen Mohammed
2017-09-26 5:24 ` Daniel Vetter
2017-09-26 5:24 ` Daniel Vetter
2017-09-26 20:15 ` Haneen Mohammed [this message]
2017-09-26 20:15 ` Haneen Mohammed
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=20170926201550.GA3729@Haneen \
--to=hamohammed.sa@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=seanpaul@chromium.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.