From: Theodore Ts'o <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 bugfix for 4.5
Date: Wed, 9 Mar 2016 22:18:46 -0500 [thread overview]
Message-ID: <20160310031846.GA19171@thunk.org> (raw)
The following changes since commit 1e9d180ba39f42e8ca4a808baef3a3ef034b1c2c:
ext2, ext4: fix issue with missing journal entry in ext4_dax_mkwrite() (2016-02-27 14:01:16 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable
for you to fetch changes up to 6ffe77bad545f4a7c8edd2a4ee797ccfcd894ab4:
ext4: iterate over buffer heads correctly in move_extent_per_page() (2016-03-09 21:37:53 -0500)
----------------------------------------------------------------
This fixes a regression which crept in v4.5-rc5.
----------------------------------------------------------------
Eryu Guan (1):
ext4: iterate over buffer heads correctly in move_extent_per_page()
fs/ext4/move_extent.c | 1 +
1 file changed, 1 insertion(+)
reply other threads:[~2016-03-10 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160310031846.GA19171@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).