path: root/Documentation/devicetree
diff options
authorLinus Torvalds <torvalds@linux-foundation.org>2017-06-21 11:30:52 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2017-06-21 11:30:52 -0700
commit021f601980ccf07e65bc03e40d0321243f782d34 (patch)
tree549c2e7693bc40754f4fe1c1cd9f4dbaf5dc26b0 /Documentation/devicetree
parentbd726c90b6b8ce87602208701b208a208e6d5600 (diff)
parent77e9ce327d9b607cd6e57c0f4524a654dc59c4b1 (diff)
Merge branch 'ufs-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
Pull more ufs fixes from Al Viro: "More UFS fixes, unfortunately including build regression fix for the 64-bit s_dsize commit. Fixed in this pile: - trivial bug in signedness of 32bit timestamps on ufs1 - ESTALE instead of ufs_error() when doing open-by-fhandle on something deleted - build regression on 32bit in ufs_new_fragments() - calculating that many percents of u64 pulls libgcc stuff on some of those. Mea culpa. - fix hysteresis loop broken by typo in (right next to the location of previous bug). - fix the insane limits of said hysteresis loop on filesystems with very low percentage of reserved blocks. If it's 5% or less, just use the OPTSPACE policy. - calculate those limits once and mount time. This tree does pass xfstests clean (both ufs1 and ufs2) and it _does_ survive cross-builds. Again, my apologies for missing that, especially since I have noticed a related percentage-of-64bit issue in earlier patches (when dealing with amount of reserved blocks). Self-LART applied..." * 'ufs-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: ufs: fix the logics for tail relocation ufs_iget(): fail with -ESTALE on deleted inode fix signedness of timestamps on ufs1
Diffstat (limited to 'Documentation/devicetree')
0 files changed, 0 insertions, 0 deletions