Re: Linux 2.6.19.2 : Oops

2007-01-22 Thread Nicolas Bareil
Greg KH <[EMAIL PROTECTED]> writes:
>> Since 2.6.19, I get the following Oops once a day, always with the same
>> process, newspipe[1] which use a lot of CPU, threads and I/O.
>> 
>> The kernel is patched by Grsecurity. The ext3 filesystem is on a
>> software RAID device (the two disks are SATA2). I tested the 
>> hardware (RAM, SMART disks) but nothing seem problematic.
>
> Can you reproduce it without the grsec patch applied?

After 4 days of tests without grsec, I didn't had any Oops. So it seems
I will have to find this bug with the grsecurity developpers...

Thank you!
-- 
Nicolas Bareil  http://chdir.org/~nico/
OpenPGP=0xAE4F7057 Fingerprint=34DB22091049FB2F33E6B71580F314DAAE4F7057

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.19.2 : Oops

2007-01-17 Thread Nicolas Bareil

On 18 Jan 2007, Greg KH wrote:
> > Since 2.6.19, I get the following Oops once a day, always with the same
> > process, newspipe[1] which use a lot of CPU, threads and I/O.
> > ...
> Can you reproduce it without the grsec patch applied?

I'm compiling a new kernel and will try it soon!

-- 
Nicolas Bareil  http://chdir.org/~nico/
OpenPGP=0xAE4F7057 Fingerprint=34DB22091049FB2F33E6B71580F314DAAE4F7057

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Linux 2.6.19.2 : Oops

2007-01-17 Thread Nicolas Bareil

Hello,

Since 2.6.19, I get the following Oops once a day, always with the same
process, newspipe[1] which use a lot of CPU, threads and I/O.

The kernel is patched by Grsecurity. The ext3 filesystem is on a
software RAID device (the two disks are SATA2). I tested the 
hardware (RAM, SMART disks) but nothing seem problematic.

kernel: BUG: unable to handle kernel NULL pointer dereference at virtual 
address 0004
kernel: printing eip:
kernel: b0176344
kernel: *pgd =0
kernel: *pmd =0
kernel: Oops:  [#1]
kernel: CPU:0
kernel: EIP:0060:[]Not tainted VLI
kernel: EFLAGS: 00210286   (2.6.19.2-grsec #1)
kernel: EIP is at do_generic_mapping_read+0x34/0x4e0
kernel: eax: d8deeb50   ebx: 001b   ecx:    edx: ed6e1df4
kernel: esi:    edi: ed6e1e1c   ebp: e6235a40   esp: ed6e1dac
kernel: ds: 0068   es: 0068   ss: 0068
kernel: Process python (pid: 13360, ti=ed6e task=daf1f030 task.ti=ed6e)
kernel: Stack: d8deeb50 0001  1000 0010   
ed6e1df4 
kernel: d8deeb50 0010  0010 0010 000e 000105a5  
kernel:  1000  0020  0020 000f  
kernel: Call Trace:
kernel: [] generic_file_aio_read+0xf3/0x230
kernel: [] file_read_actor+0x0/0x130
kernel: [] do_sync_read+0xed/0x130
kernel: [] autoremove_wake_function+0x0/0x60
kernel: [] __vma_link+0x3c/0x70
kernel: [] vma_link+0x38/0xc0
kernel: [] vfs_read+0xd4/0x1c0
kernel: [] sys_read+0x4b/0x80
kernel: [] syscall_call+0x7/0xb
kernel: [] restore_all+0x0/0x18
kernel: ===
kernel: Code: 83 ec 70 8b 84 24 84 00 00 00 8d 54 24 48 89 d7 8b b4 24 88 00 00 
00 fc 8b 00 89 54 24 1c 89 44 24 20 f3 a5 8b b4 24 90 00 00 00 <8b> 5e 04 8b 0e 
8b b4 24 94 00 00 00 89 da c1 fa 0c 89 c8 89 54 
kernel: EIP: [] do_generic_mapping_read+0x34/0x4e0 SS:ESP 
0068:ed6e1dac

My config is available on http://chdir.org/~nbareil/config-2.6.19.2-grsec.gz

Thank you!

Footnotes: 
[1]  http://newspipe.sourceforge.net/

-- 
Nicolas Bareil  http://chdir.org/~nico/
OpenPGP=0xAE4F7057 Fingerprint=34DB22091049FB2F33E6B71580F314DAAE4F7057

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/