All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ext4 bug fixes for 4.21
Date: Sun, 6 Jan 2019 08:39:43 -0500	[thread overview]
Message-ID: <20190106133943.GA10099@mit.edu> (raw)

The following changes since commit 18f2c4fcebf2582f96cbd5f2238f4f354a0e4847:

  ext4: check for shutdown and r/o file system in ext4_write_inode() (2018-12-19 14:36:58 -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 191ce17876c9367819c4b0a25b503c0f6d9054d8:

  ext4: fix special inode number checks in __ext4_iget() (2018-12-31 22:34:31 -0500)

----------------------------------------------------------------
Fix a number of ext4 bugs.

----------------------------------------------------------------
Theodore Ts'o (6):
      ext4: make sure enough credits are reserved for dioread_nolock writes
      ext4: fix a potential fiemap/page fault deadlock w/ inline_data
      ext4: avoid kernel warning when writing the superblock to a dead device
      ext4: use ext4_write_inode() when fsyncing w/o a journal
      ext4: track writeback errors using the generic tracking infrastructure
      ext4: fix special inode number checks in __ext4_iget()

 fs/ext4/fsync.c  | 16 ++++++++++++----
 fs/ext4/inline.c |  6 +++---
 fs/ext4/inode.c  |  5 +++--
 fs/ext4/super.c  |  2 +-
 4 files changed, 19 insertions(+), 10 deletions(-)

             reply	other threads:[~2019-01-06 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 13:39 Theodore Y. Ts'o [this message]
2019-01-06 21:35 ` [GIT PULL] ext4 bug fixes for 4.21 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=20190106133943.GA10099@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.