[grsec] md2_resync & PAX

Bastien Durel bastien.durel at anciens.epitech.net
Mon Aug 3 06:03:38 EDT 2009


Hello

My RAID array is syncing for an unknown reason, but PAX doesn't like it.
I attached the log.

I'm using 2.6.27.10-grsec-ipsec-ipv6-64, with
grsecurity-2.1.12-2.6.27.10-200812271347 applied.

Is there any binary I may paxctl'ed to let it finish without filling my
disks with PAX logs ? (and let load average returning to normal value ?)

thanks,

-- 
Bastien Durel
-------------- next part --------------
Aug  3 10:29:02 corrin kernel: CPU 1 
Aug  3 10:29:02 corrin kernel: Pid: 26989, comm: md2_resync Not tainted 2.6.27.10-grsec-ipsec-ipv6-64 #5
Aug  3 10:29:02 corrin kernel: RIP: 0010:[<ffffffff8063c414>]  [<ffffffff8063c414>] 0xffffffff8063c414
Aug  3 10:29:02 corrin kernel: RSP: 0018:ffff880003d73ce0  EFLAGS: 00000a02
Aug  3 10:29:02 corrin kernel: RAX: ffff88007e282000 RBX: 0000000000000000 RCX: 0000000000000002
Aug  3 10:29:02 corrin kernel: RDX: ffff88007efd8800 RSI: 000000000000000f RDI: ffff880056041bc0
Aug  3 10:29:02 corrin kernel: RBP: 0000000000000080 R08: 0000000000000000 R09: 0000000000000400
Aug  3 10:29:02 corrin kernel: R10: ffff8800563931c0 R11: 0000000000000002 R12: ffffe200003b4d80
Aug  3 10:29:02 corrin kernel: R13: ffff880037026e40 R14: ffff88007ed97c80 R15: 0000000000001000
Aug  3 10:29:02 corrin kernel: FS:  0000000000000000(0000) GS:ffff88007ec6fd40(0000) knlGS:0000000000000000
Aug  3 10:29:02 corrin kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Aug  3 10:29:02 corrin kernel: CR2: 0000064120036000 CR3: 000000000869d000 CR4: 00000000000006e0
Aug  3 10:29:02 corrin kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug  3 10:29:02 corrin kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug  3 10:29:02 corrin kernel: Process md2_resync (pid: 26989, threadinfo ffff880003d72000, task ffff88007e23d910)
Aug  3 10:29:02 corrin kernel: Stack:  000000000000000a 0000000030660ff8 ffff88007efd8800 ffff88007efd8980
Aug  3 10:29:02 corrin kernel:  0000000000000080 0000000000000002 0000000039884a00 ffffffff806536a1
Aug  3 10:29:02 corrin kernel:  000003807efd8818 0000000030660f80 0000000030660f80 ffff88007efd8800
Aug  3 10:29:02 corrin kernel: Call Trace:
Aug  3 10:29:02 corrin kernel:  [<ffffffff806536a1>] ? 0xffffffff806536a1
Aug  3 10:29:02 corrin kernel:  [<ffffffff80653ba5>] ? 0xffffffff80653ba5
Aug  3 10:29:02 corrin kernel:  [<ffffffff8024bf30>] ? 0xffffffff8024bf30
Aug  3 10:29:02 corrin kernel:  [<ffffffff80654807>] ? 0xffffffff80654807
Aug  3 10:29:02 corrin kernel:  [<ffffffff806547c0>] ? 0xffffffff806547c0
Aug  3 10:29:02 corrin kernel:  [<ffffffff8024bb77>] ? 0xffffffff8024bb77
Aug  3 10:29:02 corrin kernel:  [<ffffffff80232777>] ? 0xffffffff80232777
Aug  3 10:29:02 corrin kernel:  [<ffffffff80204209>] ? 0xffffffff80204209
Aug  3 10:29:02 corrin kernel:  [<ffffffff8024bb30>] ? 0xffffffff8024bb30
Aug  3 10:29:02 corrin kernel:  [<ffffffff802041ff>] ? 0xffffffff802041ff
Aug  3 10:29:02 corrin kernel: 



More information about the grsecurity mailing list