Bug 1419222

Description of problem:

I have successfully used the swap option of crypttab (# man crypttab)
to encrypt the swap partition dynamically. rc.sysinit enables that 
swap partition successfully at the right point (after encryption). 

The same doesn't work for the tmp option of crypttab (# man crypttab).
The encrypted partition is present after booting the system. Manually   
mounting it works but adding "/dev/mapper/luks-tmp" into fstab shows that 
the boot process tries to mount it too early (not encrypted yet). 

This is confusing because other encrypted volumes (not dynamically) 
in fstab are successfully mounted. 

Okay, I see (line 842 /etc/rc.d/init.d/functions). It seems that 
volumes with random keys are skipped at that stage.


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

initscripts-9.03.53-1.el6.1


How reproducible:

echo "luks-tmp /dev/device /dev/urandom tmp" >> /etc/crypttab
echo "/dev/mapper/luks-tmp /tmp	ext4	defaults 1 2" >> /etc/fstab  


Actual results:
Failure while booting respectively while mounting general fstab entries
 

Expected results:
mounting /tmp after encryption


Solution info:
rc.sysinit should skip volumes and memorize them that have key_is_random() 
while in the general mounting loop.

after mounting / rw and feeding random device, the line 563 in rc.sysinit will
generate the tmp enc fs. Therefore after this the mount loop must be called 
again but just for the memorized (skipped) volumes.