linux-kernel - Re: [PATCH] audit: error message typo correction

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.2.00.1011031350040.15851@pobox.suse.cz>
Date:	Wed, 3 Nov 2010 13:50:26 -0400 (EDT)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Ross Kirk <Ross.Kirk@...or.com>
Cc:	viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
	eparis@...hat.com
Subject: Re: [PATCH] audit: error message typo correction

On Fri, 22 Oct 2010, Ross Kirk wrote:

> 
> Fixes a typo in the error message raised by audit when auditd has died
> 
> Signed-off-by: Ross Kirk <ross.kirk@...or.com>
> 
> --
> 
> diff -up a/kernel/audit.c b/kernel/audit.c 
> --- a/kernel/audit.c    2010-10-22 16:25:40.000000000 +0100
> +++ b/kernel/audit.c    2010-10-22 16:25:46.000000000 +0100
> @@ -400,7 +400,7 @@ static void kauditd_send_skb(struct sk_b
>         if (err < 0) {
>                 BUG_ON(err != -ECONNREFUSED); /* Shouldn't happen */
>                 printk(KERN_ERR "audit: *NO* daemon at audit_pid=%d\n", audit_pid);
> -               audit_log_lost("auditd dissapeared\n");
> +               audit_log_lost("auditd disappeared\n");
>                 audit_pid = 0;
>                 /* we might get lucky and get this in the next auditd */
>                 audit_hold_skb(skb);

Asi this is not in linux-next as of today, I have put it into trivial 
queue.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/