All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] dlm updates for 4.21
Date: Wed, 19 Dec 2018 11:17:22 -0600	[thread overview]
Message-ID: <20181219171722.GA14517@redhat.com> (raw)

Hi Linus,

Please pull dlm updates from tag:

git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.21

This set is entirely trivial fixes, mainly around correct cleanup
on error paths and improved error checks.  One patch adds scheduling
in a potentially long recovery loop.

Thanks,
Dave

Bob Peterson (1):
      dlm: Don't swamp the CPU with callbacks queued during recovery

David Teigland (2):
      dlm: fix missing idr_destroy for recover_idr
      dlm: fix invalid cluster name warning

Denis V. Lunev (1):
      dlm: fix possible call to kfree() for non-initialized pointer

Thomas Meyer (1):
      dlm: NULL check before some freeing functions is not needed

Tycho Andersen (3):
      dlm: fix invalid free
      dlm: don't allow zero length names
      dlm: don't leak kernel pointer to userspace

Vasily Averin (4):
      dlm: fixed memory leaks after failed ls_remove_names allocation
      dlm: possible memory leak on error path in create_lkb()
      dlm: lost put_lkb on error path in receive_convert() and receive_unlock()
      dlm: memory leaks on error path in dlm_user_request()

Wen Yang (1):
      dlm: NULL check before kmem_cache_destroy is not needed

 fs/dlm/ast.c       | 10 ++++++++++
 fs/dlm/lock.c      | 17 ++++++++++-------
 fs/dlm/lockspace.c |  9 ++++-----
 fs/dlm/member.c    |  7 ++++---
 fs/dlm/memory.c    |  9 +++------
 fs/dlm/user.c      |  5 +++--
 6 files changed, 34 insertions(+), 23 deletions(-)


             reply	other threads:[~2018-12-19 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 17:17 David Teigland [this message]
2018-12-28  1:45 ` [GIT PULL] dlm updates for 4.21 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181219171722.GA14517@redhat.com \
    --to=teigland@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.