linux-kernel - Re: [PATCH] coredump: Fix typo in comment

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1424262212.32581.31.camel@hadess.net>
Date:	Wed, 18 Feb 2015 13:23:32 +0100
From:	Bastien Nocera <hadess@...ess.net>
To:	viro@...iv.linux.org.uk
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] coredump: Fix typo in comment

Any updates on this simple patch?

On Thu, 2015-02-05 at 14:35 +0100, Bastien Nocera wrote:
> Signed-off-by: Bastien Nocera <hadess@...ess.net>
> ---
>  fs/coredump.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/coredump.c b/fs/coredump.c
> index b5c86ff..f319926 100644
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -572,7 +572,7 @@ void do_coredump(const siginfo_t *siginfo)
>  			 *
>  			 * Normally core limits are irrelevant to pipes, since
>  			 * we're not writing to the file system, but we use
> -			 * cprm.limit of 1 here as a speacial value, this is a
> +			 * cprm.limit of 1 here as a special value, this is a
>  			 * consistent way to catch recursive crashes.
>  			 * We can still crash if the core_pattern binary sets
>  			 * RLIM_CORE = !1, but it runs as root, and can do


--
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/