public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore 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 updates for 5.13
Date: Fri, 30 Apr 2021 12:41:33 -0400	[thread overview]
Message-ID: <YIwzPefeKM+Vuxn5@mit.edu> (raw)

The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:

  Linux 5.12-rc4 (2021-03-21 14:56:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus

for you to fetch changes up to 6c0912739699d8e4b6a87086401bf3ad3c59502d:

  ext4: wipe ext4_dir_entry2 upon file deletion (2021-04-22 16:51:23 -0400)

----------------------------------------------------------------
New features for ext4 this cycle include support for encrypted
casefold, ensure that deleted file names are cleared in directory
blocks by zeroing directory entries when they are unlinked or moved as
part of a hash tree node split.  We also improve the block allocator's
performance on a freshly mounted file system by prefetching block
bitmaps.

There are also the usual cleanups and bug fixes, including fixing a
page cache invalidation race when there is mixed buffered and direct
I/O and the block size is less than page size, and allow the dax flag
to be set and cleared on inline directories.

----------------------------------------------------------------
Alexander Lochmann (2):
      ext4: updated locking documentation for journal_t
      Updated locking documentation for transaction_t

Arnd Bergmann (2):
      jbd2: avoid -Wempty-body warnings
      ext4: fix debug format string warning

Bhaskar Chowdhury (1):
      ext4: fix various seppling typos

Chaitanya Kulkarni (2):
      ext4: use memcpy_from_page() in pagecache_read()
      ext4: use memcpy_to_page() in pagecache_write()

Daniel Rosenberg (2):
      ext4: handle casefolding with encryption
      ext4: optimize match for casefolded encrypted dirs

Eric Whitney (1):
      ext4: delete some unused tracepoint definitions

Fengnan Chang (1):
      ext4: fix error code in ext4_commit_super

Harshad Shirwadkar (7):
      ext4: drop s_mb_bal_lock and convert protected fields to atomic
      ext4: add ability to return parsed options from parse_options
      ext4: add mballoc stats proc file
      ext4: add MB_NUM_ORDERS macro
      ext4: improve cr 0 / cr 1 group scanning
      ext4: add proc files to monitor new structures
      ext4: make prefetch_block_bitmaps default

Jack Qiu (1):
      ext4: fix trailing whitespace

Jan Kara (3):
      ext4: annotate data race in start_this_handle()
      ext4: annotate data race in jbd2_journal_dirty_metadata()
      ext4: Fix occasional generic/418 failure

Leah Rumancik (1):
      ext4: wipe ext4_dir_entry2 upon file deletion

Milan Djurovic (1):
      ext4: remove unnecessary braces in fs/ext4/dir.c

Theodore Ts'o (2):
      ext4: allow the dax flag to be set and cleared on inline directories
      fs: fix reporting supported extra file attributes for statx()

Xu Yihang (1):
      ext4: fix error return code in ext4_fc_perform_commit()

Yang Guo (1):
      ext4: delete redundant uptodate check for buffer

Ye Bin (2):
      ext4: always panic when errors=panic is specified
      ext4: fix ext4_error_err save negative errno into superblock

Zhang Yi (2):
      ext4: fix check to prevent false positive report of incorrect used inodes
      ext4: do not set SB_ACTIVE in ext4_orphan_cleanup()

 Documentation/filesystems/ext4/directory.rst |  27 ++
 fs/ext4/balloc.c                             |   2 +-
 fs/ext4/dir.c                                |  41 ++-
 fs/ext4/ext4.h                               | 107 +++++--
 fs/ext4/fast_commit.c                        |   8 +-
 fs/ext4/file.c                               |  25 +-
 fs/ext4/hash.c                               |  25 +-
 fs/ext4/ialloc.c                             |  51 ++-
 fs/ext4/indirect.c                           |   2 +-
 fs/ext4/inline.c                             |  27 +-
 fs/ext4/inode.c                              |   8 +-
 fs/ext4/ioctl.c                              |   6 +
 fs/ext4/mballoc.c                            | 592 +++++++++++++++++++++++++++++++++--
 fs/ext4/mballoc.h                            |  24 +-
 fs/ext4/migrate.c                            |   6 +-
 fs/ext4/mmp.c                                |   2 +-
 fs/ext4/namei.c                              | 245 +++++++++++----
 fs/ext4/super.c                              | 116 ++++---
 fs/ext4/sysfs.c                              |   8 +
 fs/ext4/verity.c                             |  10 +-
 fs/ext4/xattr.c                              |   2 +-
 fs/jbd2/recovery.c                           |   5 +-
 fs/jbd2/transaction.c                        |  15 +-
 fs/stat.c                                    |   8 +
 include/linux/jbd2.h                         |  33 +-
 include/trace/events/ext4.h                  | 176 -----------
 26 files changed, 1144 insertions(+), 427 deletions(-)

             reply	other threads:[~2021-04-30 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 16:41 Theodore Ts'o [this message]
2021-04-30 22:40 ` [GIT PULL] ext4 updates for 5.13 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=YIwzPefeKM+Vuxn5@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