strange behaviour in syscall

[Rik van Riel <riel@conectiva.com.br>]

[intercepted by overzealous admin_body rule, which is gone now]
---------------------
Date:   Wed, 16 May 2001 01:37:54 +0530 (IST)
From:   Sourav Sen <sourav@csa.iisc.ernet.in>
To:     kernelnewbies@humbolt.nl.linux.org
Subject: strange behaviour in syscall

Hello,
	I posted a similar doubt before, this time I might be luckier to 
get an answer!!

	In 2.2.14, I have implemented a set of system calls(This is just
academic). The numbers are from 191 - 196. (The virgin source tree has
up to 190 in entry.S). I have given a printk in the system call proper in
the last one(196),(and at many other places in the call chain from there).
(Is it fair to use those syacall numbers ?)

	But when I boot up that kernel that printk gets executed. While 
booting, at least to my knowledge, that part of the code is not supposed
to get executed. Also while the kernel goes down, that printk speaks
again. 

	All other system calls are working fine.

	Lately I have replaced the last syscall number by 191, and removed
the earlier 191 th call, now the message is not appearing!! 

	My guess is some interrupt is getting vectored in that system
call(196), but I am totally in dark why such a thing might at all happen.

	I am getting some oops and panic while that syscall executes, so I
am suspicious that I am doing something that I should never have done.

	Do anybody has any idea what might be going wrong?


Thanks,

sourav 

-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/