29 Apr, 2008
1 commit
-
SGI-PV: 976035
SGI-Modid: xfs-linux-melb:xfs-kern:30913aSigned-off-by: Barry Naujok
Signed-off-by: Christoph Hellwig
Signed-off-by: Lachlan McIlroy
18 Apr, 2008
1 commit
-
There is no point to the CONFIG_XFS_SECURITY option; it disables the
ability to set security attributes at runtime, but it does not actually
slim down or remove any code for runtime. Just remove it and always allow
security attributes to be set.SGI-PV: 980310
SGI-Modid: xfs-linux-melb:xfs-kern:30877aSigned-off-by: Eric Sandeen
Signed-off-by: Tim Shimmin
Signed-off-by: Lachlan McIlroy
07 Feb, 2008
1 commit
-
These are mostly locking annotations, marking things static, casts where
needed and declaring stuff in header files.SGI-PV: 971186
SGI-Modid: xfs-linux-melb:xfs-kern:30002aSigned-off-by: David Chinner
Signed-off-by: Christoph Hellwig
Signed-off-by: Lachlan McIlroy
16 Oct, 2007
1 commit
-
SGI-PV: 969608
SGI-Modid: xfs-linux-melb:xfs-kern:29493aSigned-off-by: Christoph Hellwig
Signed-off-by: David Chinner
Signed-off-by: Tim Shimmin
15 Oct, 2007
1 commit
-
All vnode ops now take struct xfs_inode pointers and the behaviour related
glue is split out into methods of it's own. This required fixing
xfs_create/mkdir/symlink to not mess with the inode pointer but rather use
a separate boolean for error handling. Thanks to Dave Chinner for that
fix.SGI-PV: 969608
SGI-Modid: xfs-linux-melb:xfs-kern:29492aSigned-off-by: Christoph Hellwig
Signed-off-by: David Chinner
Signed-off-by: Tim Shimmin
08 May, 2007
1 commit
-
NULL.
Patch provided by Eric Sandeen.
SGI-PV: 961693
SGI-Modid: xfs-linux-melb:xfs-kern:28199aSigned-off-by: Eric Sandeen
Signed-off-by: Lachlan McIlroy
Signed-off-by: Tim Shimmin
10 Feb, 2007
3 commits
-
The firstblock argument to xfs_bmap_finish is not used by that function.
Remove it and cleanup the code a bit.Patch provided by Eric Sandeen.
SGI-PV: 960196
SGI-Modid: xfs-linux-melb:xfs-kern:28034aSigned-off-by: Eric Sandeen
Signed-off-by: David Chinner
Signed-off-by: Tim Shimmin -
SGI-PV: 958747
SGI-Modid: xfs-linux-melb:xfs-kern:27792aSigned-off-by: Barry Naujok
Signed-off-by: Russell Cattelan
Signed-off-by: Tim Shimmin -
gcc-4.1 and more recent aggressively inline static functions which
increases XFS stack usage by ~15% in critical paths. Prevent this from
occurring by adding noinline to the STATIC definition.Also uninline some functions that are too large to be inlined and were
causing problems with CONFIG_FORCED_INLINING=y.Finally, clean up all the different users of inline, __inline and
__inline__ and put them under one STATIC_INLINE macro. For debug kernels
the STATIC_INLINE macro uninlines those functions.SGI-PV: 957159
SGI-Modid: xfs-linux-melb:xfs-kern:27585aSigned-off-by: David Chinner
Signed-off-by: David Chatterton
Signed-off-by: Tim Shimmin
28 Sep, 2006
1 commit
-
code.
SGI-PV: 954372
SGI-Modid: xfs-linux-melb:xfs-kern:26583aSigned-off-by: Tim Shimmin
20 Jun, 2006
1 commit
-
pure bloat.
SGI-PV: 952969
SGI-Modid: xfs-linux-melb:xfs-kern:26251aSigned-off-by: Nathan Scott
09 Jun, 2006
2 commits
-
SGI-PV: 953338
SGI-Modid: xfs-linux-melb:xfs-kern:26107aSigned-off-by: Nathan Scott
-
the range spanned by modifications to the in-core extent map. Add
XFS_BUNMAPI() and XFS_SWAP_EXTENTS() macros that call xfs_bunmapi() and
xfs_swap_extents() via the ioops vector. Change all calls that may modify
the in-core extent map for the data fork to go through the ioops vector.
This allows a cache of extent map data to be kept in sync.SGI-PV: 947615
SGI-Modid: xfs-linux-melb:xfs-kern:209226aSigned-off-by: Olaf Weber
Signed-off-by: Nathan Scott
29 Mar, 2006
1 commit
-
these typos.
SGI-PV: 904196
SGI-Modid: xfs-linux-melb:xfs-kern:25539aSigned-off-by: Nathan Scott
17 Mar, 2006
6 commits
-
SGI-PV: 943272
SGI-Modid: xfs-linux-melb:xfs-kern:25505aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott -
SGI-PV: 943272
SGI-Modid: xfs-linux-melb:xfs-kern:25504aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott -
SGI-PV: 943272
SGI-Modid: xfs-linux-melb:xfs-kern:25498aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott -
SGI-PV: 943272
SGI-Modid: xfs-linux-melb:xfs-kern:25497aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott -
SGI-PV: 943272
SGI-Modid: xfs-linux-melb:xfs-kern:25495aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott -
SGI-PV: 947038
SGI-Modid: xfs-linux-melb:xfs-kern:25474aSigned-off-by: Nathan Scott
12 Jan, 2006
1 commit
-
fs: Use where capable() is used.
Signed-off-by: Randy Dunlap
Acked-by: Tim Schmielau
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
11 Jan, 2006
1 commit
-
remove checks now in the VFS
XFS has an additional xattr interface through obscure ioctl. it requires
raised capabilities but we need to add some read-only/immutable checks anywaySigned-off-by: Christoph Hellwig
Cc: Nathan Scott
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
02 Nov, 2005
5 commits
-
boilerplate.
SGI-PV: 913862
SGI-Modid: xfs-linux:xfs-kern:23903aSigned-off-by: Nathan Scott
-
SGI-PV: 943122
SGI-Modid: xfs-linux:xfs-kern:23901aSigned-off-by: Nathan Scott
-
the FreeBSD porters.
SGI-PV: 942906
SGI-Modid: xfs-linux:xfs-kern:23845aSigned-off-by: Nathan Scott
-
the data/attr forks now grow up/down from either end of the literal area,
rather than dividing the literal area into two chunks and growing both
upward. Means we can now make much more efficient use of the attribute
space, incl. fitting DMF attributes inline in 256 byte inodes, and large
jumps in dbench3 performance numbers. It is self enabling, but can be
forced on/off via the attr2/noattr2 mount options.SGI-PV: 941645
SGI-Modid: xfs-linux:xfs-kern:23835aSigned-off-by: Nathan Scott
-
attributes format change (attr2).
SGI-PV: 941645
SGI-Modid: xfs-linux:xfs-kern:23833aSigned-off-by: Nathan Scott
21 Jun, 2005
1 commit
-
SGI-PV: 936255
SGI-Modid: xfs-linux:xfs-kern:192760aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!