From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for 5.3-rc6
Date: Fri, 23 Aug 2019 09:34:39 -0700 [thread overview]
Message-ID: <20190823163439.GL1037350@magnolia> (raw)
Hi Linus,
Here are a few more bug fixes that trickled in since the last pull.
They've survived the usual xfstests runs and merge cleanly with this
morning's master. Please let me know if anything strange happens.
I expect there to be one more pull request tomorrow for the fix to that
quota related inode unlock bug that we were reviewing last night, but it
will continue to soak in the testing machine for several more hours.
--D
The following changes since commit 8612de3f7ba6e900465e340516b8313806d27b2d:
xfs: don't crash on null attr fork xfs_bmapi_read (2019-08-12 09:32:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.3-fixes-4
for you to fetch changes up to b68271609c4f16a79eae8069933f64345afcf888:
fs/xfs: Fix return code of xfs_break_leased_layouts() (2019-08-19 18:15:28 -0700)
----------------------------------------------------------------
Changes since last update:
- Fix missing compat ioctl handling for get/setlabel
- Fix missing ioctl pointer sanitization on s390
- Fix a page locking deadlock in the dedupe comparison code
- Fix inadequate locking in reflink code w.r.t. concurrent directio
- Fix broken error detection when breaking layouts
----------------------------------------------------------------
Christoph Hellwig (2):
xfs: fall back to native ioctls for unhandled compat ones
xfs: compat_ioctl: use compat_ptr()
Darrick J. Wong (2):
vfs: fix page locking deadlocks when deduping files
xfs: fix reflink source file racing with directio writes
Ira Weiny (1):
fs/xfs: Fix return code of xfs_break_leased_layouts()
fs/read_write.c | 49 +++++++++++++++++++++++++++++++++-------
fs/xfs/xfs_ioctl32.c | 56 +++-------------------------------------------
fs/xfs/xfs_pnfs.c | 2 +-
fs/xfs/xfs_reflink.c | 63 ++++++++++++++++++++++++++++++----------------------
4 files changed, 82 insertions(+), 88 deletions(-)
next reply other threads:[~2019-08-23 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 16:34 Darrick J. Wong [this message]
2019-08-23 18:00 ` [GIT PULL] xfs: fixes for 5.3-rc6 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=20190823163439.GL1037350@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.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).