diff options
| author | Roberto Bergantinos Corpas <rbergant@redhat.com> | 2019-04-25 16:36:51 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-31 16:43:14 +0300 |
| commit | dab2c7d98f377202c66f948bffe4be637246758a (patch) | |
| tree | 10d9fb9395e537b896e14b812b3197bb17a56628 /fs/eventfd.c | |
| parent | 86edf5af379343f5b82085d924437d48e774e40e (diff) | |
| download | linux-dab2c7d98f377202c66f948bffe4be637246758a.tar.xz | |
NFS: make nfs_match_client killable
[ Upstream commit 950a578c6128c2886e295b9c7ecb0b6b22fcc92b ]
Actually we don't do anything with return value from
nfs_wait_client_init_complete in nfs_match_client, as a
consequence if we get a fatal signal and client is not
fully initialised, we'll loop to "again" label
This has been proven to cause soft lockups on some scenarios
(no-carrier but configured network interfaces)
Signed-off-by: Roberto Bergantinos Corpas <rbergant@redhat.com>
Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/eventfd.c')
0 files changed, 0 insertions, 0 deletions