summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorRobert Peterson <rpeterso@redhat.com>2007-06-12 11:24:36 -0500
committerSteven Whitehouse <swhiteho@redhat.com>2007-07-09 08:23:40 +0100
commit8fb68595d508fd30ec90939572484b263600376c (patch)
tree218a457675c111e2224fb57998d38e45d5786bd1 /README
parentfad59c1390045b5adb7c7249ec4e77e0f868aca5 (diff)
downloadop-kernel-dev-8fb68595d508fd30ec90939572484b263600376c.zip
op-kernel-dev-8fb68595d508fd30ec90939572484b263600376c.tar.gz
[GFS2] Journaled file write/unstuff bug
This patch is for bugzilla bug 283162, which uncovered a number of bugs pertaining to writing to files that have the journaled bit on. These bugs happen most often when writing to the meta_fs because the files are always journaled. So operations like gfs2_grow were particularly vulnerable, although many of the problems could be recreated with normal files after setting the journaled bit on. The problems fixed are: -GFS2 wasn't ever writing unstuffed journaled data blocks to their in-place location on disk. Now it does. -If you unmounted too quickly after doing IO to a journaled file, GFS2 was crashing because you would discard a buffer whose bufdata was still on the active items list. GFS2 now deals with this gracefully. -GFS2 was losing track of the bufdata for journaled data blocks, and it wasn't getting freed, causing an error when you tried to unmount the module. GFS2 now frees all the bufdata structures. -There was a memory corruption occurring because GFS2 wrote twice as many log entries for journaled buffers. -It was occasionally trying to write journal headers in buffers that weren't currently mapped. Signed-off-by: Bob Peterson <rpeterso@redhat.com> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud