Skip to contentSkip to conversation

query_modules syscall gone? Any replacement?

DISCUSSION Bodo Eggert 5 participants 10 messages Sep 9, 2005 – Sep 13, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 2 lines · iSteve

May I then ask, why is the query_module syscall gone? And more
importantly, what replaces it, if anything?

I don't know query_module, but ls -laR /sys/module might do the job.

Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
#2 lore raw

I'm aware of the sysfs interface -- but neither /proc/modules nor /sys/module/ actually really supplement the query_module api...

- iSteve

Quoted 8 lines · Bodo Eggert
Quoted 2 lines · iSteve

May I then ask, why is the query_module syscall gone? And more
importantly, what replaces it, if anything?

I don't know query_module, but ls -laR /sys/module might do the job.

#3 lore raw
In reply to Bodo Eggert

Okay, so, I have so far gathered:

- the whole module interface change between 2.4 and 2.6 was because
some security concerns, most of the stuff (loading module etc.) moved towards kernel
- query_module is gone, there is no syscall similar in function but
with different name
- losing of query_module also prevents binary-only modules
(guesswork@work)
- /proc/modules and /sys/module interface doesn't by far supply what
query_module could do

My questions are:
a) Are my observations correct? Where did I go wrong?
b) Is there any planned replacement of query_module, or extendind sysfs or procfs module interface?
c) Wouldn't revamping query_module also allow binary-only modules, therefore easier decisions for vendors, whether to support Linux?

Thanks in advance and sorry for these probably quite silly questions.

- iSteve

#4 lore raw
Quoted 5 lines · iSteve

Okay, so, I have so far gathered:

- the whole module interface change between 2.4 and 2.6 was because
some security concerns, most of the stuff (loading module etc.) moved towards kernel

I thought it was due to raciness or locking concerns, but I'm not sure about that.

Quoted 2 lines

- query_module is gone, there is no syscall similar in function but
with different name

Right.

Quoted 2 lines

- losing of query_module also prevents binary-only modules
(guesswork@work)

Nope, they are not prevented. However, there is a Tainted flag that is set when one is loaded (and that flag is never cleared).

Quoted 2 lines

- /proc/modules and /sys/module interface doesn't by far supply what
query_module could do

Can you state succinctly exactly what you are trying to do?

Quoted 4 lines

My questions are:
a) Are my observations correct? Where did I go wrong?
b) Is there any planned replacement of query_module, or extendind sysfs or procfs module interface?

Haven't heard of one.

Quoted 1 line

c) Wouldn't revamping query_module also allow binary-only modules,

they are still possible.

Quoted 5 lines

therefore easier decisions for vendors, whether to support Linux?

Thanks in advance and sorry for these probably quite silly questions.

- iSteve

Signature · 1 line
~Randy
#5 lore raw
Quoted 3 lines

Nope, they are not prevented. However, there is a Tainted flag that is set when one is loaded (and that flag is never cleared).

Okay, I've been wrong in my conclusion and I gotta read some fine manual about how the modules actually work -- could you recommend me some in particular?

Quoted 4 lines
Quoted 2 lines

- /proc/modules and /sys/module interface doesn't by far supply what
query_module could do

Can you state succinctly exactly what you are trying to do?

I would like to be able to query symbols of a loaded module, get list of and list of dependencies of loaded module from an app, preferably without having to parse a file...

#6 lore raw
Quoted 7 lines · iSteve
Quoted 3 lines

Nope, they are not prevented. However, there is a Tainted flag that is set when one is loaded (and that flag is never cleared).

Okay, I've been wrong in my conclusion and I gotta read some fine manual about how the modules actually work -- could you recommend me some in particular?

Nope, there is precious little doc about modules, especially in 2.6.

There is a FAQ, but I doubt that it answers many of your questions.
http://www.kernel.org/pub/linux/kernel/people/rusty/modules/FAQ

You could try LDD3, but I don't see much there that would help you either.
http://lwn.net/Kernel/LDD3/

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

- /proc/modules and /sys/module interface doesn't by far supply what
query_module could do

Can you state succinctly exactly what you are trying to do?

I would like to be able to query symbols of a loaded module, get list of and list of dependencies of loaded module from an app, preferably without having to parse a file...

No, no syscall to do that. Looks like it will require reading and parsing files.

And you answered my "what" question clearly, so I have one more. Why? for what purpose, to what end? What are you tring to accomplish?

Thanks,

Signature · 1 line
~Randy
#7 lore raw
Quoted 11 lines
Quoted 3 lines

I would like to be able to query symbols of a loaded module, get list of and list of dependencies of loaded module from an app, preferably without having to parse a file...

No, no syscall to do that. Looks like it will require reading and parsing files.

And you answered my "what" question clearly, so I have one more. Why? for what purpose, to what end? What are you tring to accomplish?

The files so far provided still do not seem to give these informations though...

Part of the project I'm working on -- click-click ui for handling modules, with some perks: in this case, getting info about loaded modules that I hoped to obtain via query_module.

Oh, and one more question: There were no particular issues with query_module, or were they? If there weren't, why wasn't it kept?

#8 lore raw
Quoted 8 lines · iSteve
Quoted 8 lines
Quoted 3 lines

I would like to be able to query symbols of a loaded module, get list of and list of dependencies of loaded module from an app, preferably without having to parse a file...

No, no syscall to do that. Looks like it will require reading and parsing files.

Quoted 6 lines
Quoted 3 lines

And you answered my "what" question clearly, so I have one more. Why? for what purpose, to what end? What are you tring to accomplish?

The files so far provided still do not seem to give these informations though...

Right, I don't see dependency ("requires") info there, just "using" info.

Quoted 6 lines

Part of the project I'm working on -- click-click ui for handling modules, with some perks: in this case, getting info about loaded modules that I hoped to obtain via query_module.

Oh, and one more question: There were no particular issues with query_module, or were they? If there weren't, why wasn't it kept?

I don't recall.
You can try searching the lkml archives or asking Rusty Russell:

MODULE SUPPORT
P: Rusty Russell
M: [email protected]
L: [email protected]
S: Maintained

One quick search produced this, but it doesn't help you any:
http://marc.theaimsgroup.com/?l=linux-kernel&m=108355087015676&w=2

Signature · 1 line
~Randy
#9 lore raw
In reply to iSteve
Quoted 6 lines · iSteve

Part of the project I'm working on -- click-click ui for handling modules, with some perks: in this case, getting info about loaded modules that I hoped to obtain via query_module.

Oh, and one more question: There were no particular issues with query_module, or were they? If there weren't, why wasn't it kept?

I think it wasn't kept because it would have had to get rewritten anyway, and the only user (modutils) was going away. Most of the information was only there because the old system needed it, and the new system didn't need it, so nobody bothered. Also, the modern style is to avoid special-purpose syscalls and use sysfs. It probably wouldn't be too hard to get the information exported through the sysfs interface if you ask Rusty and explain exactly what you need.

(Note that you can get module symbols by searching /proc/kallsyms for <tab>[<name>], so that part is available from the kernel, although not efficiently if you have a lot of symbols that you aren't interested in)

-Daniel
*This .sig left intentionally blank*

#10 lore raw
In reply to iSteve
Quoted 8 lines · iSteve
Quoted 3 lines

Nope, they are not prevented. However, there is a Tainted flag that is set when one is loaded (and that flag is never cleared).

Okay, I've been wrong in my conclusion and I gotta read some fine manual about how the modules actually work -- could you recommend me some in particular?

Well, the depmod(8), lsmod(8), insmod(8), modprobe(8), modules.dep(5), depmod.old(8) and modprobe.conf(5) man pages all have various bits of info.

There's also some info in chapter 2 of "Linux Device Drivers, Third Edition" - http://lwn.net/images/pdf/LDD3/ch02.pdf

Then there's The Linux Kernel Module Programming Guide -
http://www.tldp.org/LDP/lkmpg/2.6/html/

As well as the Linux Loadable Kernel Module HOWTO -
http://www.tldp.org/HOWTO/Module-HOWTO/

Also take a look at the file Documentation/kbuild/modules.txt in your kernel source dir.

That's just a little bit of reading material for you :)

Signature · 3 lines
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html