diff options
author | David S. Miller <davem@davemloft.net> | 2018-05-24 22:19:26 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-05-24 22:19:26 -0400 |
commit | 49a473f5b5f54f33e0bd8618158d33f83153c921 (patch) | |
tree | 82c1983fa92ac5f26aeeefa6b1e34aea1fb901f8 /samples/bpf/Makefile | |
parent | 180f848b8f71f0a016888d722802809dd3b32462 (diff) | |
parent | 2770a7984db588913e11a6dfcfe3461dbba9b7b2 (diff) | |
download | linux-49a473f5b5f54f33e0bd8618158d33f83153c921.tar.gz linux-49a473f5b5f54f33e0bd8618158d33f83153c921.tar.bz2 linux-49a473f5b5f54f33e0bd8618158d33f83153c921.zip |
Merge branch 'ibmvnic-Failover-hardening'
Thomas Falcon says:
====================
ibmvnic: Failover hardening
Introduce additional transport event hardening to handle
events during device reset. In the driver's current state,
if a transport event is received during device reset, it can
cause the device to become unresponsive as invalid operations
are processed as the backing device context changes. After
a transport event, the device expects a request to begin the
initialization process. If the driver is still processing
a previously queued device reset in this state, it is likely
to fail as firmware will reject any commands other than the
one to initialize the client driver's Command-Response Queue.
Instead of failing and becoming dormant, the driver will make
one more attempt to recover and continue operation. This is
achieved by setting a state flag, which if true will direct
the driver to clean up all allocated resources and perform
a hard reset in an attempt to bring the driver back to an
operational state.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'samples/bpf/Makefile')
0 files changed, 0 insertions, 0 deletions