summaryrefslogtreecommitdiff
path: root/Kconfig
diff options
context:
space:
mode:
authorJohn Garry <john.g.garry@oracle.com>2024-05-02 10:08:26 +0000
committerChandan Babu R <chandanbabu@kernel.org>2024-05-27 15:54:24 +0530
commitb33874fb7f28326380562f208d948bab785fbd6f (patch)
tree7f276483793494f6cc70b1431f7ec66e33ff5382 /Kconfig
parentd7ba701da636afae17d8e1243b3d12eed149abcb (diff)
xfs: Stop using __maybe_unused in xfs_alloc.c
In both xfs_alloc_cur_finish() and xfs_alloc_ag_vextent_exact(), local variable @afg is tagged as __maybe_unused. Otherwise an unused variable warning would be generated for when building with W=1 and CONFIG_XFS_DEBUG unset. In both cases, the variable is unused as it is only referenced in an ASSERT() call, which is compiled out (in this config). It is generally a poor programming style to use __maybe_unused for variables. The ASSERT() call is to verify that agbno of the end of the extent is within bounds for both functions. @afg is used as an intermediate variable to find the AG length. However xfs_verify_agbext() already exists to verify a valid extent range. The arguments for calling xfs_verify_agbext() are already available, so use that instead. An advantage of using xfs_verify_agbext() is that it verifies that both the start and the end of the extent are within the bounds of the AG and catches overflows. Suggested-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: John Garry <john.g.garry@oracle.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions