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.15-rc2
Date: Fri, 1 Dec 2017 12:51:39 -0800	[thread overview]
Message-ID: <20171201205139.GV21412@magnolia> (raw)

Hi Linus,

Here are some bug fixes for 4.15-rc2.

--D

The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:

  Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.15-fixes-4

for you to fetch changes up to 373b0589dc8d58bc09c9a28d03611ae4fb216057:

  xfs: Properly retry failed dquot items in case of error during buffer writeback (2017-11-30 08:47:40 -0800)

----------------------------------------------------------------
Changes since last update:
- Fix memory leaks that appeared after removing ifork inline data buffer
- Recover deferred rmap update log items in correct order
- Fix memory leaks when buffer construction fails
- Fix memory leaks when bmbt is corrupt
- Fix some uninitialized variables and math problems in the quota scrubber
- Add some omitted attribution tags on the log replay commit
- Fix some UBSAN complaints about integer overflows with large sparse files
- Implement an effective inode mode check in online fsck
- Fix log's inability to retry quota item writeout due to transient errors

----------------------------------------------------------------
Carlos Maiolino (1):
      xfs: Properly retry failed dquot items in case of error during buffer writeback

Darrick J. Wong (5):
      xfs: always free inline data before resetting inode fork during ifree
      xfs: log recovery should replay deferred ops in order
      xfs: ubsan fixes
      xfs: remove unused parameter from xfs_writepage_map
      xfs: scrub inode mode properly

Eric Sandeen (3):
      xfs: fix leaks on corruption errors in xfs_bmap.c
      xfs: fix uninitialized variable in xfs_scrub_quota
      xfs: calculate correct offset in xfs_scrub_quota_item

Michal Hocko (1):
      xfs: fortify xfs_alloc_buftarg error handling

 fs/xfs/libxfs/xfs_bmap.c   |  6 ++--
 fs/xfs/scrub/inode.c       | 14 ++++++++-
 fs/xfs/scrub/quota.c       |  4 +--
 fs/xfs/xfs_aops.c          | 12 ++++----
 fs/xfs/xfs_bmap_item.c     | 23 +++++---------
 fs/xfs/xfs_bmap_item.h     |  3 +-
 fs/xfs/xfs_buf.c           | 15 ++++++----
 fs/xfs/xfs_dquot.c         | 14 +++++++--
 fs/xfs/xfs_dquot_item.c    | 40 +++++++++++++++++++++++--
 fs/xfs/xfs_inode.c         | 21 +++++++++++++
 fs/xfs/xfs_log_recover.c   | 75 +++++++++++++++++++++++++++++++++++++++++-----
 fs/xfs/xfs_refcount_item.c | 21 +++++--------
 fs/xfs/xfs_refcount_item.h |  3 +-
 13 files changed, 190 insertions(+), 61 deletions(-)

                 reply	other threads:[~2017-12-01 20:51 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=20171201205139.GV21412@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).