xfs: sparse warning fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | xfs: fix CIL sparse lock context warningsfs/ fs/ | +3 | 1 reply | |
| 2/5 | xfs: fix sparse warning in xfs_extent_busy_clearfs/ | +23 | 2 replies | |
| 3/5 | xfs: silence sparse warning when checking version numberfs/ | +1 | 2 replies | |
| 4/5 | xfs: remove unused is_rt_data_fork() functionfs/ | +0 | 2 replies | |
| 5/5 | xfs: fix sparse warnings about unused interval tree functionsfs/ | +12 | 2 replies |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by.
| Patch | Christoph Hellwig | Darrick J. Wong |
|---|---|---|
| 1/5 | R-b | |
| 2/5 | R-b | |
| 3/5 | R-b | R-b |
| 4/5 | R-b | R-b |
| 5/5 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] xfs: sparse warning fixes
In chasing down a recent regression, I realised I wasn't running sparse regularly on my "fs/xfs-only" kernel builds, and so I missed a warning that would have prevented a bug from slipping through.
I've modified my build scripts to always run sparse when I do these delta builds as I develop code, and I found a few other warnings that needed to be addressed. No bugs were uncovered - they are simply modifications and/or annotations to the code to address the warnings and make them go away.
There remains a couple of sparse warnings in the transaction reservation calculations - sparse throws "too many tokens" warnings from the max(t4, max3(t1, t2, t3)) calculations. These are sparse code parser issues, not a code problem, so I have ignored them for now.