Arch Linux

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,668

Website

2.6.38.1 and syslog-ng errors - anyone else confirm?

Section from my dmesg booting from 2.6.38.1 (kernel26-ck):

WARNING: at kernel/printk.c:288 do_syslog+0xc1/0x510()
Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated).
Pid: 2854, comm: syslog-ng Tainted: P 2.6.38-ck #1Call Trace:
[<ffffffff8103ecfa>] ? warn_slowpath_common+0x7a/0xb0
[<ffffffff8103edd1>] ? warn_slowpath_fmt+0x41/0x50
[<ffffffff811a1564>] ? security_capable+0x24/0x30
[<ffffffff8103ff61>] ? do_syslog+0xc1/0x510
[<ffffffff81181897>] ? kmsg_open+0x17/0x20
[<ffffffff81176852>] ? proc_reg_open+0xa2/0x190
[<ffffffff81181880>] ? kmsg_open+0x0/0x20
[<ffffffff81181860>] ? kmsg_release+0x0/0x20
[<ffffffff811767b0>] ? proc_reg_open+0x0/0x190
[<ffffffff8111c95d>] ? __dentry_open+0xfd/0x370
[<ffffffff81128c7e>] ? generic_permission+0x1e/0xc0
[<ffffffff8111dc31>] ? nameidata_to_filp+0x71/0x80
[<ffffffff8112cb38>] ? finish_open+0xc8/0x1b0
[<ffffffff8112c3b2>] ? do_path_lookup+0x82/0x160
[<ffffffff8112d2c4>] ? do_filp_open+0x2a4/0x800
[<ffffffff8109c860>] ? call_rcu+0x10/0x20
[<ffffffff81139b94>] ? alloc_fd+0xf4/0x150
[<ffffffff811e502d>] ? strncpy_from_user+0x2d/0x40
[<ffffffff8111dca4>] ? do_sys_open+0x64/0x110
[<ffffffff8111dd6b>] ? sys_open+0x1b/0x20
[<ffffffff81002cfb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 5e39aac09d167e5f ]---

This went away upon installing syslog-ng-3.2.2-2 from [testing].  Can anyone else confirm using kernel26 from [testing]?

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: 2.6.38.1 and syslog-ng errors - anyone else confirm?

yes, i had that when i cherry picked from testing only the kernel. Thomas said that is how is supposed to be the warning

---

Give what you have. To someone, it may be better than you dare to think.

combuster

Member

From: Serbia

Registered: 2008-09-30

Posts: 711

Website

Re: 2.6.38.1 and syslog-ng errors - anyone else confirm?

Syslog-ng 3.2.2 with 2.6.38.1 (or 2.6.38 for that matter) shouldn't reproduce this warning. I had that with old syslog-ng and before Linus reverted this patch during rc cycle of 2.6.38 (I think that revert landed somewhere around rc6). Anyways it's nothing to worry about either way.

pcxz

Member

From: Italy

Registered: 2008-01-13

Posts: 67

Re: 2.6.38.1 and syslog-ng errors - anyone else confirm?

Section from my dmesg booting from 2.6.38.1 (kernel26-ck):

WARNING: at kernel/printk.c:288 do_syslog+0xc1/0x510()
Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated).
Pid: 2854, comm: syslog-ng Tainted: P 2.6.38-ck #1Call Trace:
[<ffffffff8103ecfa>] ? warn_slowpath_common+0x7a/0xb0
[<ffffffff8103edd1>] ? warn_slowpath_fmt+0x41/0x50
[<ffffffff811a1564>] ? security_capable+0x24/0x30
[<ffffffff8103ff61>] ? do_syslog+0xc1/0x510
[<ffffffff81181897>] ? kmsg_open+0x17/0x20
[<ffffffff81176852>] ? proc_reg_open+0xa2/0x190
[<ffffffff81181880>] ? kmsg_open+0x0/0x20
[<ffffffff81181860>] ? kmsg_release+0x0/0x20
[<ffffffff811767b0>] ? proc_reg_open+0x0/0x190
[<ffffffff8111c95d>] ? __dentry_open+0xfd/0x370
[<ffffffff81128c7e>] ? generic_permission+0x1e/0xc0
[<ffffffff8111dc31>] ? nameidata_to_filp+0x71/0x80
[<ffffffff8112cb38>] ? finish_open+0xc8/0x1b0
[<ffffffff8112c3b2>] ? do_path_lookup+0x82/0x160
[<ffffffff8112d2c4>] ? do_filp_open+0x2a4/0x800
[<ffffffff8109c860>] ? call_rcu+0x10/0x20
[<ffffffff81139b94>] ? alloc_fd+0xf4/0x150
[<ffffffff811e502d>] ? strncpy_from_user+0x2d/0x40
[<ffffffff8111dca4>] ? do_sys_open+0x64/0x110
[<ffffffff8111dd6b>] ? sys_open+0x1b/0x20
[<ffffffff81002cfb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 5e39aac09d167e5f ]---

This went away upon installing syslog-ng-3.2.2-2 from [testing].  Can anyone else confirm using kernel26 from [testing]?

I use vanilla kernel compiled myself and yes have this message (with kernel 2.6.38.1 and also with 2.6.38.2 ).

JokerBoy

Member

From: România

Registered: 2009-09-24

Posts: 641

Re: 2.6.38.1 and syslog-ng errors - anyone else confirm?

you must use syslog-ng from [testing] with 2.6.38

i686
# pacman -U http://mirrors.kernel.org/archlinux/tes … pkg.tar.xz

x86_64
# pacman -U http://mirrors.kernel.org/archlinux/tes … pkg.tar.xz

---

Arch64/DWM || My Dropbox referral link

pcxz

Member

From: Italy

Registered: 2008-01-13

Posts: 67

Re: 2.6.38.1 and syslog-ng errors - anyone else confirm?

you must use syslog-ng from [testing] with 2.6.38

i686
# pacman -U http://mirrors.kernel.org/archlinux/tes … pkg.tar.xz

Thx it work