[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUlzwDt3IWFzOSCU@kroah.com>
Date: Tue, 21 Sep 2021 07:55:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Vishnu Rangayyan <vishnu.rangayyan@...le.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs: fix for core dumping of a process getting oom-killed
On Mon, Sep 20, 2021 at 11:38:40PM -0500, Vishnu Rangayyan wrote:
> diff --git a/fs/coredump.c b/fs/coredump.c
> index 3224dee44d30..187813704533 100644
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -54,6 +54,7 @@
>
> int core_uses_pid;
> unsigned int core_pipe_limit;
> +unsigned int core_sync_bytes = 131072; /* sync core file every so many
> bytes */
> char core_pattern[CORENAME_MAX_SIZE] = "core";
> static int core_name_size = CORENAME_MAX_SIZE;
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
and can not be applied. Please read the file,
Documentation/email-clients.txt in order to fix this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists