This adds information on if xfs is in a transaction or not, and
if it is not, allows us to allocate with GFP_KERNEL. This improves
the chances of not getting an error back from the memory allocator.
Date: Fri Jan 25 09:47:08 PST 2002
Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: 2.4.x-xfs:slinx:110277a
linux/fs/xfs/xfs_trans.c - 1.125
- Maintain the current transaction in the current->journal_info pointer,
this will allow us to always tell if code is being called from within
a transaction or not.
linux/fs/xfs_support/kmem.c - 1.18
- If there is no xfs transaction pointer in the journal_info field for
the current task then it is safe to allocate memory using GFP_KERNEL
rather than GFP_NOFS.
|