diff options
| author | Sweet Tea Dorminy <[email protected]> | 2023-03-08 15:58:36 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2023-03-15 19:51:06 +0000 |
| commit | 10a8857a1beaa015efba7d56e06243d484549fb6 (patch) | |
| tree | f1509f52eb549d5aeef219df88338617fd576d9b /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
| parent | btrfs: handle missing chunk mapping more gracefully (diff) | |
| download | kernel-10a8857a1beaa015efba7d56e06243d484549fb6.tar.gz kernel-10a8857a1beaa015efba7d56e06243d484549fb6.zip | |
btrfs: fix compiler warning on SPARC/PA-RISC handling fscrypt_setup_filename
Commit 1ec49744ba83 ("btrfs: turn on -Wmaybe-uninitialized") exposed
that on SPARC and PA-RISC, gcc is unaware that fscrypt_setup_filename()
only returns negative error values or 0. This ultimately results in a
maybe-uninitialized warning in btrfs_lookup_dentry().
Change to only return negative error values or 0 from
fscrypt_setup_filename() at the relevant call site, and assert that no
positive error codes are returned (which would have wider implications
involving other users).
Reported-by: Guenter Roeck <[email protected]>
Link: https://lore.kernel.org/all/[email protected]/
Signed-off-by: Sweet Tea Dorminy <[email protected]>
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions