public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Jessica Yu <jeyu@kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	jeyu@redhat.com, rusty@rustcorp.com.au, keescook@chromium.org,
	tixxdz@gmail.com, mbenes@suse.cz, atomlin@redhat.com,
	pmladek@suse.com, hare@suse.com, james.l.morris@oracle.com,
	ebiederm@xmission.com, davem@davemloft.net,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: module: add debugging alias parsing support
Date: Thu, 30 Nov 2017 19:39:47 +0100	[thread overview]
Message-ID: <20171130183947.GI729@wotan.suse.de> (raw)
In-Reply-To: <20171130131710.ccccf4alzrnvmlp3@redbean>

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.

You're right that one can find aliases in userspace. One of the benefits
of having this dump things on the kernel log is just that you can easily
get the aliases printed out for all modules actually loaded for your system
without much effort. I did find this useful when debugging and found it much
more convenient than scraping modules one by one by hand in userspace.

I had this implemented since 2016, and I had some ideas to use them in a
functional way, however I first had to knock out a series of of fixes for
kernel/kmod.c and setting up a baseline test infrastructure for kmod
(tools/testing/selftests/kmod/ and lib/test_kmod.c) as such I hadn't had time
to yet come around and finish benchmarking the alias enhancement ideas I had
started evaluating.

As such having aliases in-kernel currently are only useful for debugging and
prototyping.

  Luis

  reply	other threads:[~2017-11-30 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  2:36 [PATCH 0/3] module: process aliasing when debugging Luis R. Rodriguez
2017-11-30  2:36 ` [PATCH 1/3] module: use goto errors on check_modinfo() and layout_and_allocate() Luis R. Rodriguez
2017-11-30  2:36 ` [PATCH 2/3] module: add helper get_modinfo_idx() Luis R. Rodriguez
2017-11-30  2:36 ` [PATCH 3/3] module: add debugging alias parsing support Luis R. Rodriguez
2017-11-30 13:17   ` Jessica Yu
2017-11-30 18:39     ` Luis R. Rodriguez [this message]
2017-12-04  9:01       ` Djalal Harouni
2017-12-04 13:58         ` Jessica Yu
2017-12-04 14:17           ` Djalal Harouni
2017-12-07 19:51         ` Luis R. Rodriguez
2018-03-10 14:09 ` [PATCH 0/3] module: process aliasing when debugging Luis R. Rodriguez

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=20171130183947.GI729@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=hare@suse.com \
    --cc=james.l.morris@oracle.com \
    --cc=jeyu@kernel.org \
    --cc=jeyu@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tixxdz@gmail.com \
    --cc=torvalds@linux-foundation.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