Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753623AbdLDORZ (ORCPT ); Mon, 4 Dec 2017 09:17:25 -0500 Received: from mail-qt0-f170.google.com ([209.85.216.170]:38125 "EHLO mail-qt0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751990AbdLDORV (ORCPT ); Mon, 4 Dec 2017 09:17:21 -0500 X-Google-Smtp-Source: AGs4zMb7tfhpDhe6atn9FCGPya4obOwAkwyQK481DqyxFGbvNw40wPLikep2tNyA5t3xfZC2x80SdIZHmbZQcdZBOFc= MIME-Version: 1.0 In-Reply-To: <20171204135829.ubgthj4pq6f77pbj@redbean> References: <20171130023605.29568-1-mcgrof@kernel.org> <20171130023605.29568-4-mcgrof@kernel.org> <20171130131710.ccccf4alzrnvmlp3@redbean> <20171130183947.GI729@wotan.suse.de> <20171204135829.ubgthj4pq6f77pbj@redbean> From: Djalal Harouni Date: Mon, 4 Dec 2017 15:17:19 +0100 Message-ID: Subject: Re: module: add debugging alias parsing support To: Jessica Yu Cc: "Luis R. Rodriguez" , Jessica Yu , Rusty Russell , Kees Cook , mbenes@suse.cz, atomlin@redhat.com, Petr Mladek , hare@suse.com, James Morris , "Eric W. Biederman" , "David S . Miller" , Andrew Morton , Linus Torvalds , linux-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1757 Lines: 46 On Mon, Dec 4, 2017 at 2:58 PM, Jessica Yu wrote: > +++ Djalal Harouni [04/12/17 10:01 +0100]: >> >> On Thu, Nov 30, 2017 at 7:39 PM, Luis R. Rodriguez >> wrote: >>> >>> On Thu, Nov 30, 2017 at 02:17:11PM +0100, Jessica Yu wrote: >>>> >>>> Just some quick questions - are there any plans to use these in-kernel >>>> module aliases anywhere else? Or are you using them just for debugging? >>> >>> >>> As-is for now just debugging, but this could also more easily enable >>> folks to >>> prototype further evaluation of its uses. IMHO just having this at least >>> posted >>> online should suffice the later aspect of enabling folks to prototype. >> >> >> I confirm that, after the module auto-load discussion where it is >> clear that we need to improve the infrastructure, this debug >> information may save some time, maybe someone can automate a script go >> through modules and then on filesystem, > > >> however these patches may show >> which module lead to load another one, right ? on userspace if there >> are multiple dependencies it can be difficult I think. > > > Hm? I'm confused by what you mean here. The patchset just saves and > prints a module's aliases on module load if the debug option is > enabled. There's no dependency tracking here; that's modprobe's job. > And if you need to see which additional modules are being loaded as a > result of a module load there's already modprobe --verbose and > modules.dep.. Yes I was referring by the printing or kernel logs order, if two modules depend on same one, we know which first one triggered it, and in that context it will be a bit easier in the auto-loading context, maybe like crypto ones that can be triggered from anywhere. Thanks! -- tixxdz