From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 952F8C433F5 for ; Thu, 31 Mar 2022 13:29:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236843AbiCaNbI (ORCPT ); Thu, 31 Mar 2022 09:31:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236845AbiCaNa7 (ORCPT ); Thu, 31 Mar 2022 09:30:59 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AA7FA5BD25; Thu, 31 Mar 2022 06:29:11 -0700 (PDT) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 5E4261F7AC; Thu, 31 Mar 2022 13:29:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1648733350; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GUXy5x8tlG26+gzs1ElKHuL93ZTpc0/Sxiw74ELvX2k=; b=UECbFTNZgZW/3XWZih3zr74DEw2KxItlzbQIBqG+AC043KOTzSPoh39VxF/LPfq7awvHM6 OdbQJzUagf5Q1keXxjzBCuBncxW4mA/pSIQTgB8QppkPSMpI1/UGk7h30c02/I6qJOfxG5 1U833MVRMHJQKhYKFT7VNpdYu1Vv/Tc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1648733350; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GUXy5x8tlG26+gzs1ElKHuL93ZTpc0/Sxiw74ELvX2k=; b=t/pxLIv7n65eVOVJ2VHGgg8xay4mGPg4q4Q4w3exYAfJJCNAaOBc8j8vD/w052kLD1bf4e wxcZHA/g+ZGLggDw== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id 4C919A3B96; Thu, 31 Mar 2022 13:29:10 +0000 (UTC) Date: Thu, 31 Mar 2022 15:29:10 +0200 Message-ID: From: Takashi Iwai To: Heikki Krogerus Cc: Won Chung , Jaroslav Kysela , Takashi Iwai , Mika Westerberg , Benson Leung , Prashant Malani , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v2] sound/hda: Add NULL check to component match callback function In-Reply-To: References: <20220330211913.2068108-1-wonchung@google.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 31 Mar 2022 11:45:47 +0200, Takashi Iwai wrote: > > On Thu, 31 Mar 2022 11:34:38 +0200, > Heikki Krogerus wrote: > > > > On Thu, Mar 31, 2022 at 11:28:20AM +0200, Takashi Iwai wrote: > > > On Thu, 31 Mar 2022 11:25:43 +0200, > > > Heikki Krogerus wrote: > > > > > > > > On Thu, Mar 31, 2022 at 11:12:55AM +0200, Takashi Iwai wrote: > > > > > > > > - if (!strcmp(dev->driver->name, "i915") && > > > > > > > > + if (dev->driver && !strcmp(dev->driver->name, "i915") && > > > > > > > > > > > > > > Can NULL dev->driver be really seen? I thought the components are > > > > > > > added by the drivers, hence they ought to have the driver field set. > > > > > > > But there can be corner cases I overlooked. > > > > > > > > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > > > Takashi > > > > > > > > > > > > Hi Takashi, > > > > > > > > > > > > When I try using component_add in a different driver (usb4 in my > > > > > > case), I think dev->driver here is NULL because the i915 drivers do > > > > > > not have their component master fully bound when this new component is > > > > > > registered. When I test it, it seems to be causing a crash. > > > > > > > > > > Hm, from where component_add*() is called? Basically dev->driver must > > > > > be already set before the corresponding driver gets bound at > > > > > __driver_probe_deviec(). So, if the device is added to component from > > > > > the corresponding driver's probe, dev->driver must be non-NULL. > > > > > > > > The code that declares a device as component does not have to be the > > > > driver of that device. > > > > > > > > In our case the components are USB ports, and they are devices that > > > > are actually never bind to any drivers: drivers/usb/core/port.c > > > > > > OK, that's what I wanted to know. It'd be helpful if it's more > > > clearly mentioned in the commit log. > > > > Agree. > > > > > BTW, the same problem must be seen in MEI drivers, too. > > > > Wasn't there a patch for those too? I lost track... > > I don't know, I just checked the latest Linus tree. > > And, looking at the HD-audio code, I still wonder how NULL dev->driver > can reach there. Is there any PCI device that is added to component > without binding to a driver? We have dev_is_pci() check at the > beginning, so non-PCI devices should bail out there... Further reading on, I'm really confused. How data=NULL can be passed to this function? The data argument is the value passed from the component_match_add_typed() call in HD-audio driver, hence it must be always the snd_hdac_bus object. And, I guess the i915 string check can be omitted completely, at least, for HD-audio driver. It already have a check of the parent of the device and that should be enough. Takashi