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: new code for 5.6
Date: Thu, 30 Jan 2020 20:07:53 -0800 [thread overview]
Message-ID: <20200131040753.GB6869@magnolia> (raw)
Hi Linus,
Please pull this set of new code for 5.6. There's a single patch fixing
an off-by-one error when we're checking to see how far we're gotten into
an EOF page.
--D
The following changes since commit fd6988496e79a6a4bdb514a4655d2920209eb85d:
Linux 5.5-rc4 (2019-12-29 15:29:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.6-merge-3
for you to fetch changes up to 243145bc4336684c69f95de0a303b31f2e5bf264:
fs: Fix page_mkwrite off-by-one errors (2020-01-06 08:58:23 -0800)
----------------------------------------------------------------
New code for 5.6:
- Fix an off-by-one error when checking if offset is within inode size
----------------------------------------------------------------
Andreas Gruenbacher (1):
fs: Fix page_mkwrite off-by-one errors
fs/iomap/buffered-io.c | 18 +++++-------------
include/linux/pagemap.h | 28 ++++++++++++++++++++++++++++
2 files changed, 33 insertions(+), 13 deletions(-)
next reply other threads:[~2020-01-31 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 4:07 Darrick J. Wong [this message]
2020-01-31 21:10 ` [GIT PULL] iomap: new code for 5.6 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=20200131040753.GB6869@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).