From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Enlist running kernel modules information
Date: Wed, 4 Dec 2019 09:52:07 +0530 [thread overview]
Message-ID: <20191204041543.GA1086470@ArchLinux> (raw)
In-Reply-To: <CAK7LNASyrYv+pufwe4CfiNvd7NtriLw=FRdLOtu7CrbmZDSVHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2860 bytes --]
On 12:10 Wed 04 Dec 2019, Masahiro Yamada wrote:
>On Tue, Dec 3, 2019 at 6:49 PM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>>
>> This is new file to show running kernel modules list.One line bash
>> script.
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> scripts/kernel_modules_info.sh | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>> create mode 100755 scripts/kernel_modules_info.sh
>>
>> diff --git a/scripts/kernel_modules_info.sh b/scripts/kernel_modules_info.sh
>> new file mode 100755
>> index 000000000000..f005c47a3aa6
>> --- /dev/null
>> +++ b/scripts/kernel_modules_info.sh
>> @@ -0,0 +1,23 @@
>> +#!/bin/bash -
>> +#SPDX-License-Identifier: GPL-2.0
>> +#===============================================================================
>> +#
>> +# FILE: kernel_modules_info.sh
>> +#
>> +# USAGE: ./kernel_modules_info.sh
>> +#
>> +# DESCRIPTION: Running kernel modules information.
>> +#
>> +# OPTIONS: ---
>> +# REQUIREMENTS: awk
>> +# BUGS: ---
>> +# NOTES: ---
>> +# AUTHOR: Bhaskar Chowdhury (https://about.me/unixbhaskar), unixbhaskar@gmail.com
>> +# ORGANIZATION: Independent
>> +# CREATED: 12/03/2019 13:52
>> +# REVISION: ---
>> +#===============================================================================
>> +
>> +set -o nounset # Treat unset variables as an error
>> +
>> +awk '{print $1}' "/proc/modules" | xargs modinfo | awk '/^(filename|desc|depends)/'
>
>
>
>I want to see a good reason (e.g. useful for other developers) for upstreaming.
>This script looks like your custom script, which you can maintain locally.
I think the usefulness comes from developers wants to see what are the
modules are using by the running kernel in formatted way.
This is very simple way to enlist all the modules with descriptions of
it.So , they can easily parse it with other scripts.
I believe you have already copy and paste the single line on your
terminal to see the output it produces, if not, I have already sent a
mail which includes the out of it.
If and only if, no other tool or mechanism(which might have skips my
eyes and knowledge) to find and display information this way.
Kindly, share me the other way , you can achieve that. This is a generic
script,and expecting stuff in common place, so everybody can use it.No,
special requirement is needed.
Here is little output,if you missed my other mail with it...
filename:/lib/modules/5.4.1-arch1-1ArchLinux-5.4.1/kernel/drivers/usb/host/xhci-pci.ko.xz
description: xHCI PCI Host Controller Driver
depends: xhci-hcd
These output can be parse by other scripts too(cliche...sorry) ..
Thanks,
Bhaskar
>
>
>--
>Best Regards
>Masahiro Yamada
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-04 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 9:48 [PATCH 1/2] Enlist running kernel modules information Bhaskar Chowdhury
2019-12-04 3:10 ` Masahiro Yamada
2019-12-04 4:22 ` Bhaskar Chowdhury [this message]
2019-12-04 13:48 ` Enrico Weigelt, metux IT consult
2019-12-05 3:30 ` Bhaskar Chowdhury
2019-12-04 15:07 ` David Sterba
2019-12-05 3:25 ` Bhaskar Chowdhury
[not found] ` <CAK7LNARdOGfvc_8TMX+KbJQ1DRGy8_xZsdDye1ZrvimSS1VoFQ@mail.gmail.com>
2019-12-06 8:10 ` Bhaskar Chowdhury
2019-12-06 15:48 ` Enrico Weigelt, metux IT consult
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191204041543.GA1086470@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox