Re: Unable to boot with encrypted swap

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

 



On 05/17/2013 03:38 AM, Michael Chapman wrote:
> On Thu, 16 May 2013, Colin Guthrie wrote:
>> Yeah it's almost certainly only for resume from suspend. Sadly this is
>> controlled by the resume= kernel command line and when the initrd is
>> generated it doesn't really know if it'll be needed or not.
> 
> I think Dracut could use the the "swap" flag in crypttab to determine that a
> volume is definitely not needed on boot, since this tells systemd-cryptsetup
> that the swap needs to be recreated on boot. And since this is a "plain"
> dm-crypt encrypted device, the (randomly generated) encryption key isn't dropped
> from the kernel on hibernation -- so, I don't think the initrd needs to touch it
> upon resuming from hibernation either.

fixed with commit bcfbddefe13d179d553da77cf66ada5e6fd804c8

Thanks for reporting!
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux