Bug 433102

Summary: Port named to use libcap library
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: atkac, hduston, kasal, kernel-maint, mcepl, mcepl, mgalgoci, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-20 10:28:28 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235706    

Description Nicolas Mailhot 2008-02-16 06:25:57 EST
As noted in http://thread.gmane.org/gmane.linux.kernel/635219 recent kernels
require an up-to-date libcap for various apps to work 

(for example named is currently dead as a dodo in rawhide following the last
kernel update:
named: capset failed: Operation not permitted: please ensure that the capset
kernel module is loaded.  see insmod(8))

Please update to the latest version at 

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
Try to start the named service
Comment 1 Chuck Ebbert 2008-02-16 10:46:34 EST
According to that thread the message is just a warning and the app should still work
Comment 2 Nicolas Mailhot 2008-02-16 13:10:21 EST
It's plenty fatal enough, sorry
Comment 3 Adam Tkac 2008-02-18 07:21:16 EST
(In reply to comment #1)
> According to that thread the message is just a warning and the app should
still work

Hm, named doesn't use libcap for such syscall so it doesn't matter which version
is installed. It simply calls raw kernel interface (syscall(SYS_capset,
&caphead, &cap)). But when I changed (in /usr/include/linux/capability.h)




named works as expected. I'm not sure if this change will breaks other apps but
I think capability version 2 needs libcap version 2 (not sure, kernel people
will help with answer). Kernel crew could also try explain me why this syscall
is successful

capset(0x19980330, 0,
0}) = 0

but this is not

capset(0x20071026, 0,
0}) = -1 EPERM (Operation not permitted)

Where is main difference?
Comment 4 Adam Tkac 2008-02-18 07:22:36 EST
*** Bug 433075 has been marked as a duplicate of this bug. ***
Comment 5 Hal Duston 2008-02-18 11:45:42 EST
The difference is as follows:
0x19980303 is _LINUX_CAPABILITY_VERSION_1, and
Among the choices for getting bind working again are these:
1. Update bind to use libcap, and then libcap will handle any current and/or future version compatibility issues.
2. Compile bind against a set of 2.6.24 kernel headers, since I'd guess that 2.6.25 is where the capability version was bumped.
3. Patch bind to hardcode _LINUX_CAPABILITY_VERSION_1, since it is already hardcoding the rest of the system call.
   This would be in bin/named/unix/os.c#162
It doesn't seem likely that updating to the newer version of libcap would gain anything for bind with any of these choices.
Comment 6 Matthew Galgoci 2008-02-18 23:15:26 EST
It's pretty fatal for named

[root@workstation0 sysconfig]# service named start
Starting named: named: capset failed: Operation not permitted: please ensure
that the capset kernel module is loaded.  see insmod(8)
[root@workstation0 sysconfig]# 
Comment 7 Adam Tkac 2008-02-19 05:54:32 EST
Use libcap is the best and long term solution. I'm going to prepare patch,
temporary fixed in bind-9.5.0-27.b2.fc9 which is build without threads and linux
Comment 8 Adam Tkac 2008-02-20 08:14:54 EST
libcap 2.06 hits rawhide, reassigning to bind component + owner
Comment 9 Adam Tkac 2008-02-20 10:28:28 EST
bind 9.5.0-28.b2 uses libcap and works fine on all kernels with both 1 and 2
libcap versions. Information about patch is on