From: Bastien Nocera <hadess@hadess.net>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coredump: Fix typo in comment
Date: Wed, 18 Feb 2015 13:23:32 +0100 [thread overview]
Message-ID: <1424262212.32581.31.camel@hadess.net> (raw)
In-Reply-To: <1423143305.14425.38.camel@hadess.net>
Any updates on this simple patch?
On Thu, 2015-02-05 at 14:35 +0100, Bastien Nocera wrote:
> Signed-off-by: Bastien Nocera <hadess@hadess.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
next prev parent reply other threads:[~2015-02-18 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 13:35 [PATCH] coredump: Fix typo in comment Bastien Nocera
2015-02-18 12:23 ` Bastien Nocera [this message]
2015-02-18 12:28 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1424262212.32581.31.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox