07981aa43f
I have come to consider BUG_ON generally harmful. The idea of an assert is to prevent a program to execute past a point where its state is known erroneous, thus preventing it from dealing more damage to the data (or hiding the traces of malfunction). The problem is, in kernel this harm has to be balanced against the harm of forced reboot. The last straw was our softmac tree, where "iwlist eth1 scan" causes a lockup. It is absolutely frivolus and provides no advantages a normal assert has to provide. In fact, doing this impedes debugging. Signed-off-by: Pete Zaitcev <zaitcev@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> |
||
---|---|---|
.. | ||
ieee80211_crypt_ccmp.c | ||
ieee80211_crypt_tkip.c | ||
ieee80211_crypt_wep.c | ||
ieee80211_crypt.c | ||
ieee80211_geo.c | ||
ieee80211_module.c | ||
ieee80211_rx.c | ||
ieee80211_tx.c | ||
ieee80211_wx.c | ||
Kconfig | ||
Makefile |