https://bugzilla.novell.com/show_bug.cgi?id=461333
Summary: pam_mount: crypted home directories are not unmounted on
logout
Product: openSUSE 11.1
Version: Final
Platform: 64bit
OS/Version: openSUSE 11.1
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: e.kunig@home.nl
QAContact: qa@suse.de
Found By: Customer
I have setup a crypted home directory for myself. It is not unmounted on
logout. Therefore I get more and more active mounts and loop devices with each
login. After 7 times login is not possible, as no more loop devices have been
left. Even worse, my home directory is not protected after logout, as it is
still mounted.
I have added some logging to /sbin/umount.crypt. I have found, that pulseaudio
is not terminating quick enough. Therefore my home directory is busy, when
pam_umount tries to unmount it. Here are the logged messages:
Dec 21 18:13:04 zappa logger: umount.crypt: /home/egbert
Dec 21 18:13:05 zappa umount.crypto: COMMAND PID USER FD TYPE DEVICE
S
IZE/OFF NODE NAME
Dec 21 18:13:05 zappa umount.crypto: pulseaudi 10493 egbert 21uW REG 253,24
13159 262161
/home/egbert/.pulse/982b04cfa1ba0ba3dccea400478cfd28:stream-volum
es.x86_64-suse-linux-gnu.gdbm
Dec 21 18:13:05 zappa umount.crypto: pulseaudi 10493 egbert 22uW REG 253,24
13189 262191
/home/egbert/.pulse/982b04cfa1ba0ba3dccea400478cfd28:device-volum
es.x86_64-suse-linux-gnu.gdbm
Dec 21 18:13:05 zappa umount.crypto: umount: /home/egbert: device is busy.
Dec 21 18:13:05 zappa umount.crypto: (In some cases useful info about
pr
ocesses that use
Dec 21 18:13:05 zappa umount.crypto: the device is found by lsof(8) or
fuser(1))
Dec 21 18:13:05 zappa umount.crypto: umount.crypt: error unmounting
/home/egbert
Dec 21 18:14:23 zappa root: umount.crypt: /home/egbert
Dec 21 18:14:24 zappa umount.crypto: ioctl: LOOP_CLR_FD: No such device or
addre
ss
Dec 21 18:14:24 zappa umount.crypto: umount.crypt: error removing /dev/loop2
As a workaround I have deactivated pulseaudio be removing the executable
permission:
chmod a-x /usr/bin/pulseaudio
This bug is critical, as data are not protected, while user might trust on
this.
There is a comment in /sbin/umount.crypt, line 57-60:
#
#