Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp389133imu; Fri, 21 Dec 2018 00:34:39 -0800 (PST) X-Google-Smtp-Source: ALg8bN6O3VNByJ8vE1Ip0LdZu9Xmr+ArvHvNHLnpoBD12pgtU8cbuAxBRnGIy2AAANYdKJmm0uOt X-Received: by 2002:a63:e5c:: with SMTP id 28mr1389734pgo.369.1545381279425; Fri, 21 Dec 2018 00:34:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545381279; cv=none; d=google.com; s=arc-20160816; b=N6aS5rOmxpGIodLwt8Q/2fJ2gaYWPnMH9MX0/tdVeavJXXuClUqoqgl+lAh459Tm1G ing4l1+RybwZNdipbm4sDz5KmTD1Zo4QFV4xx7D7y10meTxzD4Civ9wcySaGpV55/SbL AI/zVQtLXvVu309YTpcaYxy/axSupj5WJ4+C00YoDNkvHyOICw7rnPNmcuRoAZMPh+5f /xRiqUSx7p/BRZi28uGwNICDHGtM6+xl2V8wA4pqkIBgtMzz0YpUc3jQsPnendeJcdLb YsgB8/MpELYGLObFZLwiD6uBLP2bQ+ucTtJGmvsV3s6AC3dEVo4vjchfnMvZ7NI+AQEE G5TA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=B9J3875MunWhWbap4/bYP9PdAxItZFIM9nHWVhxYUjY=; b=Y18gBpu7nqOAncLJEipbEmS6YQo319AzPXVvR/6LgxOdP6HGEg1KndAhenrH/vFeBw lUe+Roax2dGW6RnBIhrRYVvcnaxfCIfo9opAhJciM7Ner3q1aHy9vU/hPB5dHXkBv0Ii K57yXmZBmurR48JbmfPUoty/DEnad5FK1MgQadoUcgeG0/+l+RN64r2t+mipB9FD3l6c P4dAMT3tobh8cViRUVCL/Qd9S94olEyfACNjb8/mFWwTpakwAJvgflJrwk4waAYzz13t XFLyj18yZkKNbNHq3P20YVOUjQdF2Tn3O0V3QGVB6owTHHfamQihhZAan2igTNJV8j1L 6Ruw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f13si22450607pln.368.2018.12.21.00.34.24; Fri, 21 Dec 2018 00:34:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390735AbeLUBx2 (ORCPT + 99 others); Thu, 20 Dec 2018 20:53:28 -0500 Received: from mga06.intel.com ([134.134.136.31]:36286 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730926AbeLUBx1 (ORCPT ); Thu, 20 Dec 2018 20:53:27 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Dec 2018 17:53:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,379,1539673200"; d="scan'208";a="131745556" Received: from pl-dbox.sh.intel.com (HELO intel.com) ([10.239.159.153]) by fmsmga001.fm.intel.com with ESMTP; 20 Dec 2018 17:53:25 -0800 Date: Fri, 21 Dec 2018 09:53:52 +0800 From: Philip Li To: Linus Torvalds Cc: kernel test robot , Christoph Hellwig , David Miller , linux-ide@vger.kernel.org, lkp@01.org, LKML Subject: Re: [LKP] [ide] ec7d9c9ce8: WARNING:at_fs/proc/generic.c:#remove_proc_entry Message-ID: <20181221015352.GA7734@intel.com> References: <20181220091931.zcibvplow3oxzacs@inn2.lkp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 20, 2018 at 08:05:28AM -0800, Linus Torvalds wrote: > On Thu, Dec 20, 2018 at 1:19 AM kernel test robot wrote: > > > > FYI, we noticed the following commit (built with gcc-7): > > > > commit: ec7d9c9ce897174243af4fcd201dbfc34df0f3a3 ("ide: replace ->proc_fops with ->proc_show") > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master > > Funky. How did the kernel test robot suddenly figure out an 8-month > old problem? Hi Linus, sorry for this late report. I can't figure out exact reason but some possible clues. The issue is captured by rcutoture which doesn't work well before. And only from late october, we have solved a few issues of the execution including the rootfs (yocto) it is using. And this issue is against an randconfig, i'm not sure whether the issue depends on a certain kconfig thus only be triggered or successfully bisected this time. > > > [ 44.180514] WARNING: CPU: 1 PID: 165 at fs/proc/generic.c:662 remove_proc_entry+0xb9/0x155 > > This is a warning for somebody doing "remove_proc_entry() on a name > that doesn't actually exist in that /proc directory. > > In this case, it does seem to be due to the named commit adding a > > + remove_proc_entry("settings", drive->proc); > > to ide_proc_unregister_device(), and looking at the patch I get the > feeling that it's due to a typo: the code *creates* the file called > "setting", but removes the file "settings". Note the missing "s" at > creation time. > > And yes, the name of the /proc file _should_be "settings", judging by > the rest of the patch. > > So it does seem to be a real bug. Nobody noticed until now? Why did > the test robot suddenly react to it? > > Linus > _______________________________________________ > LKP mailing list > LKP@lists.01.org > https://lists.01.org/mailman/listinfo/lkp