Skip to contentSkip to conversation

Changing sysctl values within the kernel?

DISCUSSION David Johnson 2 participants 3 messages Nov 25, 2006 – Nov 27, 2006

lore
Share & tools
lore
#0 lore raw

Hi all,

I'm working on a kernel module and want to change sysctl values (specifically stop-a and printk) in response to a hardware event.

Is there an accepted way of setting sysctl values within the kernel (I can't seem to find any other module doing this), or is it a completely silly idea?

Would it perhaps be better to instead create a sysfs node and let a userspace daemon worry about setting the sysctl values?

Any advice greatly appreciated!

David.

#1 lore raw
Quoted 5 lines · David Johnson

I'm working on a kernel module and want to change sysctl values (specifically stop-a and printk) in response to a hardware event.

Is there an accepted way of setting sysctl values within the kernel (I can't seem to find any other module doing this),

Yes. Next in-kernel module changing sysctls will do it via

	stop_a_enabled = 1;
	console_loglevel = 8;

(be sure, variables in question are EXPORT_SYMBOL'ed)

Quoted 1 line

or is it a completely silly idea?

Without more details it's hard to tell.

Quoted 2 lines

Would it perhaps be better to instead create a sysfs node and let a userspace daemon worry about setting the sysctl values?

Now _this_ is silly. sysctls already live in /proc/sys/, so you can open(2) /proc/sys/kernel/printk and write(2) to it.

#2 lore raw
Quoted 5 lines · you
Quoted 3 lines · David Johnson

Is there an accepted way of setting sysctl values within the kernel (I can't seem to find any other module doing this),

Quoted 7 lines

Yes. Next in-kernel module changing sysctls will do it via

	stop_a_enabled = 1;
	console_loglevel = 8;

(be sure, variables in question are EXPORT_SYMBOL'ed)

Bah, I never thought it would be that simple!

Quoted 6 lines
Quoted 3 lines

Would it perhaps be better to instead create a sysfs node and let a userspace daemon worry about setting the sysctl values?

Now _this_ is silly. sysctls already live in /proc/sys/, so you can open(2) /proc/sys/kernel/printk and write(2) to it.

OK, I'll give that a miss then ;-)

Thanks for your help!

David.