diff options
| author | Benjamin Coddington <bcodding@redhat.com> | 2019-06-07 06:37:30 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-07-14 08:11:15 +0200 |
| commit | 810cfc3d9d2e4b345ba7e5d6290b00562e9e0d27 (patch) | |
| tree | d2d7cb0181b71e569692c8b4240a01bb709767f6 /net | |
| parent | 7075654ce7d0db9aaf5326dea586c35a041f3428 (diff) | |
| download | linux-stable-810cfc3d9d2e4b345ba7e5d6290b00562e9e0d27.tar.gz linux-stable-810cfc3d9d2e4b345ba7e5d6290b00562e9e0d27.tar.bz2 linux-stable-810cfc3d9d2e4b345ba7e5d6290b00562e9e0d27.zip | |
NFS4: Only set creation opendata if O_CREAT
[ Upstream commit 909105199a682cb09c500acd443d34b182846c9c ]
We can end up in nfs4_opendata_alloc during task exit, in which case
current->fs has already been cleaned up. This leads to a crash in
current_umask().
Fix this by only setting creation opendata if we are actually doing an open
with O_CREAT. We can drop the check for NULL nfs4_open_createattrs, since
O_CREAT will never be set for the recovery path.
Suggested-by: Trond Myklebust <trondmy@hammerspace.com>
Signed-off-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 'net')
0 files changed, 0 insertions, 0 deletions