Greg Kroah-Hartman 154d4899e4 iwlwifi: mvm: properly check debugfs dentry before using it ... debugfs can now report an error code if something went wrong instead of just NULL. So if the return value is to be used as a "real" dentry, it needs to be checked if it is an error before dereferencing it. This is now happening because of ff9fb72bc0 ("debugfs: return error values, not NULL"). If multiple iwlwifi devices are in the system, this can cause problems when the driver attempts to create the main debugfs directory again. Later on in the code we fail horribly by trying to dereference a pointer that is an error value. Reported-by: Laura Abbott <labbott@redhat.com> Reported-by: Gabriel Ramirez <gabriello.ramirez@gmail.com> Cc: Johannes Berg <johannes.berg@intel.com> Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Cc: Luca Coelho <luciano.coelho@intel.com> Cc: Intel Linux Wireless <linuxwifi@intel.com> Cc: Kalle Valo <kvalo@codeaurora.org> Cc: stable <stable@vger.kernel.org> # 5.0 Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>		2019-04-18 15:06:44 +03:00
..
ipw2x00	wireless-drivers-next patches for 4.21	2018-12-20 16:47:10 -08:00
iwlegacy	iwlegacy: no need to check return value of debugfs_create functions	2019-02-01 14:28:59 +02:00
iwlwifi	iwlwifi: mvm: properly check debugfs dentry before using it	2019-04-18 15:06:44 +03:00
Kconfig	net/wireless: fix spaces and grammar copy/paste in vendor Kconfig help text	2018-03-13 18:52:25 +02:00
Makefile