summaryrefslogtreecommitdiffstats
path: root/fs/gfs2/incore.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-04-14 10:52:54 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2013-04-14 10:52:54 -0700
commit3792a64fdeeb9cab56c22695aaeb0624f1b295b4 (patch)
tree6867fa61e0a61e87f3ec273248339dd72666afd2 /fs/gfs2/incore.h
parent3c91930f0cbd54d522d8844b221c36199a2dc11e (diff)
parent4bc4bee4595662d8bff92180d5c32e3313a704b0 (diff)
downloadop-kernel-dev-3792a64fdeeb9cab56c22695aaeb0624f1b295b4.zip
op-kernel-dev-3792a64fdeeb9cab56c22695aaeb0624f1b295b4.tar.gz
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
Pull one more btrfs fix from Chris Mason: "This has a recent fix from Josef for our tree log replay code. It fixes problems where the inode counter for the number of bytes in the file wasn't getting updated properly during fsync replay. The commit did get rebased this morning, but it was only to clean up the subject line. The code hasn't changed." * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs: Btrfs: make sure nbytes are right after log replay
Diffstat (limited to 'fs/gfs2/incore.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud