initrd stage: CAP_SYS_RAWIO on /dev/iscsictl fails . help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Subject :   Is CAP_SYS_RAWIO  not permitted during the  initrd stage in kernel 2.6.9-22 ?  It was permitted in 2.4.20 kernel. 

                 Installing and booting from iSCSI disk (worked in 2.4.20 , fails in 2.6.9-22 kernel).

 

 

Hi,

 

   I am in the initrd stage of boot .  Kernel 2.6.9-22 , Red Hat enterprise linux.

  During post-install stage and before the first  boot , I modified the initrd to have my iscsi driver and related daemon in initrd.

  The installation was made successfully to an iSCSI disk.  Now need to boot through it. 

  During the initrd stage in first-time-boot , my daemon gets the iSCSI device name from the remote storage server.

 

  “ now it wants to pass that information to iscsi-sfnet.ko via  IOCTL”  , the ioctl call returns error (-1) which is EPERM, the perror says—Inappropriate IOCTL”. Why that error return from sys_ioctl ?

 

   Is CAP_SYS_RAWIO or some other capability  not permitted during the  initrd stage in kernel 2.6.9-22? 

  

I have used the same thing in 2.4.20 kernel . works great.  I can install and also boot from the remote iSCSI disk  with my modified initrd in 2.4.20 kernels.

Are the new security features of 2.6 kernel ( security/seclvl.c)  hindering  this IOCTL operation  during initrd stage?

 

What is the solution to my problem. Is there a boot-time parameter ?

 

Please advice .

 

thanks

 

-Vikas

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux