From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bug fixes for 5.1
Date: Sun, 24 Mar 2019 15:18:27 -0400 [thread overview]
Message-ID: <20190324191827.GG5675@mit.edu> (raw)
In-Reply-To: <20190324191431.GA29605@mit.edu>
Apologies, I forgot to add the CC's before I hit the send button....
- Ted
On Sun, Mar 24, 2019 at 03:14:31PM -0400, Theodore Ts'o wrote:
> The following changes since commit 0df6f46995a9fc92a6b9e591428e77527dd9609a:
>
> jbd2: jbd2_get_transaction does not need to return a value (2019-03-01 00:36:57 -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 18915b5873f07e5030e6fb108a050fa7c71c59fb:
>
> ext4: prohibit fstrim in norecovery mode (2019-03-23 12:10:29 -0400)
>
> ----------------------------------------------------------------
> Miscellaneous ext4 bug fixes for 5.1.
>
> ----------------------------------------------------------------
> Darrick J. Wong (1):
> ext4: prohibit fstrim in norecovery mode
>
> Jan Kara (1):
> ext4: avoid panic during forced reboot
>
> Jason Yan (1):
> ext4: remove useless ext4_pin_inode()
>
> Jiufei Xue (1):
> ext4: fix NULL pointer dereference while journal is aborted
>
> Lukas Czerner (3):
> ext4: fix data corruption caused by unaligned direct AIO
> ext4: add missing brelse() in add_new_gdb_meta_bg()
> ext4: report real fs size after failed resize
>
> zhangyi (F) (2):
> ext4: brelse all indirect buffer in ext4_ind_remove_space()
> ext4: cleanup bh release code in ext4_ind_remove_space()
>
> fs/ext4/ext4_jbd2.h | 2 +-
> fs/ext4/file.c | 2 +-
> fs/ext4/indirect.c | 43 ++++++++++++++++++++++---------------------
> fs/ext4/inode.c | 30 ------------------------------
> fs/ext4/ioctl.c | 7 +++++++
> fs/ext4/resize.c | 17 ++++++++++++++---
> fs/ext4/super.c | 16 +++++++++++++---
> 7 files changed, 58 insertions(+), 59 deletions(-)
parent reply other threads:[~2019-03-24 19:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190324191431.GA29605@mit.edu>]
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=20190324191827.GG5675@mit.edu \
--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).