glusterfs.git/xlators/mount, branch v9dev

mount/fuse: Wait for 'mount' child to exit before dying

2020-04-09T04:15:17+00:00

Problem:
tests/bugs/protocol/bug-1433815-auth-allow.t fails
sometimes because of stale mount. This stale mount
comes into picture when parent process dies without
waiting for the child process which mounts fuse fs
to die

Fix:
Wait for mounting child process to die before dying.

Fixes: #1152
Change-Id: I8baee8720e88614fdb762ea822d5877973eef8dc
Signed-off-by: Pranith Kumar K

mount.glusterfs: don't strip / from subdir-mounts

2020-02-20T13:11:33+00:00

Change-Id: Ib07c31dc6669aa9d9f84a21e6160237290ed9afb
Fixes: bz#1804786

fuse: degrade logging of write failure to fuse device

2020-01-09T19:43:55+00:00

Problem:

FUSE uses failures of communicating with /dev/fuse with various
errnos to indicate in-kernel conditions to userspace. Some of these
shouldn't be handled as an application error. Also the standard
POSIX errno description should not be shown as they are misleading
in this context.

Solution:

When writing to the fuse device, the caller of the respective
convenience routine can mask those errnos which don't qualify to
be an error for the application in that context, so then those
shall be reported at DEBUG level.

The possible non-standard errnos are reported with their
POSIX name instead of their description to avoid confusion.
(Eg. for ENOENT we don't log "no such file or directory",
we log indeed literal "ENOENT".)

Change-Id: I510158843e4b1d482bdc496c2e97b1860dc1ba93
updates: bz#1193929
Signed-off-by: Csaba Henk

Avoid buffer overwrite due to uuid_utoa() misuse

2019-12-27T16:59:42+00:00

Code like:

f(..., uuid_utoa(x), uuid_utoa(y));

is not valid (causes undefined behaviour) because uuid_utoa()
uses the only static thread-local buffer which will be overwritten
by the subsequent call. All such cases should be converted to use
uuid_utoa_r() with explicitly specified buffer.

Change-Id: I5e72bab806d96a9dd1707c28ed69ca033b9c8d6c
Updates: bz#1193929
Signed-off-by: Dmitry Antipov

fuse: add missing unlock

2019-12-10T10:27:58+00:00

updates: bz#1193929
Change-Id: I50f75f730ea6970e99347fcee661ce9dc8477725
Signed-off-by: Xie Changlong

ctime: Fix ctime inconsisteny with utimensat

2019-12-10T05:07:19+00:00

Problem:
When touch is used to create a file, the ctime is not matching
atime and mtime which ideally should match. There is a difference
in nano seconds.

Cause:
When touch is used modify atime or mtime to current time (UTIME_NOW),
the current time is taken from kernel. The ctime gets updated to current
time when atime or mtime is updated. But the current time to update
ctime is taken from utime xlator. Hence the difference in nano seconds.

Fix:
When utimesat uses UTIME_NOW, use the current time from kernel.

fixes: bz#1773530
Change-Id: I9ccfa47dcd39df23396852b4216f1773c49250ce
Signed-off-by: Kotresh HR

Improve logging of fusedump creation failure

2019-11-07T08:10:41+00:00

updates bz#1193929
Signed-off-by: Csaba Henk 
Change-Id: I12cbe1d87f60fb497654d0e13e12171940867f76

Multiple files: make root gfid a static variable

2019-10-14T08:21:52+00:00

In many places we use it, compare to it, etc. It could be a static variable,
as it really doesn't change. I think it's better than initializing to 0
and then doing gfid[15] = 1 or other tricks.

I think there are additional oppportunuties to make more variables static.
This is an attempt at an easy one.

Change-Id: I7f23a30a94056d8f043645371ab841cbd0f90d19
updates: bz#1193929
Signed-off-by: Yaniv Kaul

glusterfs/fuse: Reduce the default lru-limit value

2019-09-24T13:21:26+00:00

The current lru-limit value still uses memory for
upto 128K inodes.
Reduce the default value of lru-limit to 64K.

Change-Id: Ica2dd4f8f5fde45cb5180d8f02c3d86114ac52b3
Fixes: bz#1753880
Signed-off-by: N Balachandran

mount/fuse - Fixing a coverity issue

2019-08-20T06:29:13+00:00

Fixed resource leak of dict_value and newkey variables

CID: 1398630
Updates: bz#789278

Change-Id: I589fdc0aecaeb4f446cd29f95bad36ccd7a35beb
Signed-off-by: Barak Sason