diff options
author | kay.sievers@vrfy.org <kay.sievers@vrfy.org> | 2004-10-13 23:13:26 -0700 |
---|---|---|
committer | Greg KH <gregkh@suse.de> | 2005-04-26 21:47:44 -0700 |
commit | 7e89a569cc4db0c1482662dc4df5f60df7aef3ff (patch) | |
tree | 815fbb823b795e99cb04096a38f3b049c71a9ee2 /README-gcov_for_udev | |
parent | c36f0ac34fa3bf8b952889b9197a5ee1ea5d2714 (diff) |
[PATCH] prevent deadlocks on an corrupt udev database
Here is the patch, that should prevent all of the known deadlocks with
corrupt tdb databases we discovered.
Thanks to Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>, who tested all this
endlessly with a NFS mounted /dev. The conclusion is, that udev will not work
on filesystems without proper record locking, but we should prevent the
endless loops anyway. This patch implements:
o recovery from a corrupted udev database. udev will continue
without database support now, instead of doing nothing. So the node should
be generated in any case, remove will obviously not work for custom names.
o added iteration limits to the tdb-code at the places we discovered endless
loops. In the case tdb tries to find more than 100.000 entries with the
same hash, we better give up :)
o prevent a {all_partitions} loop caused by corrupt db data
o log all tdb errors to syslog
o switch sleep() to usleep() cause we want to use alarm()
Diffstat (limited to 'README-gcov_for_udev')
0 files changed, 0 insertions, 0 deletions