LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: serge@hallyn.com
Cc: buraphalinuxserver@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: at program breaks with kernel 2.6.24
Date: Wed, 27 Feb 2008 20:36:44 +0100	[thread overview]
Message-ID: <E1JUS56-0001ur-Tq@faramir.fjphome.nl> (raw)
In-Reply-To: <20080227181740.GA14532@vino.hallyn.com>

serge@hallyn.com wrote:
> Quoting BuraphaLinux Server (buraphalinuxserver@gmail.com):
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463669
>> 
>> I have the same problem - it is not debian specific.  Did the
>> semantics of kill() change with the new kernel?  I thought as long as
>> something is setuid, even with capability stuff around the setuid
>> programs just get _all_ capabilities and would keep working.
>> 
>> I did a good search and found many people with the problem, but no
>> solutions except going back to 2.6.23.x kernels.  I guess you'll flame
>> me, but at least include a link to the solution too.
> 
> Why would we flame you?  I'll just apologize as I think it's my fault,
> and ask you to please try the newest available kernel where I believe it
> should be fixed.

Would it be this commit that fixed this issue?
commit 094972840f2e7c1c6fc9e1a97d817cc17085378e
Author: Serge E. Hallyn <serue@us.ibm.com>
Date:   Sat Feb 23 15:23:33 2008 -0800
    file capabilities: simplify signal check

I see stable was CCed on it, so I guess it will be included in the next
point release, but distributions may want to apply it earlier.

  reply	other threads:[~2008-02-27 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 12:27 BuraphaLinux Server
2008-02-27 13:41 ` Jiri Kosina
2008-02-27 18:17 ` serge
2008-02-27 19:36   ` Frans Pop [this message]
2008-02-27 19:47   ` BuraphaLinux Server
2008-02-28  3:00     ` serge
2008-02-28  5:23       ` BuraphaLinux Server
2008-02-28 14:54         ` serge
2008-02-28 17:19         ` serge
2008-02-28 17:51           ` BuraphaLinux Server

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=E1JUS56-0001ur-Tq@faramir.fjphome.nl \
    --to=elendil@planet.nl \
    --cc=buraphalinuxserver@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge@hallyn.com \
    --subject='Re: at program breaks with kernel 2.6.24' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).