glusterfs.git/xlators/features, branch master

bitrot/stub: Fix memory leak gf_br_stub_mt_version_t

2020-09-30T17:04:03+00:00

The data type gf_br_stub_mt_version_t is leaking because the
data type has been added to the dict as static type and the memory
is not free'd from anywhere else

Change-Id: Ib10134f41f45a39be849af1708b1960c77fb62fd
Fixes: #1427
Signed-off-by: Mohammed Rafi KC

locks: null dereference

2020-09-29T14:04:11+00:00

Added a null check before executing the strtok_r()
to avoid null dereference in case of strdup() failure.

CID: 1407938
Updates: #1060

Change-Id: Iec6e72ae8cb54f6d0a287615c43756325b2026ec
Signed-off-by: nik-redhat

xlators: prefer libglusterfs time API

2020-09-07T12:56:45+00:00

Prefer timespec_now_realtime() and gf_time() over clock_gettime()
and time(), use gf_tvdiff() and gf_tsdiff() where appropriate,
drop unused time_elapsed() and leftovers in 'struct posix_private'.

Change-Id: Ie1f0229df5b03d0862193ce2b7fb91d27b0981b6
Signed-off-by: Dmitry Antipov 
Updates: #1002

core: Avoid dict OR key is NULL message in brick logs

2020-09-04T07:23:09+00:00

Problem: At the time of mount a volume server_first_lookup
        call's syncop_lookup with a NULL xattr so index_lookup
        is throwing a message at the time of fetching "link-count"
        from a dictionary

Solution: Call dict_get_str_sizen instead of calling dict_get_str
          to avoid a warning message

Fixes: #1464
Change-Id: I2b1ee3123ab817fa09f3abe39998c0d66ac0b824
Signed-off-by: Mohit Agrawal

features/quota: simplify and cleanup internal time management

2020-08-24T09:49:13+00:00

Since this xlator measures time intervals in seconds,
gettimeofday() may be replaced with simpler gf_time().
Simplify and convert quota_timeout() to static as well.

Change-Id: I0e042cdd759dd9fca25fcf8bc780e5fc4934f7e1
Signed-off-by: Dmitry Antipov 
Updates: #1002

features/changelog: simplify and cleanup internal time management

2020-08-22T03:48:19+00:00

Drop extra point of failure in changelog_fill_rollover_data(),
changelog_init() and reconfigure(), consistently use time_t
and gf_time() where appropriate, adjust all related users.

Change-Id: Id8e4236e96789cd74da5fdc3da05f0c1df98a62b
Signed-off-by: Dmitry Antipov 
Updates: #1002

metadisp: new translator for data and metadata separation

2020-08-21T14:11:23+00:00

Summary:

feature/metadisp is an xlator for performing "metadata dispersal" across
multiple children. it does this by flattening the complex
POSIX paths into /$GFID style paths, then forwarding the
metadata operations to its first child and forwarding the
data operations to its second child.

The purpose of this xlator is to allow separation of data and metadata,
in cases where metadata might be stored in another format (embedded kv?),
on another disk (ssd), on another host (dht2).

Change-Id: I392c8bd0c867a3237d144aea327323f700a2728d
Updates: #816
Signed-Off-By: Sheena Artrip 
Tested-By: Amar Tumballi

features/locks: simplify and cleanup internal time management

2020-08-21T14:06:09+00:00

Since this xlator measures time intervals in seconds,
gettimeofday() may be replaced with simpler gf_time().

Change-Id: Ib2c81376c093613124bdbed184516077cbe80dac
Signed-off-by: Dmitry Antipov 
Updates: #1002

features/bit-rot: simplify and cleanup internal time management

2020-08-21T14:05:13+00:00

Since this xlator measures time intervals in seconds, gettimeofday() may
be replaced with simpler gf_time(). Adjust comments and style as well.

Signed-off-by: Dmitry Antipov 
Change-Id: I2e5900ccb5da2478656d80e5f570487e3ba70966
Updates: #1002

features/shard: optimization over shard lookup in case of prealloc

2020-08-20T06:02:19+00:00

Assume that we are preallocating a VM of size 1TB with a shard
block size of 64MB then there will be ~16k shards.

This creation happens in 2 steps shard_fallocate() path i.e

1. lookup for the shards if any already present and
2. mknod over those shards do not exist.

But in case of fresh creation, we dont have to lookup for all
shards which are not present as the the file size will be 0.
Through this, we can save lookup on all shards which are not
present. This optimization is quite useful in the case of
preallocating big vm.

Also if the file is already present and the call is to
extend it to bigger size then we need not to lookup for non-
existent shards. Just lookup preexisting shards, populate
the inodes and issue mknod on extended size.

Fixes: #1425
Change-Id: I60036fe8302c696e0ca80ff11ab0ef5bcdbd7880
Signed-off-by: Vinayakswami Hariharmath