summaryrefslogtreecommitdiff
path: root/drivers/net/ethernet/intel/i40evf
diff options
context:
space:
mode:
authorMitch Williams <mitch.a.williams@intel.com>2018-01-22 12:00:32 -0500
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2018-02-13 11:40:10 -0800
commit7be78aa444794d4d242f8192c627df57e2cc2e98 (patch)
treec300e09b6f78806f5cb5ea84db175088f3781912 /drivers/net/ethernet/intel/i40evf
parent03f431b33a6486680ff4e43b059176720bb41972 (diff)
downloadlinux-7be78aa444794d4d242f8192c627df57e2cc2e98.tar.gz
linux-7be78aa444794d4d242f8192c627df57e2cc2e98.tar.bz2
linux-7be78aa444794d4d242f8192c627df57e2cc2e98.zip
i40e: don't leak memory addresses
Could a Bad Person do Bad Things to a server if they found these addresses printed in the log? Who knows? But let's not take that risk. Remove pointers from a bunch of printks. In some cases, I was able to adjust the message to indicate whether or not the value was null. In others, I just removed the entire message as there was really no hope of saving it. Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ethernet/intel/i40evf')
0 files changed, 0 insertions, 0 deletions