From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762219AbdAKHnt (ORCPT ); Wed, 11 Jan 2017 02:43:49 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:34784 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757988AbdAKHnn (ORCPT ); Wed, 11 Jan 2017 02:43:43 -0500 Date: Wed, 11 Jan 2017 08:43:39 +0100 From: Daniel Vetter To: Dave Hansen Cc: Daniel Vetter , Jani Nikula , David Airlie , intel-gfx , dri-devel , Linux Kernel Mailing List Subject: Re: [Intel-gfx] 4.10-rc2 oops in DRM connector code Message-ID: <20170111074338.rapmbctzne2da6vm@phenom.ffwll.local> Mail-Followup-To: Dave Hansen , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx , dri-devel , Linux Kernel Mailing List References: <7fd16549-1349-a9e5-ceff-9aa6f748caae@intel.com> <20170109101516.y3acaev5ujbjugwl@phenom.ffwll.local> <16a1e734-667c-5d9a-c418-555b1f13e446@intel.com> <20170110103157.xuz7mefbv3fw5hlc@phenom.ffwll.local> <30c171a4-e144-778e-4fe2-d342602c3940@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30c171a4-e144-778e-4fe2-d342602c3940@intel.com> X-Operating-System: Linux phenom 4.8.0-1-amd64 User-Agent: NeoMutt/20161126 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote: > On 01/10/2017 02:31 AM, Daniel Vetter wrote: > > commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e > > Author: Daniel Vetter > > Date: Sun Dec 18 14:35:45 2016 +0100 > > > > drm: prevent double-(un)registration for connectors > > > > Lack of that would perfectly explain that oops ... Otherwise still no idea > > what's going wrong. > > No... That's not in mainline as far as I can see. Should I test with > it applied? Hm, I guess failed to cc: stable that one properly, iirc we decided the race fix is too academic and can't be hit in reality ;-) Testing would be great. Probably conflicts because we extracted drm_connector.c only recently, but running s/drm_connector\.c/drm_crtc.c/ over the diff and then applying with some fudge should take care of that. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch