diff options
author | Neil Horman <[email protected]> | 2013-01-15 14:34:40 -0500 |
---|---|---|
committer | Robert Love <[email protected]> | 2013-01-28 11:13:01 -0800 |
commit | f9184df3b99375964340c1a78e33f304bbf15f06 (patch) | |
tree | 740f3bdd627c95ee5856127dcbc0ff97ca310146 /drivers/scsi/mpt2sas/mpi/mpi2_raid.h | |
parent | cf02820041668b14cbfa0fbd2bab45ac79bd6174 (diff) |
fcoe: close race on link speed detection in fcoe code
When creating an fcoe interfce, we call fcoe_link_speed_update before we add the
lports fcoe interface to the fc_hostlist. Since network device events like
NETDEV_CHANGE are only processed if an fcoe interface is found with an
underlying netdev that matches the netdev of the event. Since this processing
in fcoe_device_notification is how link_speed changes get communicated to the
libfc code (via fcoe_link_speed_update), we have a race condition - if a
NETDEV_CHANGE event is sent after the call to fcoe_link_speed_update in
fcoe_netdev_config, but before we add the interface to the fc_hostlist, we will
loose the event and attributes like /sys/class/fc_host/hostX/speed will not get
updated properly.
Fix this by moving the add to the fc_hostlist above the serialized call to
fcoe_netdev_config, ensuring that we catch netdev envents before we make a
direct call to fcoe_link_speed_update.
Also use this opportunity to clean up access to the fc_hostlist a bit by
creating a fcoe_hostlist_del accessor and replacing the cleanup in fcoe_exit to
use it properly.
Tested by myself successfully
[ Comment over 80 chars broken into multi-line by Robert Love to
satisfy checkpatch.pl ]
Signed-off-by: Neil Horman <[email protected]>
Reviewed-by: Yi Zou <[email protected]>
Signed-off-by: Robert Love <[email protected]>
Diffstat (limited to 'drivers/scsi/mpt2sas/mpi/mpi2_raid.h')
0 files changed, 0 insertions, 0 deletions