From: serge@hallyn.com
To: David R <david@unsolicited.net>
Cc: serge@hallyn.com, 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 13:34:51 -0500 [thread overview]
Message-ID: <20080421183451.GA22071@vino.hallyn.com> (raw)
In-Reply-To: <20080421080101.htzh4s03snescog4@unsolicited.net>
Quoting David R (david@unsolicited.net):
> Quoting serge@hallyn.com:
>
> > Quoting David (david@unsolicited.net):
> >> Casey Schaufler wrote:
> >>> Do you have a libcap that reflects the change from 32 capabilities
> >>> to 64? You'll be looking for libcap.so.2.06 or thereabouts.
> >>>
> >> Adding libcap-2.08 and recompiling ntpd has fixed the issue, and I'm now
> >> running normally, thanks!
> >
> > I don't understand why, though. Looking at the ntpd code (ntp-4.2.4p4)
> > it just does a cap_set_proc(cap_from_text("X=epi")); It should simply
> > be sending in the _LINUX_CAPABILITY_VERSION which shipped with libcap,
> > which should have been _V1, and the kernel should honor that so long as
> > you didn't try to send in caps > 31, which ntpd wasn't.
> >
> >> Was this userspace visible change planned in advance for 2.6.25 ? ... as I
> >> guess a few other people with venerable old userspace components may come
> >> across this issue.
> >>
> >> Cheers
> >> David
> >
> > It's been in the works a long time and we thought we'd done pretty
> > well with backward compatibility. I really don't see why you had
> > that failure!
> >
> > Do you know which version of libcap you had before?
>
> /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)
thanks,
-serge
next prev parent reply other threads:[~2008-04-21 18:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:43 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 [this message]
2008-04-21 18:48 ` David
2008-04-21 19:01 ` serge
2008-04-21 20:28 ` David
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=20080421183451.GA22071@vino.hallyn.com \
--to=serge@hallyn.com \
--cc=casey@schaufler-ca.com \
--cc=david@unsolicited.net \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®