06 Jan, 2009
2 commits
-
This is safer. We no longer have to worry about tracking changes to
jbd_state_bits.Signed-off-by: Mark Fasheh
-
Add an optional validation hook to ocfs2_read_blocks(). Now the
validation function is only called when a block was actually read off of
disk. It is not called when the buffer was in cache.We add a buffer state bit BH_NeedsValidate to flag these buffers. It
must always be one higher than the last JBD2 buffer state bit.The dinode, dirblock, extent_block, and xattr_block validators are
lifted to this scheme directly. The group_descriptor validator needs to
be split into two pieces. The first part only needs the gd buffer and
is passed to ocfs2_read_block(). The second part requires the dinode as
well, and is called every time. It's only 3 compares, so it's tiny.
This also allows us to clean up the non-fatal gd check used by resize.c.
It now has no magic argument.Signed-off-by: Joel Becker
Signed-off-by: Mark Fasheh
02 Dec, 2008
1 commit
-
We're panicing in ocfs2_read_blocks_sync() if a jbd-managed buffer is seen.
At first glance, this seems ok but in reality it can happen. My test case
was to just run 'exorcist'. A struct inode is being pushed out of memory but
is then re-read at a later time, before the buffer has been checkpointed by
jbd. This causes a BUG to be hit in ocfs2_read_blocks_sync().Reviewed-by: Joel Becker
Signed-off-by: Mark Fasheh
15 Oct, 2008
3 commits
-
ocfs2_read_blocks() currently requires the CACHED flag for cached I/O.
However, that's the common case. Let's flip it around and provide an
IGNORE_CACHE flag for the special users. This has the added benefit of
cleaning up the code some (ignore_cache takes on its special meaning
earlier in the loop).Signed-off-by: Joel Becker
Signed-off-by: Mark Fasheh -
Now that synchronous readers are using ocfs2_read_blocks_sync(), all
callers of ocfs2_read_blocks() are passing an inode. Use it
unconditionally. Since it's there, we don't need to pass the
ocfs2_super either.Signed-off-by: Joel Becker
Signed-off-by: Mark Fasheh -
The ocfs2_read_blocks() function currently handles sync reads, cached,
reads, and sometimes cached reads. We're going to add some
functionality to it, so first we should simplify it. The uncached,
synchronous reads are much easer to handle as a separate function, so we
instroduce ocfs2_read_blocks_sync().Signed-off-by: Joel Becker
Signed-off-by: Mark Fasheh
26 Jan, 2008
2 commits
-
If we know a buffer_head is non-null, then brelse() is unnecessary and
put_bh() can be used instead. Also, an explicit check for NULL is
unnecessary when using brelse(). This patch only covers buffer_head_io.c and
resize.c, which have recently added code which exhibits this problem.Signed-off-by: Mark Fasheh
-
This patch adds the ability for a userspace program to request an extend of
last cluster group on an Ocfs2 file system. The request is made via ioctl,
OCFS2_IOC_GROUP_EXTEND. This is derived from EXT3_IOC_GROUP_EXTEND, but is
obviously Ocfs2 specific.tunefs.ocfs2 would call this for an online-resize operation if the last
cluster group isn't full.Signed-off-by: Tao Ma
Signed-off-by: Mark Fasheh
21 Sep, 2006
1 commit
-
Uptodate.c now knows about read-ahead buffers. Use some more aggressive
logic in ocfs2_readdir().The two functions which currently use directory read-ahead are
ocfs2_find_entry() and ocfs2_readdir().Signed-off-by: Mark Fasheh
25 Mar, 2006
1 commit
-
Signed-off-by: Mark Fasheh
04 Feb, 2006
1 commit
-
ip_io_sem is now ip_io_mutex.
Signed-off-by: Mark Fasheh
04 Jan, 2006
1 commit
-
The OCFS2 file system module.
Signed-off-by: Mark Fasheh
Signed-off-by: Kurt Hackel