[grsec] Debug output?

John Anderson johnha at ccbill.com
Wed Mar 9 16:56:37 EST 2005


We are still testing our installation of GRSEC on certain boxes, and 
after the upgrade to 2.1.3, we starting seeing some strange behavior.  
Whith grsec up and running, if a user access a program, like vim or ls 
or whatever, we get some debugging information (I think) printed to the 
console.  Vim still executes and runs properly however.  It looks like this:

Mar  7 15:35:32 bastion-dev kernel: grsec: From 10.20.27.18: 
(root:U:/bin/bash) exec of /usr/bin/vim (vim policy ) by 
/bin/bash[bash:32617] uid/euid:0/0 gid/egid:0/0, parent 
/bin/bash[bash:13864] uid/euid:0/0 gid/egid:0/0
Mar  7 15:35:32 bastion-dev kernel: BUG: using smp_processor_id() in 
preemptible [00000001] code: vim/32617
Mar  7 15:35:32 bastion-dev kernel:  [<c0250844>]
Mar  7 15:35:32 bastion-dev kernel:  [<c02448a9>]
Mar  7 15:35:32 bastion-dev kernel:  [<c040976d>]
Mar  7 15:35:32 bastion-dev kernel:  [<c018390a>]
Mar  7 15:35:32 bastion-dev kernel:  [<c0183cb6>]
Mar  7 15:35:32 bastion-dev kernel:  [<c0183cb6>]
Mar  7 15:35:32 bastion-dev kernel:  [<c0159f30>]
Mar  7 15:35:32 bastion-dev kernel:  [<c0159cd1>]
Mar  7 15:35:32 bastion-dev kernel:  [<c0159d66>]
Mar  7 15:35:32 bastion-dev kernel:  [<c014b400>]
Mar  7 15:35:32 bastion-dev kernel:  [<c01382e7>]
Mar  7 15:36:22 bastion-dev kernel: grsec: From 10.20.27.18: 
(root:U:/bin/bash) exec of /bin/ls (ls --color=tty -lAt /var/ ) by 
/bin/bash[bash:28927] uid/euid:0/0 gid/egid:0/0, parent 
/bin/bash[bash:1260] uid/euid:0/0 gid/egid:0/0
Mar  7 15:36:22 bastion-dev kernel: BUG: using smp_processor_id() in 
preemptible [00000001] code: ls/28927
Mar  7 15:36:22 bastion-dev kernel:  [<c0250844>]
Mar  7 15:36:22 bastion-dev kernel:  [<c02448a9>]
Mar  7 15:36:22 bastion-dev kernel:  [<c040976d>]
Mar  7 15:36:22 bastion-dev kernel:  [<c018390a>]
Mar  7 15:36:22 bastion-dev kernel:  [<c0183cb6>]
Mar  7 15:36:22 bastion-dev kernel:  [<c0159f30>]
Mar  7 15:36:22 bastion-dev kernel:  [<c0159cd1>]
Mar  7 15:36:22 bastion-dev kernel:  [<c0159d66>]
Mar  7 15:36:22 bastion-dev kernel:  [<c014b400>]
Mar  7 15:36:22 bastion-dev kernel:  [<c01382e7>]

Is this normal, expected behavior, or is it debugging output?  If it's 
debugging output is there a flag that can be set to turn it off?

Thanks again,

-- 
- John A.
Systems Administrator
CCBill, LLC.




More information about the grsecurity mailing list