LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [PATCH] coredump: Fix typo in comment
@ 2015-02-05 13:35 Bastien Nocera
2015-02-18 12:23 ` Bastien Nocera
0 siblings, 1 reply; 3+ messages in thread
From: Bastien Nocera @ 2015-02-05 13:35 UTC (permalink / raw)
To: viro, linux-fsdevel; +Cc: linux-kernel
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
--
2.1.0
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] coredump: Fix typo in comment
2015-02-05 13:35 [PATCH] coredump: Fix typo in comment Bastien Nocera
@ 2015-02-18 12:23 ` Bastien Nocera
2015-02-18 12:28 ` Borislav Petkov
0 siblings, 1 reply; 3+ messages in thread
From: Bastien Nocera @ 2015-02-18 12:23 UTC (permalink / raw)
To: viro; +Cc: linux-fsdevel, linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] coredump: Fix typo in comment
2015-02-18 12:23 ` Bastien Nocera
@ 2015-02-18 12:28 ` Borislav Petkov
0 siblings, 0 replies; 3+ messages in thread
From: Borislav Petkov @ 2015-02-18 12:28 UTC (permalink / raw)
To: Bastien Nocera; +Cc: viro, linux-fsdevel, linux-kernel, trivial
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 <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
>
>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-02-18 12:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-05 13:35 [PATCH] coredump: Fix typo in comment Bastien Nocera
2015-02-18 12:23 ` Bastien Nocera
2015-02-18 12:28 ` Borislav Petkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).