linux.git/fs/dlm, branch v5.1

socket: Rename SO_RCVTIMEO/ SO_SNDTIMEO with _OLD suffixes

2019-02-03T19:17:31+00:00

SO_RCVTIMEO and SO_SNDTIMEO socket options use struct timeval
as the time format. struct timeval is not y2038 safe.
The subsequent patches in the series add support for new socket
timeout options with _NEW suffix that will use y2038 safe
data structures. Although the existing struct timeval layout
is sufficiently wide to represent timeouts, because of the way
libc will interpret time_t based on user defined flag, these
new flags provide a way of having a structure that is the same
for all architectures consistently.
Rename the existing options with _OLD suffix forms so that the
right option is enabled for userspace applications according
to the architecture and time_t definition of libc.

Signed-off-by: Deepa Dinamani 
Acked-by: Willem de Bruijn 
Cc: ccaulfie@redhat.com
Cc: deller@gmx.de
Cc: paulus@samba.org
Cc: ralf@linux-mips.org
Cc: rth@twiddle.net
Cc: cluster-devel@redhat.com
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-alpha@vger.kernel.org
Cc: linux-arch@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Cc: linux-parisc@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Signed-off-by: David S. Miller

dlm: fix invalid cluster name warning

2018-12-03T21:30:24+00:00

The warning added in commit 3b0e761ba83
  "dlm: print log message when cluster name is not set"

did not account for the fact that lockspaces created
from userland do not supply a cluster name, so bogus
warnings are printed every time a userland lockspace
is created.

Signed-off-by: David Teigland

dlm: NULL check before some freeing functions is not needed

2018-12-03T16:02:01+00:00

NULL check before some freeing functions is not needed.

Signed-off-by: Thomas Meyer 
Signed-off-by: David Teigland

dlm: NULL check before kmem_cache_destroy is not needed

2018-11-28T14:45:55+00:00

kmem_cache_destroy(NULL) is safe, so removes NULL check before
freeing the mem. This patch also fix ifnullfree.cocci warnings.

Signed-off-by: Wen Yang 
Signed-off-by: David Teigland

dlm: fix missing idr_destroy for recover_idr

2018-11-15T17:21:21+00:00

Which would leak memory for the idr internals.

Signed-off-by: David Teigland

dlm: memory leaks on error path in dlm_user_request()

2018-11-15T15:57:22+00:00

According to comment in dlm_user_request() ua should be freed
in dlm_free_lkb() after successful attach to lkb.

However ua is attached to lkb not in set_lock_args() but later,
inside request_lock().

Fixes 597d0cae0f99 ("[DLM] dlm: user locks")
Cc: stable@kernel.org # 2.6.19

Signed-off-by: Vasily Averin 
Signed-off-by: David Teigland

dlm: lost put_lkb on error path in receive_convert() and receive_unlock()

2018-11-15T15:57:22+00:00

Fixes 6d40c4a708e0 ("dlm: improve error and debug messages")
Cc: stable@kernel.org # 3.5

Signed-off-by: Vasily Averin 
Signed-off-by: David Teigland

dlm: possible memory leak on error path in create_lkb()

2018-11-15T15:57:22+00:00

Fixes 3d6aa675fff9 ("dlm: keep lkbs in idr")
Cc: stable@kernel.org # 3.1

Signed-off-by: Vasily Averin 
Signed-off-by: David Teigland

dlm: fixed memory leaks after failed ls_remove_names allocation

2018-11-15T15:57:22+00:00

If allocation fails on last elements of array need to free already
allocated elements.

v2: just move existing out_rsbtbl label to right place

Fixes 789924ba635f ("dlm: fix race between remove and lookup")
Cc: stable@kernel.org # 3.6

Signed-off-by: Vasily Averin 
Signed-off-by: David Teigland

dlm: fix possible call to kfree() for non-initialized pointer

2018-11-13T17:41:09+00:00

Technically dlm_config_nodes() could return error and keep nodes
uninitialized. After that on the fail path of we'll call kfree()
for that uninitialized value.

The patch is simple - we should just initialize nodes with NULL.

Signed-off-by: Denis V. Lunev 
Signed-off-by: David Teigland