SGI Modid: 2.5.x-xfs:slinx:132214a

SGI Modid: 2.5.x-xfs:slinx:132176a

SGI Modid: 2.5.x-xfs:slinx:132045a

SGI Modid: 2.5.x-xfs:slinx:131939a

SGI Modid: 2.5.x-xfs:slinx:131630a

SGI Modid: 2.5.x-xfs:slinx:131565a

We can't allow quota state changes on a read-only device,
this would kick of a failing transaction & shut down the fs.
Previously the test was quota/no quota but we need to disallow
any change wrt user and/or group quota state.

SGI Modid: 2.5.x-xfs:slinx:131554a

a separate file, xfs_iomap.c out of xfs_lrw.c. Remove some parts
of the code which were not doing anything for us. This is step
one in some major reorgs of this code.

SGI Modid: 2.5.x-xfs:slinx:131524a

SGI Modid: 2.5.x-xfs:slinx:131504a

SGI Modid: 2.5.x-xfs:slinx:131490a

SGI Modid: 2.5.x-xfs:slinx:131438a

SGI Modid: 2.5.x-xfs:slinx:131386a

the layout of a log record for a buffer, the linux code deals with buffers
which are not contiguous in memory - this only applies to an inode buffer.
This adds one more fragmentation case to the code, and a line was missing
from this. The end result would be the logging of too much data if this
was not the last component of the buffer.

The code was definitely wrong, but I think the chances of hitting this were
pretty slim, and the resulting error would only matter if there was a
crash shortly afterward.

SGI Modid: 2.5.x-xfs:slinx:131221a

SGI Modid: 2.5.x-xfs:slinx:131187a

SGI Modid: 2.5.x-xfs:slinx:131618a

devices (log/realtime).  path_init was missing the LOOKUP_POSITIVE
flag, so it would fail to tell us if the file doesn't exist, there
was a spot where we were returning the wrong signedness for the code,
and when mount is failing, we can call into xfs_blkdev_put with a
NULL pointer depending on which devices were initialised and which
weren't.

SGI Modid: 2.5.x-xfs:slinx:131469a

SGI Modid: 2.5.x-xfs:slinx:131214a

SGI Modid: 2.5.x-xfs:slinx:131185a

SGI Modid: 2.5.x-xfs:slinx:131130a

SGI Modid: 2.5.x-xfs:slinx:130837a

SGI Modid: 2.5.x-xfs:slinx:130823a

SGI Modid: 2.5.x-xfs:slinx:130709a

the standard permission bits, and remove existing attrs
if acls are reduced to standard permissions.

SGI Modid: 2.5.x-xfs:slinx:130256a

longer needs to be declared globally here.

SGI Modid: 2.5.x-xfs:slinx:130827a

and struct inodes down in with the rest of the Linux-specific code.

SGI Modid: 2.5.x-xfs:slinx:130824a

SGI Modid: 2.5.x-xfs:slinx:130598a

SGI Modid: 2.5.x-xfs:slinx:130589a

with a directory block size larger than the filesystem (and hence attr)
blocksize.  This does not affect filesystems built with default mkfs.xfs
parameters, and only hits when a large number of attributes are set on
an inode.

SGI Modid: 2.5.x-xfs:slinx:130577a

SGI Modid: 2.5.x-xfs:slinx:130575a

headers.  Allows us to not repeat the xfs_stratcb declaration in several
places.  Also rename linvfs_set_inode_ops to xfs_set_inodeops since its
an auxillary routine not a linvfs method.

SGI Modid: 2.5.x-xfs:slinx:130573a

a few weeks ago with the rework of the target device pointer between the
xfs_mount and pb_target structures.

SGI Modid: 2.5.x-xfs:slinx:130572a

a kernel panic on certain option strings.

SGI Modid: 2.5.x-xfs:slinx:130571a

There's only the one, in XFS.

  - Add the library function read_cache_pages(), which is used in a
    similar fashion to the single page 'read_cache_page()'. It hides
    the details of the LRU cache etc. from a filesystem that wants to
    to populate an address space with a list of pages.

  - Fix NFS so that readahead uses the ->readpages() interface. Means
    that we can immediately schedule an RPC call in order to complete
    the I/O, rather than relying on somebody later triggering it by
    calling lock_page() (and hence sync_page()). The sync_page()
    method is race-prone, since the waiting page may try to call it
    before we've finished initializing the 'struct nfs_page'.

  - Clear out nfs_sync_page(), the nfs_inode->read list, and
    friends. When the I/O completion gets scheduled in ->readpage(),
    ->readpages(), they have no reason to exist.

The following patch makes the ->readpages() address_space_operation
take a struct file argument just like ->readpage().

This is the second iteration of thread-aware coredumps.

Changes:

- Ulrich Drepper has reviewed the data structures and checked actual
  coredumps via readelf - everything looks fine and according to the spec.

- a serious bug has been fixed in the thread-state dumping code - it was
  still based on the 2.4 assumption that the task struct points to the
  kernel stack - it's task->thread_info in 2.5. This bug caused bogus
  register info to be filled in for threads.

- properly wait for all threads that share the same MM to serialize with
  the coredumping thread. This is CLONE_VM based, not tied to
  CLONE_THREAD and/or signal semantics, ie. old-style (or different-style)
  threaded apps will be properly stopped as well.

  The locking might look a bit complex, but i wanted to keep the
  __exit_mm() overhead as low as possible. It's not quite trivial to get
  these bits right, because 'sharing the MM' is detached from signals
  semantics, so we cannot rely on broadcast-kill catching all threads. So
  zap_threads() iterates through every thread and zaps those which were
  left out. (There's a minimal race left in where a newly forked child
  might escape the attention of zap_threads() - this race is fixed by the
  OOM fixes in the mmap-speedup patch.)

- fill_psinfo() is now called with the thread group leader, for the
  coredump to get 'process' state.

 - initialize the elf_thread_status structure with zeroes.

the IA64 ELF bits are not included, yet, to reduce complexity of the
patch. The patch has been tested on x86 UP and SMP.