Date: Thu, 15 Apr 2004 15:54:08 -0700
From: Andrew Morton <akpm@osdl.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: manfred@colorfullife.com, drepper@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: message queue limits
Message-Id: <20040415155408.0902a0c0.akpm@osdl.org>
In-Reply-To: <20040415214632.GA4402@logos.cnet>
References: <407A2DAC.3080802@redhat.com>
	<20040415145350.GF2085@logos.cnet>
	<20040415122411.0bcb9195.akpm@osdl.org>
	<20040415195430.GB3568@logos.cnet>
	<20040415214632.GA4402@logos.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 926
Lines: 24

Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
>
> This adds a new "RLIMIT_SIGPENDING" limit, which is used to limit
> per-uid pending signals. Currently an unpriviledged user can queue 
> more than maximum of allowed signals and cause overall system 
> malfunction.

So now it takes two users to gang up and do the same thing.  We should
either exempt root from the global check or simply remove the global limit
altogether.

Is it possible for a process to do setuid() with outstanding signals?  If
so, they may end up with a negative current->user->signal_pending?

You need to initialise ->signal_pending in alloc_uid().

What are you doing for testing of this?

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/