summaryrefslogtreecommitdiff
path: root/contrib/dissector_fuzz.sh
AgeCommit message (Expand)AuthorFilesLines
2018-12-10contrib: move auxiliary scripts to own directoryTobias Klauser1-0/+79
ption value='5'>5space:mode:
authorMatti Gottlieb <matti.gottlieb@intel.com>2016-04-10 10:53:57 +0300
committerEmmanuel Grumbach <emmanuel.grumbach@intel.com>2016-04-12 11:52:39 +0300
commitf742aaf36edf0390c54d0614bc4d20fd4cd3762a (patch)
tree21644d7af66fb39be2a2b7f7a23b4b23959d893d /Documentation/kobject.txt
parente1ba684f762b9a8064de2c916bb60b1694dd8a17 (diff)
iwlwifi: mvm: fix accessing Null pointer during fw dump collection
The firwmare file can come with data that is relevant for paging. This data is availablet to the firmware upon request, but it stored in the host's memory. During the firmware init flow, the driver configures the firmware so that the firwmare knows where is the data. When paging is used, the variable paging_mem_size is the number of bytes that are available through paging. This variable is not zeror-ed if the driver fails to configure the paging in the firmware, but the memory is freed which is inconsistent. This inconsistency led to a NULL pointer dereference in the code that collects the debug data. Fix this by zero-ing the paging_mem_size variable and NULLify the relevant pointers, so that the code that collects the debug data will know that the paging data is not available. Signed-off-by: Matti Gottlieb <matti.gottlieb@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'Documentation/kobject.txt')