https://bugs.archlinux.org/task/22555?getfile=6297 ArchLinux has a patch already... Reproducible: Always Steps to Reproduce: 1. Boot into 2.6.38+ and start syslog-ng 2. 3.
Offical bugreport can be found here: https://bugzilla.balabit.com/show_bug.cgi?id=108 And there is also a thread about this change on lkml: https://lkml.org/lkml/2011/1/28/80 Sorry about not giving anything usefull yet, take these only as fyi.
I think it's worth noting that the archlinux patch posted above applies correctly to syslog-ng-3.1.4 and fixes the issue.
(In reply to comment #2) > I think it's worth noting that the archlinux patch posted above applies > correctly to syslog-ng-3.1.4 and fixes the issue. > Well it may fix this one, but the kernel change would break many userspace tools not just syslog-ng. Fixing every one of them would take a lot of time. Even more, as of 2.6.38 is not even released, patching tools here and then may cause troubles in the future. I would rather wait for a statement about this either from the kernel devs or from Balabit (vendor of syslog-ng). Of course I wouldn't stop you from using the patch though :)
#3: I think you're absolutely right and yes, for now I'm using the patch. ;)
(In reply to comment #3) > (In reply to comment #2) > > I think it's worth noting that the archlinux patch posted above applies > > correctly to syslog-ng-3.1.4 and fixes the issue. > > > > Well it may fix this one, but the kernel change would break many userspace > tools not just syslog-ng. Fixing every one of them would take a lot of time. > Even more, as of 2.6.38 is not even released, patching tools here and then may > cause troubles in the future. > > I would rather wait for a statement about this either from the kernel devs or > from Balabit (vendor of syslog-ng). > > Of course I wouldn't stop you from using the patch though :) > For your information https://bugzilla.balabit.com/show_bug.cgi?id=108#c13
For now this is fixed upstream at k.o http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ee24aebffb75a7f940cf52c8cf6910947b3130c0
FYI: same here, using gentoo-sources-2.6.39 + syslog-ng-3.2.4. Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated). ------------[ cut here ]------------ WARNING: at kernel/printk.c:293 Modules linked in: arc4 ecb b43 mac80211 snd_aoa_codec_toonie cfg80211 snd_aoa_fabric_layout snd_aoa rfkill ssb snd_aoa_i2sbus snd_aoa_soundbus dm_mod scsi_wait_scan NIP: c0029cec LR: c0029cec CTR: 00000000 REGS: df9a7c90 TRAP: 0700 Not tainted (2.6.39-gentoo) MSR: 00029032 <EE,ME,CE,IR,DR> CR: 84022482 XER: 00000000 TASK = dfbc8c00[3376] 'syslog-ng' THREAD: df9a6000 GPR00: c0029cec df9a7d40 dfbc8c00 0000004f df9a7c6c df9a7c68 c05cba0c 65707265 GPR08: c05cbdd0 c059f42c 00004edb df9a7d00 24022488 1001c228 00000000 00000000 GPR16: 10030000 100166bc 100166b4 00000000 00000000 10710c7c 00000000 df9a7f18 GPR24: 00000024 bffb7df8 fffffff4 dfa60400 ffffffff 00000001 00000000 00000000 NIP [c0029cec] do_syslog+0x94/0x538 LR [c0029cec] do_syslog+0x94/0x538 Call Trace: [df9a7d40] [c0029cec] do_syslog+0x94/0x538 (unreliable) [df9a7da0] [c00e0e34] kmsg_open+0x20/0x30 [df9a7db0] [c00d7a44] proc_reg_open+0x90/0x10c [df9a7dd0] [c0097d80] __dentry_open.clone.15+0x178/0x288 [df9a7df0] [c00a5a54] do_last.clone.41+0x630/0x754 [df9a7e40] [c00a5cac] path_openat+0xb4/0x340 [df9a7e90] [c00a5f6c] do_filp_open+0x34/0x7c [df9a7f10] [c0098d44] do_sys_open+0x124/0x1b8 [df9a7f40] [c000ff88] ret_from_syscall+0x0/0x38 --- Exception: c01 at 0xfdd5a48 LR = 0xfdd59fc Instruction dump: 48008795 2f830000 419e04c0 3d20c05d 3929b924 3d290002 880904ac 2f800001 41be0028 3c60c04f 386358c3 483ffff1 <0fe00000> 3d20c05d 38000001 3929b924 ---[ end trace 3280ec4656a9f7f7 ]---
FYI: syslog-ng-3.2.4 using 2 patches from upstream bugzilla on gentoo-sources-3.0.4-r2 works w/o annoying messages in dmesg.
