aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/checktransupdate.py
diff options
context:
space:
mode:
authorShuhao Fu <[email protected]>2025-08-27 18:24:19 +0000
committerSteve French <[email protected]>2025-08-27 19:59:06 +0000
commitab529e6ca1f67bcf31f3ea80c72bffde2e9e053e (patch)
tree9ec513c082fbbee48a0e6e242a12594ce2cf0692 /scripts/checktransupdate.py
parentsmb3 client: fix return code mapping of remap_file_range (diff)
downloadkernel-ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e.tar.gz
kernel-ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e.zip
fs/smb: Fix inconsistent refcnt update
A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic also gets ignored. Signed-off-by: Shuhao Fu <[email protected]> Acked-by: Paulo Alcantara (Red Hat) <[email protected]> Cc: [email protected] Signed-off-by: Steve French <[email protected]>
Diffstat (limited to 'scripts/checktransupdate.py')
0 files changed, 0 insertions, 0 deletions