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, agruenba@redhat.com,
rpeterso@redhat.com, cluster-devel@redhat.com,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] iomap: fixes for 5.5
Date: Fri, 6 Dec 2019 11:54:56 -0800 [thread overview]
Message-ID: <20191206195456.GB9464@magnolia> (raw)
Hi Linus,
Please pull these iomap bug fixes for 5.5-rc1, which fix a race
condition and a use-after-free error.
The branch has survived overnight xfstests runs and merges cleanly with
this morning's master. Please let me know if anything strange happens.
--D
The following changes since commit 88cfd30e188fcf6fd8304586c936a6f22fb665e5:
iomap: remove unneeded variable in iomap_dio_rw() (2019-11-26 09:28:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.5-merge-14
for you to fetch changes up to c275779ff2dd51c96eaae04fac5d766421d6c596:
iomap: stop using ioend after it's been freed in iomap_finish_ioend() (2019-12-05 07:41:16 -0800)
----------------------------------------------------------------
Fixes for 5.5-rc1:
- Fix a UAF when reporting writeback errors
- Fix a race condition when handling page uptodate on a blocksize <
pagesize file that is also fragmented
----------------------------------------------------------------
Christoph Hellwig (1):
iomap: fix sub-page uptodate handling
Zorro Lang (1):
iomap: stop using ioend after it's been freed in iomap_finish_ioend()
fs/iomap/buffered-io.c | 40 ++++++++++++++++++++++++++++------------
1 file changed, 28 insertions(+), 12 deletions(-)
next reply other threads:[~2019-12-06 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 19:54 Darrick J. Wong [this message]
2019-12-08 1:10 ` [GIT PULL] iomap: fixes for 5.5 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=20191206195456.GB9464@magnolia \
--to=djwong@kernel.org \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).