Your message dated Fri, 25 Sep 2009 14:59:36 +0200
with message-id <[email protected]>
and subject line Re: [pkg-cryptsetup-devel] Bug#547598: output an error message
if a module cannot be found
has caused the Debian Bug report #547598,
regarding output an error message if a module cannot be found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
547598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547598
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.7-2
Severity: normal
I've been bitten by initramfs not including the right modules
for cryptroot support a few times now.
By peeking in:
/usr/share/initramfs-tools/hooks/cryptroot
I believe the script does not output any warning if it fails to
find a module.
I believe the script should report missing modules, so the user
can manually tweak /etc/modules and regenerate the ramfs before
actually rebooting the system or having to play with grub.
Carlo
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.30-1-686 root=/dev/mapper/root ro quiet
-- /etc/crypttab
# <target name> <source device> <key file> <options>
root /dev/mapper/system-root none
cipher=aes-xts-essiv:wp256,size=256,hash=ripemd160
-- /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sda1 /boot ext2 noatime,nodev,nosuid,noexec,sync 0 2
/dev/mapper/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/mapper/root / ext3 commit=60,data=journal,errors=remount-ro 0 1
/dev/mapper/opt /opt ext3 commit=60,data=journal,errors=remount-ro 0 1
/dev/mapper/dumps /opt/dumps ext3 commit=60,data=journal,errors=remount-ro 0 2
-- lsmod
Module Size Used by
cpufreq_stats 3520 0
i915 147544 1
drm 137920 2 i915
i2c_algo_bit 4860 1 i915
ip6t_REJECT 3276 1
nf_conntrack_ipv6 11616 1
ip6table_filter 3084 1
ip6_tables 11316 1 ip6table_filter
ipt_REJECT 2496 1
nf_conntrack_ipv4 11928 1
nf_defrag_ipv4 1664 1 nf_conntrack_ipv4
xt_conntrack 3184 2
nf_conntrack 57924 3 nf_conntrack_ipv6,nf_conntrack_ipv4,xt_conntrack
iptable_filter 2956 1
ip_tables 10188 1 iptable_filter
x_tables 14108 5
ip6t_REJECT,ip6_tables,ipt_REJECT,xt_conntrack,ip_tables
joydev 8576 0
hdaps 9228 1
thinkpad_ec 6288 1 hdaps
ext2 54120 1
fuse 47752 1
snd_hda_codec_conexant 17164 1
arc4 1560 2
snd_hda_intel 22192 5
ecb 2368 2
snd_hda_codec 63580 2 snd_hda_codec_conexant,snd_hda_intel
snd_hwdep 6120 1 snd_hda_codec
snd_pcm_oss 32232 0
snd_mixer_oss 12368 3 snd_pcm_oss
snd_pcm 62420 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
iwlagn 72244 0
i2400m_usb 24368 0
iwlcore 92264 1 iwlagn
i2400m 69512 1 i2400m_usb
mac80211 142848 2 iwlagn,iwlcore
snd_timer 17436 1 snd_pcm
snd 49060 14
snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 6184 3 snd
cfg80211 55556 3 iwlagn,iwlcore,mac80211
wimax 22620 2 i2400m_usb,i2400m
uvcvideo 49308 0
thinkpad_acpi 55616 0
wmi 6184 0
led_class 3852 2 iwlcore,thinkpad_acpi
pcspkr 2104 0
nvram 6376 1 thinkpad_acpi
i2c_i801 8564 0
i2c_core 20844 4 i915,drm,i2c_algo_bit,i2c_i801
evdev 8028 22
videodev 31040 1 uvcvideo
snd_page_alloc 8180 2 snd_hda_intel,snd_pcm
serio_raw 4560 0
v4l1_compat 11416 2 uvcvideo,videodev
rfkill 9668 5 iwlcore,wimax,thinkpad_acpi
psmouse 37528 0
processor 34504 2
battery 6012 0
ac 2960 0
button 5060 0
ext3 107172 3
jbd 41036 1 ext3
mbcache 6924 2 ext2,ext3
sha256_generic 11216 0
cbc 3012 1
aes_i586 8092 11
aes_generic 27436 1 aes_i586
xts 2688 3
gf128mul 7708 1 xts
dm_crypt 11092 4
dm_mod 49992 23 dm_crypt
sd_mod 28748 3
crc_t10dif 1632 1 sd_mod
uhci_hcd 19132 0
ide_pci_generic 3632 0
ide_core 88100 1 ide_pci_generic
ahci 30068 2
ata_generic 4340 0
ehci_hcd 29680 0
libata 150904 2 ahci,ata_generic
usbcore 126004 5 i2400m_usb,uvcvideo,uhci_hcd,ehci_hcd
e1000e 98380 0
scsi_mod 131800 2 sd_mod,libata
intel_agp 22900 1
agpgart 30836 3 drm,intel_agp
video 18044 1 i915
output 2604 1 video
thermal 12580 0
fan 4044 0
thermal_sys 13140 4 processor,video,thermal,fan
wp512 25864 0
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (1100, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.36-4 The Linux Kernel Device Mapper use
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.36-4 The Linux Kernel Device Mapper use
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libuuid1 2.16-3 Universally Unique ID library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
pn dosfstools <none> (no description available)
ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii udev 0.141-2 /dev/ and hotplug management daemo
-- no debconf information
--- End Message ---
--- Begin Message ---
On 24/09/2009 Carlo Contavalli wrote:
> > unfortunately your suggestion is not an
> > option. in order to support system which do have some/all crypto support
> > compiled into the kernel adding modules to the initramfs will remain
> > quiet.
>
> uhm .. right, and I guess there is no way to check /boot/config* or
> the system map to verify if the needed code is in the kernel?
>
> Why not add a configuration parameter for all those who are using
> stock kernels and don't have crypto modules compiled in?
>
> Eg, the choice seems to be between (1) 'we remain silent, the output
> looks cool, but we might make the system unusable without warning the
> user' or (2) 'we sometimes output warnings that we shouldn't output'.
>
> If it was me, I'd pick 2, rather than 1 :-), maybe adding a text like
> 'watch out, if you have modules compiled it, you can probably ignore
> this warning', or better an option somewhere that defaults to 'yes,
> spit warnings for missing modules'.
i don't see a reason why cryptroot initramfs implementation should
check whether the kernel provides all required modules at all. after all
we're only talking about encrypted root filesystem, as only this one is
unlocked in intramfs. to create the encrypted device in the first place,
a working kernel was required. if people update their kernels later and
don't take care of requirements they're lost anyway. a system doesn't
check for required hardware drivers at installing new kernels either.
if there was a simple solution to warn about missing crypto modules etc,
then i would be fine with adding that to cryptroot, but i don't like the
idea to print loads of warnings about missing modules for kernels that
do have the crypto support compiled into the kernel image.
checking kernel config might be an option, but it would require a rather
complicated and error-prone config parsing implementation that would
need to be checked and updated for new kernel releases.
closing this bugreport for that reason.
greetings,
jonas
signature.asc
Description: Digital signature
--- End Message ---
