public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] misleading error message
Date: Thu, 02 Dec 2004 07:33:41 -0500	[thread overview]
Message-ID: <41AF0BA5.5080901@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0411302329550.13758@yvahk01.tjqt.qr>

Random side thoughts..

a) is there a simple way to search for symbols in a running kernel's 
memory area that
b) can differentiate between module and static, and if so
c) is there an interest in a tiny tool that scripts  could use to 
determine existing support?

I want to be able to request information about a whooplesnoople without 
it triggering a module load request, to determine if it's compiled in 
statically.  I want to be able to distinguish static a static 
whooplesnoople from a modularly loaded whooplesnoople.

i.e.
Scott ~$ kernfunctionexists "iptables"
builtin

Other possible values:
module
not found

The tool would do the work of doing a lookup on "iptables" to match it 
with a certain name.  I.e "irda" would be resolved to a known proper 
irda_function_name() value.

The purpose of this is not to be able to research any given function 
name in the kernel, but to look for major support functions such as 
iptables.

David


  reply	other threads:[~2004-12-02 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 19:45 PROBLEM: misleading error message Bebel
2004-11-30 20:56 ` Misleading " Jan Engelhardt
2004-11-30 23:36   ` Greg KH
2004-11-30 21:58 ` PROBLEM: misleading " Jesper Juhl
2004-11-30 22:10   ` [RFC] " Jan Engelhardt
2004-11-30 22:29     ` Jesper Juhl
2004-11-30 22:27       ` Phil Oester
2004-11-30 22:29       ` Lee Revell
2004-11-30 22:30       ` Jan Engelhardt
2004-12-02 12:33         ` David Ford [this message]
2004-12-02 23:40           ` Ken Moffat
2004-12-03 10:35             ` Jan Engelhardt
2004-12-05  0:32           ` Horst von Brand

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=41AF0BA5.5080901@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.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