Re: strange behaviour in syscall

["H. Peter Anvin" <hpa@zytor.com>]

Followup to:  <Pine.SOL.3.96.1010515230910.8808A-100000@kohinoor.csa.iisc.ernet.in>
By author:    Sourav Sen <sourav@csa.iisc.ernet.in>
In newsgroup: linux.dev.kernel
> 
> 	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.
> 
> 	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?
> 
> Sorry to you all for disturbing,
> 

Yes, you are using system call numbers that have already been assigned
(in other kernel versions.)  libc tries to use them to see if they are
available, and so they seem to be.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt