All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] override RLIMIT_SIGPENDING for non-RT signals
Date: Wed, 23 Feb 2005 18:43:08 -0800	[thread overview]
Message-ID: <200502240243.j1O2h8Bk010811@magilla.sf.frob.com> (raw)
In-Reply-To: Chris Wright's message of  Wednesday, 23 February 2005 18:32:45 -0800 <20050224023245.GA28536@shell0.pdx.osdl.net>

> * Roland McGrath (roland@redhat.com) wrote:
> > Indeed, I think your patch does not go far enough.  I can read POSIX to say
> > that the siginfo_t data must be available when `kill' was used, as well.
> 
> How?  I only see reference to filling in SI_USER for rt signals?
> Just curious...(I've only got SuSv3 and some crusty old POSIX rt docs).

There is stuff about a SA_SIGINFO signal handler's siginfo_t argument
"shall contain" the various specified information like si_pid/si_uid values
for a kill caller.

> Good point.  Although it's RLIMIT_SIGPENDING + (31 * user_nprocs).  So
> that could be 31 * 8k, for example.

And a "good point" back to you, sir!  I think the right way to think about
this in terms of resource consumption is that sizeof(struct sigqueue)*31 is
part of the potential per-process overhead that make up the consumption
units one should have in mind when choosing how to set the RLIMIT_NPROC limit.


Thanks,
Roland

  reply	other threads:[~2005-02-24  2:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  6:42 [PATCH] Always send siginfo for synchronous signals Jeremy Fitzhardinge
2005-02-23 20:19 ` Chris Wright
2005-02-23 23:09   ` Jeremy Fitzhardinge
2005-02-23 23:46     ` Chris Wright
2005-02-24  0:50       ` Jeremy Fitzhardinge
2005-02-24  2:07     ` [PATCH] show RLIMIT_SIGPENDING usage in /proc/PID/status Roland McGrath
2005-02-24  2:33       ` Chris Wright
2005-02-24  2:55         ` Roland McGrath
2005-02-24  3:06           ` Chris Wright
2005-02-24  2:24     ` [PATCH] set RLIMIT_SIGPENDING limit based on RLIMIT_NPROC Roland McGrath
2005-02-24  3:07       ` Chris Wright
2005-02-25  2:05         ` Jeremy Fitzhardinge
2005-02-25  2:10           ` Chris Wright
2005-02-23 23:44   ` [PATCH] Always send siginfo for synchronous signals Jeremy Fitzhardinge
2005-02-24  1:45     ` [PATCH] override RLIMIT_SIGPENDING for non-RT signals Roland McGrath
2005-02-24  2:32       ` Chris Wright
2005-02-24  2:43         ` Roland McGrath [this message]
2005-02-24  3:12           ` Chris Wright
2005-02-25  2:01       ` Jeremy Fitzhardinge
2005-02-25  2:12         ` Chris Wright
2005-02-25  2:16           ` Roland McGrath
2005-02-25  3:02             ` Chris Wright

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=200502240243.j1O2h8Bk010811@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.