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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CD861C19F2A for ; Thu, 11 Aug 2022 15:11:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=oP0fYPzPiNXp7NI7EXiPQr8ST1E9+u6YNZFoGENlypk=; b=iN8VP2Zx0hOiho Ixf9TyF84bVRD0D2hVNWy0isWvZF+Chl/bS/VHq6WjHJ+Pmq+G3kPVmwobc+zsZ+LhWRjumxS+mrE TPu8MX0XTls+DckJJAezeTNEx8Aty6EM9dEMp5OcDEMg5eQEevKB+i7EGfAL9HrewRMoSTSKZMuyP iphENeTiFH0T0f1qUEd8hTNRA0DMuHxQ24TJU8odiCt263rtOXtKEf6+KJy8pOLB0lxiWI6wGjNB/ AG6mZn7VgSuKjiVptZm1+ueafgxSvTIKSRbH1sKeiU7aYwqmGLnHPDfdIynvZGKAM60L5WJETInay mnK/02mn3uGSMWk1+xIw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oM9on-00Dhkg-3G; Thu, 11 Aug 2022 15:09:53 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oM9oj-00DhhM-OP for linux-arm-kernel@lists.infradead.org; Thu, 11 Aug 2022 15:09:51 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id C159168AA6; Thu, 11 Aug 2022 17:09:39 +0200 (CEST) Date: Thu, 11 Aug 2022 17:09:39 +0200 From: Christoph Hellwig To: Mike Leach Cc: Christoph Hellwig , "Suzuki K. Poulose" , Mathieu Poirier , Coresight ML , linux-arm-kernel Subject: Re: [PATCH v4 7/7] configfs: Fix LOCKDEP nesting issues with fragment semaphores Message-ID: <20220811150939.GA11253@lst.de> References: <20220706214338.19812-1-mike.leach@linaro.org> <20220706214338.19812-8-mike.leach@linaro.org> <20220728210158.GA25083@lst.de> <20220729132435.GA28515@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220811_080949_982573_AB596490 X-CRM114-Status: GOOD ( 13.27 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Aug 05, 2022 at 03:15:53PM +0100, Mike Leach wrote: > You are correct - in this patchset we are adding the use of a binary > attribute to load and unload Coresight configurations and features - > which action has a side effect of adding and removing entries in > particular sub-directories in our configfs sub-system. I don't think configfs was designed to be that dynamic. Especially the fact that a write to a binary attribute, which is intended to be just for passthrough to hardware is a bit concerning. >From your further description it sounds like this binary attribute is loading structured data interpreted by the kernel, which really isn't how binary attributes in configfs or sysfs are intended to be used. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel