From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] coredump: Fix typo in comment Date: Wed, 18 Feb 2015 13:28:45 +0100 Message-ID: <20150218122845.GA3363@pd.tnic> References: <1423143305.14425.38.camel@hadess.net> <1424262212.32581.31.camel@hadess.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, trivial@kernel.org To: Bastien Nocera Return-path: Content-Disposition: inline In-Reply-To: <1424262212.32581.31.camel@hadess.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org CC: trivial@kernel.org On Wed, Feb 18, 2015 at 01:23:32PM +0100, Bastien Nocera wrote: > Any updates on this simple patch? > > On Thu, 2015-02-05 at 14:35 +0100, Bastien Nocera wrote: > > Signed-off-by: Bastien Nocera > > --- > > 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 > > -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --