linux.git/fs/xfs/xfs_vnodeops.c, branch v3.11

xfs: Add pquota fields where gquota is used.

2013-07-11T15:35:32+00:00

Add project quota changes to all the places where group quota field
is used:
   * add separate project quota members into various structures
   * split project quota and group quotas so that instead of overriding
     the group quota members incore, the new project quota members are
     used instead
   * get rid of usage of the OQUOTA flag incore, in favor of separate
     group and project quota flags.
   * add a project dquot argument to various functions.

Not using the pquotino field from superblock yet.

Signed-off-by: Chandra Seetharaman 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers

xfs: fix the symbolic link assert in xfs_ifree

2013-06-19T19:14:43+00:00

Adding an extended attribute to a symbolic link can force that
link to an remote extent. xfs_inactive() incorrectly assumes
that any symbolic link small enough to be in the inode core
is incore, resulting in the remote extent to not be removed.
xfs_ifree() will assert on presence of this leaked remote extent.

Signed-off-by: Mark Tinguely 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers

xfs: fix rounding in xfs_free_file_space

2013-05-20T19:25:50+00:00

The offset passed into xfs_free_file_space() needs to be rounded
down to a certain size, but the rounding mask is built by a 32 bit
variable. Hence the mask will always mask off the upper 32 bits of
the offset and lead to incorrect writeback and invalidation ranges.

This is not actually exposed as a bug because we writeback and
invalidate from the rounded offset to the end of the file, and hence
the offset we are actually punching a hole out of will always be
covered by the code. This needs fixing, however, if we ever want to
use exact ranges for writeback/invalidation here...

Signed-off-by: Dave Chinner 
Reviewed-by: Brian Foster 
Signed-off-by: Ben Myers

xfs: split out symlink code into it's own file.

2013-04-21T20:38:04+00:00

The symlink code is about to get more complicated when CRCs are
added for remote symlink blocks. The symlink management code is
mostly self contained, so move it to it's own files so that all the
new code and the existing symlink code will not be intermingled
with other unrelated code.

Signed-off-by: Dave Chinner 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers

xfs: take inode version into account in XFS_LITINO

2013-03-14T21:19:14+00:00

Add a version argument to XFS_LITINO so that it can return different values
depending on the inode version.  This is required for the upcoming v3 inodes
with a larger fixed layout dinode.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Dave Chinner 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers

xfs: Remove boolean_t typedef completely.

2013-01-17T23:32:57+00:00

Since we are using C99 we have one builtin defined in include/linux/types.h,
use that instead.

v2: you missed one in fs/xfs/xfs_qm_bhv.c, cleaned up. -bpm

Signed-off-by: Thiago Farina 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers

xfs: byte range granularity for XFS_IOC_ZERO_RANGE

2012-11-29T20:21:46+00:00

XFS_IOC_ZERO_RANGE simply does not work properly for non page cache
aligned ranges. Neither test 242 or 290 exercise this correctly, so
the behaviour is completely busted even though the tests pass.

Fix it to support full byte range granularity as was originally
intended for this ioctl.

Signed-off-by: Dave Chinner 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Ben Myers

xfs: make buffer read verication an IO completion function

2012-11-16T03:34:02+00:00

Add a verifier function callback capability to the buffer read
interfaces.  This will be used by the callers to supply a function
that verifies the contents of the buffer when it is read from disk.
This patch does not provide callback functions, but simply modifies
the interfaces to allow them to be called.

The reason for adding this to the read interfaces is that it is very
difficult to tell fom the outside is a buffer was just read from
disk or whether we just pulled it out of cache. Supplying a callbck
allows the buffer cache to use it's internal knowledge of the buffer
to execute it only when the buffer is read from disk.

It is intended that the verifier functions will mark the buffer with
an EFSCORRUPTED error when verification fails. This allows the
reading context to distinguish a verification error from an IO
error, and potentially take further actions on the buffer (e.g.
attempt repair) based on the error reported.

Signed-off-by: Dave Chinner 
Reviewed-by: Christoph Hellwig 
Reviewed-by: Phil White 
Signed-off-by: Ben Myers

xfs: remove xfs_flushinval_pages

2012-11-14T21:15:08+00:00

It's just a simple wrapper around VFS functionality, and is actually
bugging in that it doesn't remove mappings before invalidating the
page cache. Remove it and replace it with the correct VFS
functionality.

Signed-off-by: Dave Chinner 
Reviewed-by: Andrew Dahl 
Signed-off-by: Ben Myers

xfs: remove xfs_flush_pages

2012-11-14T21:12:45+00:00

It is a complex wrapper around VFS functions, but there are VFS
functions that provide exactly the same functionality. Call the VFS
functions directly and remove the unnecessary indirection and
complexity.

We don't need to care about clearing the XFS_ITRUNCATED flag, as
that is done during .writepages. Hence is cleared by the VFS
writeback path if there is anything to write back during the flush.

Signed-off-by: Dave Chinner 
Reviewed-by: Andrew Dahl 
Signed-off-by: Ben Myers