All of lore.kernel.org
 help / color / mirror / Atom feed
From: David <david@unsolicited.net>
To: serge@hallyn.com
Cc: casey@schaufler-ca.com, Mike Galbraith <efault@gmx.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morgan <morgan@kernel.org>
Subject: Re: 2.6.25 Kernel - Problems with capabilities
Date: Mon, 21 Apr 2008 21:28:11 +0100	[thread overview]
Message-ID: <480CF8DB.9010405@unsolicited.net> (raw)
In-Reply-To: <20080421190143.GA23365@vino.hallyn.com>

serge@hallyn.com wrote:
> Quoting David (david@unsolicited.net):
>   
>> serge@hallyn.com wrote:
>>     
>>>> /lib/libcap.so.1 -> libcap.so.1.92
>>>>
>>>> I guess that's 1.92 (should be the version shipped with SuSE 9.1).
>>>>     
>>>>         
>>> Ok, thanks, then it's definately not what I was thinking.
>>>
>>> (Will wait to check out your strace)
>>>   
>>>       
>> strace attached.
>>
>> Cheers
>> David
>>
>>     
>
> ...
>   
>> capget(0x20071026, 0, {, , })           = -1 EINVAL (Invalid argument)
>>     
>
> This is odd.  libcap-1.x should be passing in 0x19980330.
>
> Next, given the -EINVAL return value ntpd should be seeing a NULL result
> from cap_get_proc() and exiting right there.
>
> What version of ntpd is this?  (I must be looking at a wrong value, but
> even so the fact that cap_get_proc()->capget() is using 0x20071026 for
> version doesn't make sense)
>
>   
>> capset(0, 0, {CAP_NET_BIND_SERVICE|CAP_SYS_TIME, CAP_NET_BIND_SERVICE|CAP_SYS_TIME, CAP_NET_BIND_SERVICE|CAP_SYS_TIME}) = -1 EINVAL (Invalid argument)
>> time(NULL)                              = 1208803493
>> write(5, "21 Apr 19:44:53 ntpd[6118]: cap_"..., 92) = 92
>> munmap(0x40022000, 4096)                = 0
>> exit_group(-1)                          = ?
>> Process 6118 detached
>>     
>
>   
Oh dear .. more investigation... here's the source from libcap-1.92. 
capget() is being called with null arguments, which I guess returns with 
the latest version in ch.version ?

The switch then fails and the set gets called with version = 0 ??

Cheers
David

void _libcap_establish_api(void)
{
    struct __user_cap_header_struct ch;
    struct __user_cap_data_struct cs;

    if (_libcap_kernel_version) {
        _cap_debug("already identified kernal api 0x%.8x",
                   _libcap_kernel_version);
        return;
    }

    memset(&ch, 0, sizeof(ch));
    memset(&cs, 0, sizeof(cs));

    (void) capget(&ch, &cs);

    switch (ch.version) {

    case 0x19980330:
        _libcap_kernel_version = 0x19980330;
        _libcap_kernel_features = CAP_FEATURE_PROC;
        break;

    case 0x19990414:
        _libcap_kernel_version = 0x19990414;
        _libcap_kernel_features = CAP_FEATURE_PROC|CAP_FEATURE_FILE;
        break;

    default:
        _libcap_kernel_version = 0x00000000;
        _libcap_kernel_features = 0x00000000;
    }

    _cap_debug("version: %x, features: %x\n",
               _libcap_kernel_version, _libcap_kernel_features);
}


> thanks,
> -serge
>   


  reply	other threads:[~2008-04-21 20:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 18:43 2.6.25 Kernel - Problems with capabilities David
     [not found] ` <1208676743.4763.10.camel@marge.simson.net>
2008-04-20 14:09   ` David
2008-04-20 17:15     ` Casey Schaufler
2008-04-20 17:29       ` David
2008-04-20 19:08         ` Andi Kleen
2008-04-20 22:04           ` Casey Schaufler
2008-04-20 22:36             ` Andi Kleen
2008-04-21  0:00         ` serge
2008-04-21  0:44           ` Andrew Morgan
2008-04-21  7:20             ` David R
2008-04-21  7:01           ` David R
2008-04-21 18:34             ` serge
2008-04-21 18:48               ` David
2008-04-21 19:01                 ` serge
2008-04-21 20:28                   ` David [this message]
2008-04-22  2:42                     ` serge
2008-04-22  5:29                       ` Andrew G. Morgan
2008-04-22  5:54                         ` David R
2008-04-20 22:21     ` Andrew Morton

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=480CF8DB.9010405@unsolicited.net \
    --to=david@unsolicited.net \
    --cc=casey@schaufler-ca.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=serge@hallyn.com \
    /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.