From: Eugene Teo <eteo@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jeremy@goop.org, martin.pitt@ubuntu.com, wwoods@redhat.com
Subject: Re: [PATCH 1/3] core_pattern: ignore RLIMIT_CORE if core_pattern is a pipe
Date: Sun, 29 Jul 2007 21:03:19 +0800 [thread overview]
Message-ID: <46AC9017.7080109@redhat.com> (raw)
In-Reply-To: <20070727200355.GB18946@hmsreliant.homelinux.net>
Neil Horman wrote:
[...]
> + * Don't bother to check the RLIMIT_CORE value if core_pattern points
> + * to a pipe. Since we're not writing directly to the filesystem
> + * RLIMIT_CORE doesn't really apply, as no actual core file will be
> + * created unless the pipe reader choses to write out the core file
> + * at which point file size limits and permissions will be imposed
^^^
Trailing space.
Eugene
prev parent reply other threads:[~2007-07-29 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 20:03 [PATCH 1/3] core_pattern: ignore RLIMIT_CORE if core_pattern is a pipe Neil Horman
2007-07-29 13:03 ` Eugene Teo [this message]
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=46AC9017.7080109@redhat.com \
--to=eteo@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=nhorman@tuxdriver.com \
--cc=wwoods@redhat.com \
/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