From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938322AbdAKPks (ORCPT ); Wed, 11 Jan 2017 10:40:48 -0500 Received: from mail-io0-f194.google.com ([209.85.223.194]:35828 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751423AbdAKPjh (ORCPT ); Wed, 11 Jan 2017 10:39:37 -0500 MIME-Version: 1.0 X-Originating-IP: [212.51.149.109] In-Reply-To: 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> <20170111074338.rapmbctzne2da6vm@phenom.ffwll.local> From: Daniel Vetter Date: Wed, 11 Jan 2017 16:39:35 +0100 X-Google-Sender-Auth: C77q2iaNDAtNP8wfVDU-j7-MbjQ Message-ID: Subject: Re: [Intel-gfx] 4.10-rc2 oops in DRM connector code To: Dave Hansen Cc: Daniel Vetter , Jani Nikula , David Airlie , intel-gfx , dri-devel , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 11, 2017 at 4:24 PM, Dave Hansen wrote: > On 01/10/2017 11:43 PM, Daniel Vetter wrote: >> 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. > > It doesn't apply to mainline, with or without the substitution you suggest. > > Do you want that commit itself tested from -next? Hm, just cherry-picked it on top of Linus' latest 4.10 git, applies cleanly there. The substituation was for 4.9. I can send you the patch here, but seems all fine from what I can tell ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch