linux-kernel - Re: [PATCH trivial] docs: fix core_pipe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20091005234741.GA7538@localhost.localdomain>
Date:	Mon, 5 Oct 2009 19:47:41 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH trivial] docs: fix core_pipe_limit info

On Tue, Oct 06, 2009 at 12:03:40AM +0200, Jiri Kosina wrote:
> On Sun, 4 Oct 2009, Randy Dunlap wrote:
> 
> > From: Randy Dunlap <randy.dunlap@...cle.com>
> > 
> > Fix typos in core_pipe_limit info.
> > 
> > Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> > Cc: Neil Horman <nhorman@...driver.com>
> > ---
> >  Documentation/sysctl/kernel.txt |    6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > --- linux-next-20090930.orig/Documentation/sysctl/kernel.txt
> > +++ linux-next-20090930/Documentation/sysctl/kernel.txt
> > @@ -139,9 +139,9 @@ core_pattern is used to specify a core d
> >  core_pipe_limit:
> >  
> >  This sysctl is only applicable when core_pattern is configured to pipe core
> > -files to user space helper a (when the first character of core_pattern is a '|',
> > +files to a user space helper (when the first character of core_pattern is a '|',
> >  see above).  When collecting cores via a pipe to an application, it is
> > -occasionally usefull for the collecting application to gather data about the
> > +occasionally useful for the collecting application to gather data about the
> >  crashing process from its /proc/pid directory.  In order to do this safely, the
> >  kernel must wait for the collecting process to exit, so as not to remove the
> >  crashing processes proc files prematurely.  This in turn creates the possibility
> > @@ -152,7 +152,7 @@ applications in parallel.  If this value
> >  processes above that value are noted via the kernel log and their cores are
> >  skipped.  0 is a special value, indicating that unlimited processes may be
> >  captured in parallel, but that no waiting will take place (i.e. the collecting
> > -process is not guaranteed access to /proc/<crahing pid>/).  This value defaults
> > +process is not guaranteed access to /proc/<crashing pid>/).  This value defaults
> >  to 0.
> 
> Applied to trivial queue, thanks Randy.
> 
Thank you Randy, Jiri.
Neil

> -- 
> Jiri Kosina
> SUSE Labs, Novell Inc.
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/