Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp3256787pxt; Mon, 9 Aug 2021 22:16:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw6AKV+5n7aa/3eoUKjheRZyYo5sm4N9IB9cdWokCph/HyI3Ulq1ZCKvSxWkEy2muY8V379 X-Received: by 2002:a02:cd02:: with SMTP id g2mr4699454jaq.42.1628572602256; Mon, 09 Aug 2021 22:16:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628572602; cv=none; d=google.com; s=arc-20160816; b=jsPaGP88oTz99I0G5m1n/6x0inVMQ9Xoxha9N3p/T0+P24OQslLXkHGuS6eWrXZsDj g/JnoxZnRCMaju1FJ4tveFwNvAfaSJkDY4ptD06cgodGZ9BzN6a46wFpIlP8IHOdNTyZ W40kGJxNhq00oaT60Zmys2DtejPlKCv5jriJ19K3HU4++P7X2sC2ghDLDTKgQGHxKJmv Ys7HuXf47rYvkjH1mOv/yRzQJH/dTMcoT5o2+onqWEXTGQ9tmZ+BupZSeNBpJB4lVpKQ y8HsDHVLRFQxfcO7m7/pcjI+lFZfhmhgU4xAtXL1odk9fIMEzWf6UwibCqH5V8g21D3W GDGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=CwKNOnnzAd5qosOD7HgKOb5hYzfIZY7Sz4p7lyYQkDQ=; b=dD7Q1Dopjn6NgwzRMyBHkcJlvNkUMeHA/i+Er5wIMnrPYP/FCTH/6MHnJzu3qOSE6H q12hYvPCghLZpZXSCLdT4ERVM5sNzJYSoMkktm0kb+wCXv4r86k3TxAcYPitzIHsDvDB +IjcoCyPoLZQpbOfJD8uPNJDpGtZpZDj7dBghu4YKcwN+X0jLLrsB1tEWh+fe5O9tDf5 t/7cPk4pUAiS9+/SrBoylK4tIX/qsMTadIAfVjKU4QXduhcdHMkNU1/5xiHwI8ZQoTux uxU65FAt1FVbfDufAX4U/z0s3G4AaZr0tzr7yRfRPMLDxwGsFRKe+YHlQu4EqDQXZBZ9 So6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Aw1PwLw9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b15si21609843ioj.7.2021.08.09.22.16.26; Mon, 09 Aug 2021 22:16:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Aw1PwLw9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237074AbhHIXvI (ORCPT + 99 others); Mon, 9 Aug 2021 19:51:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231127AbhHIXvH (ORCPT ); Mon, 9 Aug 2021 19:51:07 -0400 Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EE66CC0613D3; Mon, 9 Aug 2021 16:50:45 -0700 (PDT) Received: by mail-oi1-x234.google.com with SMTP id bi32so2328936oib.2; Mon, 09 Aug 2021 16:50:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CwKNOnnzAd5qosOD7HgKOb5hYzfIZY7Sz4p7lyYQkDQ=; b=Aw1PwLw9e6HEVLxXhk3SYCBTevOdoaIoFpu5z454kaPWRiGrPfArMajweYsgcLKbzk Imp4itmpEiA+3FGketSR7PifxV6klN1X7wdOV8tp5BICwZtSPUnkFUYUnhH/puiFckkW 1owHYvHPyAoPARvslIafJjcn/4RIdhVJ0Bc32zc71tDqTV5oykqqsJOgtUfcqJitBWVL RghRsH8xnfUNvK2oQlex1pdgJooRD0CQeGSABCvcUkkILPupJIlrkitKO/7TGNzA/ZGH I6qV0Qvj260FojJGnK5wmkBtJSht0PHFoI81D06mAQCrIiQVUGxwBN0BD7p3xBiDmVeK z5Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CwKNOnnzAd5qosOD7HgKOb5hYzfIZY7Sz4p7lyYQkDQ=; b=SY0FCAMT5ZBUDy+qJVPEXfoUlk91UISAgZ/A6gjFLXlAO5jCzJzQK+BuQ1H19Q/+wz 7nuY0EEI02k87pBiKU3+WK+rdw6jbumbTo4GscoWzIodmOgUsY6YIDNngo5iIzO5ApG9 HQWAIGf8HqbolfjFmIluKOVD8i1/EtKjvhzRNxzSYKI4wbd0oqMP9P6skI0yhlvUg67C JVwXO0LyH/VyIHNlbLvhdrIfR9BN/Drhp5geXSjkGina8EpwhTytcz2N6QdtBezKeRDn V6X3WrLg8n2m+s+JjSyrfWIcJZ50XtypAPIKa1MfvgciPshAmwbInVW43eudCXDHc3kn Xl4g== X-Gm-Message-State: AOAM5320w90JMwN74L4oCO5Hlv3gG4ZVOB4qjMKUXHY0U6dix8yqs6PT DKDm7GzEPXRpkYbGekPzfbY= X-Received: by 2002:a05:6808:601:: with SMTP id y1mr16033359oih.27.1628553045406; Mon, 09 Aug 2021 16:50:45 -0700 (PDT) Received: from ian.penurio.us ([47.184.51.90]) by smtp.gmail.com with ESMTPSA id u8sm496600oiw.52.2021.08.09.16.50.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 Aug 2021 16:50:44 -0700 (PDT) Subject: Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers To: =?UTF-8?Q?Marek_Beh=c3=ban?= , Greg KH , hch@lst.de Cc: pali@kernel.org, linux-block@vger.kernel.org, linux-leds@vger.kernel.org, axboe@kernel.dk, pavel@ucw.cz, linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org References: <20210809033217.1113444-1-arequipeno@gmail.com> <20210809205633.4300bbea@thinkpad> <81c128a1-c1b8-0f1e-a77b-6704bade26c0@gmail.com> <20210810004331.0f0094a5@thinkpad> From: Ian Pilcher Message-ID: <7b5f3509-5bcd-388b-8d3b-4ea95a9483ad@gmail.com> Date: Mon, 9 Aug 2021 18:50:44 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210810004331.0f0094a5@thinkpad> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/9/21 5:43 PM, Marek BehĂșn wrote: > I confess that I am not very familiar with internal blkdev API. It's mainly a matter of symbol visibility. See this thread from a few months ago: https://www.spinics.net/lists/linux-leds/msg18244.html Now ... my code currently lives in block/, so there isn't actually anything technically preventing it from iterating through the block devices. The reactions to Enzo's patch (which you can see in that thread) make me think that anything that iterates through all block devices is likely to be rejected, but maybe I'm reading too much into it. Greg / Christoph - (As you were the people who expressed disapproval of Enzo's patch to export block_class and disk_type ...) Can you weigh in on the acceptability of iterating through the block devices (searching by name) from LED trigger code within the block subsystem (i.e. no new symbols would need to be exported)? This would allow the trigger to implement the sysfs API that Marek and Pavel want. Thanks! -- ======================================================================== In Soviet Russia, Google searches you! ========================================================================