From: Damien Lespiau <damien.lespiau@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm: Kernel Crash in drm_unlock
Date: Tue, 31 Mar 2015 14:28:45 +0100 [thread overview]
Message-ID: <20150331132845.GG8912@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20150331132532.GK6354@phenom.ffwll.local>
On Tue, Mar 31, 2015 at 03:25:32PM +0200, Daniel Vetter wrote:
> > ---
> > drivers/gpu/drm/drm_lock.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_lock.c b/drivers/gpu/drm/drm_lock.c
> > index f645268..80253a7 100644
> > --- a/drivers/gpu/drm/drm_lock.c
> > +++ b/drivers/gpu/drm/drm_lock.c
> > @@ -156,6 +156,14 @@ int drm_unlock(struct drm_device *dev, void *data, struct drm_file *file_priv)
>
> Also please rebase to latest upstream when submitting patches to the
> public (the function is now called drm_legacy_unlock).
and include dri-devel@lists.freedesktop.org for core drm patches.
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-31 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 8:09 [PATCH] drm: Kernel Crash in drm_unlock Peter Antoine
2015-03-31 8:09 ` [PATCH] drm: Possible lock priority escalation Peter Antoine
2015-03-31 15:53 ` shuang.he
2015-03-31 8:09 ` [PATCH] drm: Fixes unsafe deference in locks Peter Antoine
2015-03-31 18:20 ` shuang.he
2015-03-31 13:24 ` [PATCH] drm: Kernel Crash in drm_unlock shuang.he
2015-03-31 13:25 ` Daniel Vetter
2015-03-31 13:28 ` Damien Lespiau [this message]
2015-03-31 13:34 ` Antoine, Peter
2015-03-31 14:00 ` Daniel Vetter
2015-03-31 14:21 ` Antoine, Peter
2015-04-15 14:22 ` Antoine, Peter
2015-04-16 7:30 ` Daniel Vetter
2015-03-31 13:35 ` Damien Lespiau
2015-03-31 13:38 ` Antoine, Peter
2015-03-31 13:44 ` Damien Lespiau
2015-03-31 13:47 ` Antoine, Peter
2015-03-31 13:53 ` He, Shuang
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=20150331132845.GG8912@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@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 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.