[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94dd5feed72c391b6204a11658c1bc8f0a8f8cd6.camel@kernel.org>
Date: Tue, 12 Jan 2021 12:00:24 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Sukadev Bhattiprolu <sukadev@...ux.ibm.com>, netdev@...r.kernel.org
Cc: Dany Madden <drt@...ux.ibm.com>, Lijun Pan <ljp@...ux.ibm.com>,
Rick Lindsley <ricklind@...ux.ibm.com>
Subject: Re: [PATCH net-next v2 0/7] ibmvnic: Use more consistent locking
On Tue, 2021-01-12 at 10:14 -0800, Sukadev Bhattiprolu wrote:
> Use more consistent locking when reading/writing the adapter->state
> field. This patch set fixes a race condition during ibmvnic_open()
> where the adapter could be left in the PROBED state if a reset occurs
> at the wrong time. This can cause networking to not come up during
> boot and potentially require manual intervention in bringing up
> applications that depend on the network.
>
> Changelog[v2] [Address comments from Jakub Kicinski]
> - Fix up commit log for patch 5/7 and drop unnecessary variable
> - Format Fixes line properly (no wrapping, no blank lines)
>
> Sukadev Bhattiprolu (7):
> ibmvnic: restore state in change-param reset
> ibmvnic: update reset function prototypes
> ibmvnic: avoid allocating rwi entries
> ibmvnic: switch order of checks in ibmvnic_reset
> ibmvnic: serialize access to work queue
> ibmvnic: check adapter->state under state_lock
> ibmvnic: add comments about state_lock
>
>
Other than the two minor comments,
Reviewed-by: Saeed Mahameed <saeedm@...dia.com>
Powered by blists - more mailing lists