summaryrefslogtreecommitdiffstats
path: root/drivers/regulator
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2016-06-01 15:29:13 +0200
committerDavid S. Miller <davem@davemloft.net>2016-06-02 07:04:54 +0200
commit14b84e8654c89ed59f433654e6bb64c886d095cd (patch)
tree133468288259491c2cc894f757f51d5a3a763b8b /drivers/regulator
parentnet/ethoc: fix null dereference on error exit path (diff)
downloadlinux-14b84e8654c89ed59f433654e6bb64c886d095cd.tar.xz
linux-14b84e8654c89ed59f433654e6bb64c886d095cd.zip
qed: fix qed_fill_link() error handling
gcc warns about qed_fill_link possibly accessing uninitialized data: drivers/net/ethernet/qlogic/qed/qed_main.c: In function 'qed_fill_link': drivers/net/ethernet/qlogic/qed/qed_main.c:1170:35: error: 'link_caps' may be used uninitialized in this function [-Werror=maybe-uninitialized] While this warning is only about the specific case of CONFIG_QED_SRIOV being disabled but the function getting called for a VF (which should never happen), another possibility is that qed_mcp_get_*() fails without returning data. This rearranges the code so we bail out in either of the two cases and print a warning instead of accessing the uninitialized data. The qed_link_output structure remains untouched in this case, but all callers first call memset() on it, so at least we are not leaking stack data then. As discussed, we also use a compile-time check to ensure we never use any of the VF code if CONFIG_QED_SRIOV is disabled, and the PCI device table is updated to no longer bind to virtual functions in that configuration. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Yuval Mintz <Yuval.Mintz@qlogic.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions