linux-kernel - Re: Syslog-NG Fails as of Kernel 2.6.38-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Jan 2011 09:53:04 +0000 (UTC)
From:	WANG Cong <xiyou.wangcong@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Syslog-NG Fails as of Kernel 2.6.38-rc1

On Thu, 27 Jan 2011 04:51:10 -0800, Eugene Markow wrote:

> The following appears in dmesg from kernels 2.6.38-rc1 to
> 2.6.38-rc2-git5 (Not an issue in 2.6.37 stable):
> 
> ----------
> WARNING: at kernel/printk.c:430 do_syslog+0xeb/0x5e0()

Looks like syslog-ng passes a wrong type to sys_syslog():

        if (type == SYSLOG_ACTION_OPEN || !from_file) {
                if (dmesg_restrict && !capable(CAP_SYSLOG))
                        goto warn;

                if ((type != SYSLOG_ACTION_READ_ALL &&
                     type != SYSLOG_ACTION_SIZE_BUFFER) &&
                    !capable(CAP_SYSLOG))
                        goto warn;
        }

...
> 
> Furthermore, during the bootup process, I'm getting:
> 
> 
> ----------
> ::Starting Syslg-NG            [BUSY] Error opening file for reading:
> filename '/proc/kmsg', error='Operation not permitted (1)'
> Error initializing source driver: source='src', id='src#2' Error
> initializing message pipline;
>                     [FAIL]


Hmm, it writes /proc/kmsg... I will look at the code later.


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