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,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] iomap: bug fix for 5.7
Date: Wed, 8 Apr 2020 08:58:13 -0700 [thread overview]
Message-ID: <20200408155813.GB6741@magnolia> (raw)
Hi Linus,
Please pull this single iomap bug fix for 5.7 to prevent a crash when
memory is tight and readahead is going on. It merged cleanly with
upstream head as of a few minutes ago.
--D
The following changes since commit d9973ce2fe5bcdc5e01bb3f49833d152b8e166ca:
iomap: fix comments in iomap_dio_rw (2020-03-18 08:04:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.7-merge-3
for you to fetch changes up to 457df33e035a2cffc6561992f3f25a6c61605c46:
iomap: Handle memory allocation failure in readahead (2020-04-02 09:08:53 -0700)
----------------------------------------------------------------
Bug fixes for 5.7:
- Fix a problem in readahead where we can crash if we can't allocate a
full bio due to GFP_NORETRY.
----------------------------------------------------------------
Matthew Wilcox (Oracle) (1):
iomap: Handle memory allocation failure in readahead
fs/iomap/buffered-io.c | 8 ++++++++
1 file changed, 8 insertions(+)
next reply other threads:[~2020-04-08 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 15:58 Darrick J. Wong [this message]
2020-04-09 4:55 ` [GIT PULL] iomap: bug fix for 5.7 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=20200408155813.GB6741@magnolia \
--to=djwong@kernel.org \
--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=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).