linux.git/fs/btrfs/ordered-data.h, branch v4.19

btrfs: remove remaing full_sync logic from btrfs_sync_file

2018-08-06T11:12:31+00:00

The logic to check if the inode is already in the log can now be
simplified since we always wait for the ordered extents to complete
before deciding whether the inode needs to be logged. The big comment
about it can go away too.

CC: Filipe Manana 
Suggested-by: Filipe Manana 
[ code and changelog copied from mail discussion ]
Signed-off-by: David Sterba

btrfs: remove the logged extents infrastructure

2018-08-06T11:12:30+00:00

This is no longer used anywhere, remove all of it.

Signed-off-by: Josef Bacik 
Reviewed-by: Filipe Manana 
Signed-off-by: David Sterba

btrfs: replace GPL boilerplate by SPDX -- headers

2018-04-12T14:29:46+00:00

Remove GPL boilerplate text (long, short, one-line) and keep the rest,
ie. personal, company or original source copyright statements. Add the
SPDX header.

Unify the include protection macros to match the file names.

Signed-off-by: David Sterba

btrfs: add more __cold annotations

2018-03-26T13:09:39+00:00

The __cold functions are placed to a special section, as they're
expected to be called rarely. This could help i-cache prefetches or help
compiler to decide which branches are more/less likely to be taken
without any other annotations needed.

Though we can't add more __exit annotations, it's still possible to add
__cold (that's also added with __exit). That way the following function
categories are tagged:

- printf wrappers, error messages
- exit helpers

Signed-off-by: David Sterba

btrfs: Don't hardcode the csum size in btrfs_ordered_sum_size

2018-03-26T13:09:29+00:00

Currently the function uses a hardcoded value for the checksum size of
a sector. This is fine, given that we currently support only a single
algorithm, whose checksum is 4 bytes == sizeof(u32). Despite not
having other algorithms, btrfs' design supports using a different
algorithm whith different space requirements. To future-proof the code
query the size of the currently used algorithm from the in-memory copy
of the super block. No functional changes.

Signed-off-by: Nikolay Borisov 
Reviewed-by: Qu Wenruo 
Reviewed-by: Su Yue 
Signed-off-by: David Sterba

btrfs: fix integer overflow in calc_reclaim_items_nr

2017-06-29T18:17:02+00:00

Dave Jones hit a WARN_ON(nr < 0) in btrfs_wait_ordered_roots() with
v4.12-rc6.  This was because commit 70e7af244 made it possible for
calc_reclaim_items_nr() to return a negative number.  It's not really a
bug in that commit, it just didn't go far enough down the stack to find
all the possible 64->32 bit overflows.

This switches calc_reclaim_items_nr() to return a u64 and changes everyone
that uses the results of that math to u64 as well.

Reported-by: Dave Jones 
Fixes: 70e7af2 ("Btrfs: fix delalloc accounting leak caused by u32 overflow")
Signed-off-by: Chris Mason 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: convert btrfs_ordered_extent.refs from atomic_t to refcount_t

2017-04-18T12:07:23+00:00

refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.

Signed-off-by: Elena Reshetova 
Signed-off-by: Hans Liljestrand 
Signed-off-by: Kees Cook 
Signed-off-by: David Windsor 
Signed-off-by: David Sterba

btrfs: Make btrfs_lookup_ordered_range take btrfs_inode

2017-02-28T10:30:08+00:00

Signed-off-by: Nikolay Borisov 
Signed-off-by: David Sterba

Btrfs: specify a new ordered extent type for create_io_em

2017-02-17T11:03:48+00:00

As 0 refers to an existing type BTRFS_ORDERED_IO_DONE, this specifies a
new type 'REGULAR' for regular IO.

Signed-off-by: Liu Bo 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: Make btrfs_get_logged_extents take btrfs_inode

2017-02-14T14:50:55+00:00

Signed-off-by: Nikolay Borisov 
Signed-off-by: David Sterba