grsecurity forums

(Perhaps not grsec related) This doesn't seem reproducible, some
mornings I find it the screen, never happens in office hours. Searching
"kernel BUG at signal.c" in google gives only one result, in a line distant
to 784 :).

ksymoops 2.4.9 on i686 2.6.7-proto-grsec. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.7-proto-grsec/ (default)
-m /boot/System.map-2.6.7-proto-grsec (default)

Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Reading Oops report from the terminal
Feb 16 10:06:39 proto kernel: kernel BUG at kernel/signal.c:784!
Feb 16 10:06:39 proto kernel: invalid operand: 0000 [#1]
Feb 16 10:06:39 proto kernel: CPU: 0
Feb 16 10:06:39 proto kernel: EIP: 0060:[<c01fefa7>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Feb 16 10:06:39 proto kernel: EFLAGS: 00010246 (2.6.7-proto-grsec)
Feb 16 10:06:39 proto kernel: eax: 00000000 ebx: 0000000b ecx: 00000004 edx: c55f3930
Feb 16 10:06:39 proto kernel: esi: c55f3930 edi: c7d8bf24 ebp: 00000000 esp: c7d8bedc
Feb 16 10:06:39 proto kernel: ds: 007b es: 007b ss: 0068
Feb 16 10:06:39 proto kernel: Stack: c55f3930 0000000b 00000000 00000213 c01ff079 0000000b c7d8bf24 c55f3930
Feb 16 10:06:39 proto kernel: c55f3930 cca8e100 00000000 c7dfc9bc c01f1b4b 0000000b c7d8bf24 c55f3930
Feb 16 10:06:39 proto kernel: 00000000 c55f3930 0000000b 00000000 00030001 00000000 c0203304 c16f5d00
Feb 16 10:06:39 proto kernel: Call Trace:
Feb 16 10:06:39 proto kernel: [<c01ff079>] [<c01f1b4b>] [<c0203304>] [<c01f2da6>] [<c04337c3>] [<c0433911>] [<c01f1a60>] [<c01e6fbd>]
Feb 16 10:06:39 proto kernel: Code: 0f 0b 10 03 84 03 45 c0 83 ff 02 76 09 81 7f 08 fe ff 01 00


>>EIP; c01fefa7 <specific_send_sig_info+27/b0> <=====

>>edx; c55f3930 <__crc_usb_init_urb+2049ab/54bf38>
>>esi; c55f3930 <__crc_usb_init_urb+2049ab/54bf38>
>>edi; c7d8bf24 <__crc_rtnl_lock+33c337/47703a>
>>esp; c7d8bedc <__crc_rtnl_lock+33c2ef/47703a>

Trace; c01ff079 <force_sig_info+49/b0>
Trace; c01f1b4b <do_page_fault+eb/680>
Trace; c0203304 <in_group_p+34/70>
Trace; c01f2da6 <recalc_task_prio+a6/1d0>
Trace; c04337c3 <schedule+1a3/510>
Trace; c0433911 <schedule+2f1/510>
Trace; c01f1a60 <do_page_fault+0/680>
Trace; c01e6fbd <error_code+2d/40>

Code; c01fefa7 <specific_send_sig_info+27/b0>
00000000 <_EIP>:
Code; c01fefa7 <specific_send_sig_info+27/b0> <=====
0: 0f 0b ud2a <=====
Code; c01fefa9 <specific_send_sig_info+29/b0>
2: 10 03 adc %al,(%ebx)
Code; c01fefab <specific_send_sig_info+2b/b0>
4: 84 03 test %al,(%ebx)
Code; c01fefad <specific_send_sig_info+2d/b0>
6: 45 inc %ebp
Code; c01fefae <specific_send_sig_info+2e/b0>
7: c0 83 ff 02 76 09 81 rolb $0x81,0x97602ff(%ebx)
Code; c01fefb5 <specific_send_sig_info+35/b0>
e: 7f 08 jg 18 <_EIP+0x18>
Code; c01fefb7 <specific_send_sig_info+37/b0>
10: fe (bad)
Code; c01fefb8 <specific_send_sig_info+38/b0>
11: ff 01 incl (%ecx)

Are you able to reproduce the problem with grsec 2.1.1 for 2.6.10?

-Brad