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 X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B700C7618B for ; Fri, 26 Jul 2019 06:19:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 70ACC218DA for ; Fri, 26 Jul 2019 06:19:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="GLd+HRYD"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="X2x19VCL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725925AbfGZGT3 (ORCPT ); Fri, 26 Jul 2019 02:19:29 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:56438 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725869AbfGZGT2 (ORCPT ); Fri, 26 Jul 2019 02:19:28 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id F1AA360312; Fri, 26 Jul 2019 06:19:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1564121967; bh=tuIggQu6dJ8EB1vu2q34aTSvJWiTR8Y13JpxH0xY+wo=; h=To:From:Subject:Date:From; b=GLd+HRYDHP2wOvvCi3x5CMnCrbkekNVca/1Uy6EFC1nCpkic07IIESw3d6+OpkGiV YrSi7hXbtLvf/pdv6MER8/MhmWn7PENFg7DOzs0AhGAZQAPavApYcPD6HV1+mJtrje QKcfgbBUywp2EX35TCKd4CvSQLBHQcUE0qBqJx5k= Received: from [10.79.136.27] (blr-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.18.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: saiprakash.ranjan@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 8042660312; Fri, 26 Jul 2019 06:19:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1564121965; bh=tuIggQu6dJ8EB1vu2q34aTSvJWiTR8Y13JpxH0xY+wo=; h=To:From:Subject:Date:From; b=X2x19VCLEvSnVju/55PiYdcmUN1JnwmeqJKkA/dPQldYNU0NOKs2iRXnVAiZBtuK8 Qu/tG1PUc1KjCA+tagInUh/4FeAmNhjQwGUEKQNYmeLxdcaNgGX7nZOG8ZPOrBXfcU Rhl88eP28xhYgHGCrITkH09US2tE50OZOOipQn48= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 8042660312 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=saiprakash.ranjan@codeaurora.org To: Geert Uytterhoeven , Greg Kroah-Hartman , Mathieu Poirier , Suzuki K Poulose , Leo Yan , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org From: Sai Prakash Ranjan Subject: [Regression] Missing device nodes for ETR, ETF and STM after CONFIG_UEVENT_HELPER=n Message-ID: Date: Fri, 26 Jul 2019 11:49:19 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi, When trying to test my coresight patches, I found that etr,etf and stm device nodes are missing from /dev. Bisection gives this as the bad commit. 1be01d4a57142ded23bdb9e0c8d9369e693b26cc is the first bad commit commit 1be01d4a57142ded23bdb9e0c8d9369e693b26cc Author: Geert Uytterhoeven Date: Thu Mar 14 12:13:50 2019 +0100 driver: base: Disable CONFIG_UEVENT_HELPER by default Since commit 7934779a69f1184f ("Driver-Core: disable /sbin/hotplug by default"), the help text for the /sbin/hotplug fork-bomb says "This should not be used today [...] creates a high system load, or [...] out-of-memory situations during bootup". The rationale for this was that no recent mainstream system used this anymore (in 2010!). A few years later, the complete uevent helper support was made optional in commit 86d56134f1b67d0c ("kobject: Make support for uevent_helper optional."). However, if was still left enabled by default, to support ancient userland. Time passed by, and nothing should use this anymore, so it can be disabled by default. Signed-off-by: Geert Uytterhoeven Signed-off-by: Greg Kroah-Hartman drivers/base/Kconfig | 1 - 1 file changed, 1 deletion(-) Any idea on this? -Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation