Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 8 Apr 2020 08:58:13 -0700
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
Message-ID: <20200408155813.GB6741@magnolia>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

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(+)