Eric W. Biederman wrote:
Ben Greear [EMAIL PROTECTED] writes:
I guess that will do, but then if you ever change the strings, any user-space
that is
depending on this will break or have to be modified with additional cruft.
It
seems
cleaner to me to have an ioctl or a specific place
When the number of conntracks is reached nf_conntrack_max limit, early_drop() is
called and tries to free one of already used conntracks in one of the hash
buckets. If it does not find any conntracks that may be freed, it
leads to transmission errors.
However it is not fair because of current hash
Vasily Averin a e'crit :
When the number of conntracks is reached nf_conntrack_max limit, early_drop() is
called and tries to free one of already used conntracks in one of the hash
buckets. If it does not find any conntracks that may be freed, it
leads to transmission errors.
However it is not
Daniel Pittman [EMAIL PROTECTED] writes:
First, sorry for the cross-post. Since this is an issue with the
interaction between the two software packages -- and seems to be of
general interest on the OpenVZ users list where I first posted -- I felt
it was best to copy all three locations up front.
On 4/6/07, Srivatsa Vaddagiri [EMAIL PROTECTED] wrote:
On Fri, Apr 06, 2007 at 04:32:24PM -0700, [EMAIL PROTECTED] wrote:
+static int attach_task(struct container *cont, struct task_struct *tsk)
{
[snip]
+ task_lock(tsk);
You need to check here if task state is PF_EXITING and fail
Eric Dumazet wrote:
Vasily Averin a e'crit :
When the number of conntracks is reached nf_conntrack_max limit,
early_drop() is
called and tries to free one of already used conntracks in one of the
hash
buckets. If it does not find any conntracks that may be freed, it
leads to transmission
