grsecurity forums

Hi,

I'm getting the following warnings printed in my logs quite often, but only when I'm running KVM's. I'm running 9 KVMs, 8 FreeBSD 4.x based ones and a Windows 2003 Server based one.

Code: Select all

------------[ cut here ]------------
WARNING: at security/security.c:217 ()
Hardware name:
Modules linked in: i2c_dev xt_NFQUEUE iptable_filter ipt_MASQUERADE ipt_REDIRECT xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables nls_iso8859_1 nls_cp437 microcode nfnetlink_queue nfnetlink vfat fat nls_base loop usbhid usb_storage snd_hda_codec_realtek snd_hda_intel ehci_hcd evdev snd_hda_codec snd_pcm snd_seq snd_timer snd_seq_device uhci_hcd fan rtc_cmos 8250_pnp 8250 serial_core snd i2c_i801 usbcore rtc_core rtc_lib button soundcore snd_page_alloc i2c_core iTCO_wdt thermal processor thermal_sys intel_agp agpgart
Pid: 10757, comm: khelper Not tainted 2.6.29.2-grsec-tim #1
Call Trace:
 [<c04454df>] 0xc04454df
 [<c04778dd>] 0xc04778dd
 [<c04b2134>] 0xc04b2134
 [<c0485fd0>] 0xc0485fd0
 [<c0489095>] 0xc0489095
 [<c0530e45>] 0xc0530e45
 [<c0530e45>] 0xc0530e45
 [<c049e895>] 0xc049e895
 [<c05280e8>] 0xc05280e8
 [<c05280e8>] 0xc05280e8
 [<c0485865>] 0xc0485865
 [<c0509a1e>] 0xc0509a1e
 [<c048bbac>] 0xc048bbac
 [<c04a2bc0>] 0xc04a2bc0
 [<c0530068>] 0xc0530068
 [<c04a2d43>] 0xc04a2d43
 [<c04a5474>] 0xc04a5474
 [<c043cdcb>] 0xc043cdcb
 [<c043ce9f>] 0xc043ce9f
 [<c06567f5>] 0xc06567f5
 [<c0440d96>] 0xc0440d96
 [<c041e826>] 0xc041e826
 [<c0420802>] 0xc0420802
 [<c042469c>] 0xc042469c
 [<c0456120>] 0xc0456120
 [<c045623b>] 0xc045623b
 [<c0456120>] 0xc0456120
 [<c0420fd7>] 0xc0420fd7
---[ end trace 3180072cc3f7b350 ]---


Kernel is 2.6.29.2 with grsecurity-2.1.14-2.6.29.2-200905011803.patch applied.

System.map and .config are here: http://fozzie.muppetz.com/info.tar.bz2

I don't get this when I'm using vanilla 2.6.29.2

If it helps, I'm using KVM-85

Thanks,
Tim

Hi Tim,

I believe that was due to a mismerge on my part when porting to 2.6.29.2. It should be fixed in the latest test patch; let me know if you still have any problems.

-Brad

Thanks Brad, I'll give it a test shortly.

Latest patch has fixed this problem, thank you.