linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: fixes for 4.16-rc4
Date: Wed, 28 Feb 2018 11:21:25 -0800	[thread overview]
Message-ID: <20180228192125.GM19312@magnolia> (raw)

Hi Linus,

Here's the first round of bugfixes for 4.16.  It should merge cleanly,
but please let me know if it doesn't.

--Darrick

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:

  Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.16-fixes-2

for you to fetch changes up to 5b4c845ea4f4b86c43096eb924354c83a2e26f3c:

  xfs: fix potential memory leak in mount option parsing (2018-02-26 10:02:13 -0800)

----------------------------------------------------------------
Changes since last update:
- Fix some compiler warnings
- Fix block rservations for transactions created during log recovery
- Fix resource leaks when respecifying mount options

----------------------------------------------------------------
Chengguang Xu (1):
      xfs: fix potential memory leak in mount option parsing

Darrick J. Wong (1):
      xfs: reserve blocks for refcount / rmap log item recovery

Eric Sandeen (1):
      xfs: use memset to initialize xfs_scrub_agfl_info

 fs/xfs/scrub/agheader.c    | 3 ++-
 fs/xfs/xfs_refcount_item.c | 9 ++++++---
 fs/xfs/xfs_rmap_item.c     | 4 +++-
 fs/xfs/xfs_super.c         | 2 ++
 4 files changed, 13 insertions(+), 5 deletions(-)

                 reply	other threads:[~2018-02-28 19:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180228192125.GM19312@magnolia \
    --to=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).