kernel_replicant_linux/fs/xfs/Makefile, branch v4.13-rc5

xfs: use the common helper uuid_is_null()

2017-06-05T14:59:08+00:00

Use the common helper uuid_is_null() and remove the xfs specific
helper uuid_is_nil().

The common helper does not check for the NULL pointer value as
xfs helper did, but xfs code never calls the helper with a pointer
that can be NULL.

Conform comments and warning strings to use the term 'null uuid'
instead of 'nil uuid', because this is the terminology used by
lib/uuid.c and its users. It is also the terminology used in
userspace by libuuid and xfsprogs.

Signed-off-by: Amir Goldstein 
[hch: remove now unused uuid.[ch]]
Signed-off-by: Christoph Hellwig 
Reviewed-by: Brian Foster 
Reviewed-by: Andy Shevchenko

xfs: implement the GETFSMAP ioctl

2017-04-03T22:18:17+00:00

Introduce a new ioctl that uses the reverse mapping btree to return
information about the physical layout of the filesystem.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Brian Foster

xfs: introduce the CoW fork

2016-10-05T01:06:40+00:00

Introduce a new in-core fork for storing copy-on-write delalloc
reservations and allocated extents that are in the process of being
written out.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig

xfs: log bmap intent items

2016-10-04T18:05:44+00:00

Provide a mechanism for higher levels to create BUI/BUD items, submit
them to the log, and a stub function to deal with recovered BUI items.
These parts will be connected to the rmapbt in a later patch.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig

xfs: create bmbt update intent log items

2016-10-04T18:05:43+00:00

Create bmbt update intent/done log items to record redo information in
the log.  Because we roll transactions multiple times for reflink
operations, we also have to track the status of the metadata updates
that will be recorded in the post-roll transactions in case we crash
before committing the final transaction.  This mechanism enables log
recovery to finish what was already started.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig

xfs: log refcount intent items

2016-10-03T16:11:21+00:00

Provide a mechanism for higher levels to create CUI/CUD items, submit
them to the log, and a stub function to deal with recovered CUI items.
These parts will be connected to the refcountbt in a later patch.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig

xfs: create refcount update intent log items

2016-10-03T16:11:20+00:00

Create refcount update intent/done log items to record redo
information in the log.  Because we need to roll transactions between
updating the bmbt mapping and updating the reverse mapping, we also
have to track the status of the metadata updates that will be recorded
in the post-roll transactions, just in case we crash before committing
the final transaction.  This mechanism enables log recovery to finish
what was already started.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig

xfs: add refcount btree operations

2016-10-03T16:11:19+00:00

Implement the generic btree operations required to manipulate refcount
btree blocks.  The implementation is similar to the bmapbt, though it
will only allocate and free blocks from the AG.

Since the refcount root and level fields are separate from the
existing roots and levels array, they need a separate logging flag.

Signed-off-by: Darrick J. Wong 
[hch: fix logging of AGF refcount btree fields]
Signed-off-by: Christoph Hellwig

xfs: define the on-disk refcount btree format

2016-10-03T16:11:18+00:00

Start constructing the refcount btree implementation by establishing
the on-disk format and everything needed to read, write, and
manipulate the refcount btree blocks.

Signed-off-by: Darrick J. Wong 
Signed-off-by: Christoph Hellwig 
Reviewed-by: Christoph Hellwig

xfs: set up per-AG free space reservations

2016-09-19T00:30:52+00:00

One unfortunate quirk of the reference count and reverse mapping
btrees -- they can expand in size when blocks are written to *other*
allocation groups if, say, one large extent becomes a lot of tiny
extents.  Since we don't want to start throwing errors in the middle
of CoWing, we need to reserve some blocks to handle future expansion.
The transaction block reservation counters aren't sufficient here
because we have to have a reserve of blocks in every AG, not just
somewhere in the filesystem.

Therefore, create two per-AG block reservation pools.  One feeds the
AGFL so that rmapbt expansion always succeeds, and the other feeds all
other metadata so that refcountbt expansion never fails.

Use the count of how many reserved blocks we need to have on hand to
create a virtual reservation in the AG.  Through selective clamping of
the maximum length of allocation requests and of the length of the
longest free extent, we can make it look like there's less free space
in the AG unless the reservation owner is asking for blocks.

In other words, play some accounting tricks in-core to make sure that
we always have blocks available.  On the plus side, there's nothing to
clean up if we crash, which is contrast to the strategy that the rough
draft used (actually removing extents from the freespace btrees).

Signed-off-by: Darrick J. Wong 
Reviewed-by: Dave Chinner 
Signed-off-by: Dave Chinner