diff options
author | 2020-03-12 18:25:20 -0400 | |
---|---|---|
committer | 2020-03-12 18:25:20 -0400 | |
commit | d9a9f4849fe0c9d560851ab22a85a666cddfdd24 (patch) | |
tree | ad95e615975c7e052ffa8ad0d1e446653d1cc45e /arch | |
parent | gfs2_atomic_open(): fix O_EXCL|O_CREAT handling on cold dcache (diff) | |
download | linux-d9a9f4849fe0c9d560851ab22a85a666cddfdd24.tar.gz linux-d9a9f4849fe0c9d560851ab22a85a666cddfdd24.tar.bz2 linux-d9a9f4849fe0c9d560851ab22a85a666cddfdd24.zip |
cifs_atomic_open(): fix double-put on late allocation failure
several iterations of ->atomic_open() calling conventions ago, we
used to need fput() if ->atomic_open() failed at some point after
successful finish_open(). Now (since 2016) it's not needed -
struct file carries enough state to make fput() work regardless
of the point in struct file lifecycle and discarding it on
failure exits in open() got unified. Unfortunately, I'd missed
the fact that we had an instance of ->atomic_open() (cifs one)
that used to need that fput(), as well as the stale comment in
finish_open() demanding such late failure handling. Trivially
fixed...
Fixes: fe9ec8291fca "do_last(): take fput() on error after opening to out:"
Cc: stable@kernel.org # v4.7+
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions