Linux Ext4 Filesystem

• Thread Index

• Re: [PATCH v2] xfstests, generic: add project quota attribute tests
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] ext4: verify extent header depth
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2] xfstests, generic: add project quota attribute tests
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] ext4: verify extent header depth
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ext4: verify extent header depth
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• [PATCH] ext4: verify extent header depth
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [PATCH v23 13/22] vfs: Cache richacl in struct inode
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 12/22] vfs: Add get_richacl and set_richacl inode operations
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v2] xfstests, generic: add project quota attribute tests
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: ext4 crash in 4.4.10
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: fix reference counting bug on block allocation error
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• [PATCH] ext4: Cleanup ext4_sync_parent()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH -v3] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC] weirdness in ext4_sync_file()
  • From: Jan Kara <jack@xxxxxxx>
• Re: ext4 crash in 4.4.10
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: ext4 crash in 4.4.10
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] quota: fix coredump if projid file dose not exist
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH v2] xfstests, generic: add project quota attribute tests
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH RESEND] e2fsck: update j_tail_sequence after recovery
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH e2fsprogs] fuse2fs: needs SYSLIBS
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Fix filesystem deadlock while reading corrupted xattr block
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] Ext4: fix project quota accounting without quota limits enabled.
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH RESEND] e2fsck: update j_tail_sequence after recovery
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• [PATCH] ext4: validate s_reserved_gdt_blocks on mount
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: mbcache: fix to detect failure of register_shrinker
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• RE: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl
  • From: "Frank Filz" <ffilzlnx@xxxxxxxxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v23 11/22] vfs: Cache base_acl objects in inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 10/22] posix_acl: Improve xattr fixup code
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH v23 09/22] richacl: Permission check algorithm
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH] xfstests, ext4: add project quota attribute tests
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] xfstests, ext4: add project quota attribute tests
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH v23 07/22] richacl: Permission mapping functions
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 06/22] richacl: In-memory representation and helper functions
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 05/22] vfs: Add permission flags for setting file attributes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 04/22] vfs: Make the inode passed to inode_change_ok non-const
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v23 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH] xfstests, ext4: add project quota attribute tests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] quota: fix coredump if projid file dose not exist
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH] Ext4: fix project quota accounting without quota limits enabled.
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH] xfstests, ext4: add project quota attribute tests
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [4.7-rc4] WARNING: CPU: 10 PID: 3359 at fs/inode.c:280 drop_nlink+0x3e/0x50
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/1]ext4: Fix WARN_ON_ONCE when marking buffer dirty
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [4.7-rc4] WARNING: CPU: 10 PID: 3359 at fs/inode.c:280 drop_nlink+0x3e/0x50
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: 4.7-rc6, ext4, sparc64: Unable to handle kernel paging request at ...
  • From: Meelis Roos <mroos@xxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: don't call ext4_should_journal_data() on the journal inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/1]ext4: Fix WARN_ON_ONCE when marking buffer dirty
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH -v2] quota: fix generic/244 on 32-bit platforms
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: 4.7-rc6, ext4, sparc64: Unable to handle kernel paging request at ...
  • From: Anatoly Pugachev <matorola@xxxxxxxxx>
• 4.7-rc6, ext4, sparc64: Unable to handle kernel paging request at ...
  • From: Meelis Roos <mroos@xxxxxxxx>
• [Bug 121371] fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: ext4 crash in 4.4.10
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: [PATCH] ext4: don't call ext4_should_journal_data() on the journal inode
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/1]ext4: Fix WARN_ON_ONCE when marking buffer dirty
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: [PATCH] quota: fix generic/244 on 32-bit platforms
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH RESEND] ext4: correct error value of function verifying dx checksum
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH RESEND] ext4: correct error value of function verifying dx checksum
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• [PATCH] quota: fix generic/244 on 32-bit platforms
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: avoid modifying checksum fields directly during checksum verification
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [Bug 121371] fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 121371] fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 121371] fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 121371] fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 121371] New: fsck created undeletable directory
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] ext4: don't call ext4_should_journal_data() on the journal inode
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [PATCH] ext4: don't call ext4_should_journal_data() on the journal inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH] ext4: don't call ext4_should_journal_data() on the journal inode
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [RFC PATCH] ext4: validate number of meta clusters in group
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Refreshed rootfs.img for kvm-xfstests
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: ext4: what are possible causes of "zero length extent" ?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• RE: ext4: what are possible causes of "zero length extent" ?
  • From: "Craske, Mark" <Mark_Craske@xxxxxxxxxx>
• [RFC PATCH] ext4: validate number of meta clusters in group
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4: check for extents that wrap around
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] jbd2: make journal y2038 safe
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 4/4] jbd2: Track more dependencies on transaction commit
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 3/4] jbd2: Move lockdep tracking to journal_s
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 2/4] jbd2: Move lockdep instrumentation for jbd2 handles
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Refreshed rootfs.img for kvm-xfstests
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH -v3] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v23 00/22] Richacls (Core and Ext4)
  • From: Volker Lendecke <Volker.Lendecke@xxxxxxxxx>
• [PATCH v23 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 10/22] posix_acl: Improve xattr fixup code
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 04/22] vfs: Make the inode passed to inode_change_ok non-const
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 08/22] richacl: Compute maximum file masks from an acl
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 09/22] richacl: Permission check algorithm
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 12/22] vfs: Add get_richacl and set_richacl inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 11/22] vfs: Cache base_acl objects in inodes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 06/22] richacl: In-memory representation and helper functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 07/22] richacl: Permission mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 18/22] richacl: xattr mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 13/22] vfs: Cache richacl in struct inode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 16/22] richacl: Create-time inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 15/22] richacl: Check if an acl is equivalent to a file mode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 14/22] richacl: Update the file masks in chmod()
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 19/22] richacl: Add richacl xattr handler
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 21/22] ext4: Add richacl support
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 17/22] richacl: Automatic Inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 20/22] vfs: Add richacl permission checking
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 00/22] Richacls (Core and Ext4)
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 05/22] vfs: Add permission flags for setting file attributes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v23 22/22] ext4: Add richacl feature flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Corrupted inode timestamps on v4.4+?
  • From: Tomáš Trnka <ttrnka@xxxxxxxxxxxx>
• [PATCH 0/1]ext4: Fix for WARN_ON_ONCE when marking buffer dirty
  • From: "Pranay Kr. Srivastava" <pranjas@xxxxxxxxx>
• [PATCH 1/1]ext4: Fix WARN_ON_ONCE when marking buffer dirty
  • From: "Pranay Kr. Srivastava" <pranjas@xxxxxxxxx>
• Re: WARNING at fs/ext4/inode.c ext4_evict_inode() triggers on 4.0
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: check for extents that wrap around
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [Y2038] [PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: Omar Sandoval <osandov@xxxxxxxxxxx>
• Re: [PATCH] Fix filesystem deadlock while reading corrupted xattr block
  • From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
• [PATCH] Fix filesystem deadlock while reading corrupted xattr block
  • From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
• [PATCH v3 07/24] fs: ext4: Use current_time() for inode timestamps
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• [PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• [RFC] weirdness in ext4_sync_file()
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH v2] ext4: always pre-allocate max depth for path
  • From: "Faccini, Bruno" <bruno.faccini@xxxxxxxxx>
• Re: [PATCH] ext4: always pre-allocate max depth for path
  • From: "Faccini, Bruno" <bruno.faccini@xxxxxxxxx>
• [PATCH e2fsprogs] fuse2fs: needs SYSLIBS
  • From: Gustavo Zacarias <gustavo@xxxxxxxxxxxxxxx>
• Re: [Y2038] [PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: FW: ext4 out of order when use cfq scheduler
  • From: Jan Kara <jack@xxxxxxx>
• FW: ext4 out of order when use cfq scheduler
  • From: "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@xxxxxxxxxxxx>
• RE: [PATCH] jbd2: wake up j_wait_done_commit before commit callback
  • From: Wang Shilong <wshilong@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• Re: [PATCH] e2undo: fix endian issues
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [Y2038] [PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [patch] ext4: underflow in alignment check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: [patch] ext4: underflow in alignment check
  • From: Jan Kara <jack@xxxxxxx>
• Re: [patch] ext4: underflow in alignment check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [patch] ext4: underflow in alignment check
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] jbd2: wake up j_wait_done_commit before commit callback
  • From: Jan Kara <jack@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: Reported regressions for 4.7 as of Sunday, 2016-06-19
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH] jbd2: make journal y2038 safe
  • From: Jan Kara <jack@xxxxxxx>
• Re: WARNING at fs/ext4/inode.c ext4_evict_inode() triggers on 4.0
  • From: Jan Kara <jack@xxxxxxx>
• Re: PROBLEM: [SOLVED] incorrect data block bitmap after running resize2fs and e2fsck
  • From: Lars Wijtemans <lars@xxxxxxxxxxxx>
• Re: WARNING at fs/ext4/inode.c ext4_evict_inode() triggers on 4.0
  • From: Calvin Owens <calvinowens@xxxxxx>
• [PATCH] jbd2: make journal y2038 safe
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: PROBLEM: incorrect data block bitmap after running resize2fs and e2fsck
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• PROBLEM: incorrect data block bitmap after running resize2fs and e2fsck
  • From: Lars Wijtemans <lars@xxxxxxxxxxxx>
• Re: [PATCH -v2] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] jbd2: wake up j_wait_done_commit before commit callback
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH] e2undo: fix endian issues
  • From: Marcus Hüwe <suse-tux@xxxxxx>
• Re: [PATCH] e2undo: fix endian issues
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH] e2undo: fix endian issues
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [PATCH -v2] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH -v2] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4: always pre-allocate max depth for path
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH] ext4: always pre-allocate max depth for path
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH] ext4: always pre-allocate max depth for path
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH] ext4: always pre-allocate max depth for path
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH -v2] ext4: respect the nobarrier mount option in nojournal mode
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: always pre-allocate max depth for path
  • From: "Faccini, Bruno" <bruno.faccini@xxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 3/4] jbd2: Move lockdep tracking to journal_s
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH 4/4] jbd2: Track more dependencies on transaction commit
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 1/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 3/4] jbd2: Move lockdep tracking to journal_s
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 2/4] jbd2: Move lockdep instrumentation for jbd2 handles
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/4] ext4: Fix deadlock during page writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: WARNING at fs/ext4/inode.c ext4_evict_inode() triggers on 4.0
  • From: Jan Kara <jack@xxxxxxx>
• [patch] ext4: underflow in alignment check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] jbd2: wake up j_wait_done_commit before commit callback
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH] ext4: avoid modifying checksum fields directly during checksum verification
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: [PATCH] ext4: avoid modifying checksum fields directly during checksum verification
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• WARNING at fs/ext4/inode.c ext4_evict_inode() triggers on 4.0
  • From: Calvin Owens <calvinowens@xxxxxx>
• [RFC PATCH] coredump: avoid ext4 auto_da_alloc for core file
  • From: Omar Sandoval <osandov@xxxxxxxxxxx>
• [PATCH] ext4: avoid modifying checksum fields directly during checksum verification
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH -v2] ext4: respect the nobarrier mount option in nojournal mode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• K3.18-lts : ext4/namei.c: hash used un-initialized
  • From: pavi1729 <pavitra1729@xxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• Re: [PATCH e2fsprogs] fuse2fs: might need librt
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Bob Copeland <me@xxxxxxxxxxxxxxx>
• [PATCH e2fsprogs] fuse2fs: might need librt
  • From: Gustavo Zacarias <gustavo@xxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] dax: Take shared lock in dax_do_io()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Jan Kara <jack@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• [PATCH 01/21] fs: Replace CURRENT_TIME_SEC with current_fs_time()
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Release of e2fsprogs 1.43.1
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 0/2] linux-block for-next REQ_OP fixes
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] ext4: use bio op helprs in ext4 crypto code
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 1/2] ext4: use bio op helprs in ext4 crypto code
  • From: mchristi@xxxxxxxxxx
• [PATCH 0/2] linux-block for-next REQ_OP fixes
  • From: mchristi@xxxxxxxxxx
• [PATCH 2/2] mg_disk: fix enum REQ_OP_ kbuild error
  • From: mchristi@xxxxxxxxxx
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Holger Hoffstätte <holger@xxxxxxxxxxxxxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path
  • From: Lin Feng <linf@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] ext4: respect the nobarrier mount option in nojournal mode
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [PATCH -v2] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH] ext4: respect the nobarrier mount option in nojournal mode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH -v2] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH] ext4: optimize ext4_should_retry_alloc() to improve ENOSPC performance
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH] ext4: mballoc.h typo fix: correct wrong comments about MB_DEFAULT_STREAM_THRESHOLD
  • From: Lin Feng <linf@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 28/45] target: use bio op accessors
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 28/45] target: use bio op accessors
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 41/45] block, drivers, fs: shrink bi_rw from long to int
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 40/45] block: move bio io prio to a new field
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 28/45] target: use bio op accessors
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 25/45] bcache: use bio op accessors
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 24/45] dm: use bio op accessors
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 09/45] block discard: use bio set op accessor
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 08/45] block, fs, mm, drivers: use bio set/get op accessors
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 07/45] bcache: use op_is_write instead of checking for REQ_WRITE
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 06/45] dm: use op_is_write instead of checking for REQ_WRITE
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 05/45] block, drivers, cgroup: use op_is_write helper instead of checking for REQ_WRITE
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 02/45] block: add REQ_OP definitions and helpers
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 01/45] block/fs/drivers: remove rw argument from submit_bio
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path
  • From: Lin Feng <linf@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 01/45] block/fs/drivers: remove rw argument from submit_bio
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 01/45] block/fs/drivers: remove rw argument from submit_bio
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 01/45] block/fs/drivers: remove rw argument from submit_bio
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH 09/45] block discard: use bio set op accessor
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/45] block, fs, mm, drivers: use bio set/get op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 00/45] v8: separate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/45] direct-io: use bio set/get op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/45] btrfs: have submit_one_bio users use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 12/45] btrfs: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 13/45] btrfs: update __btrfs_map_block for REQ_OP transition
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/45] f2fs: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/45] gfs2: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/45] hfsplus: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/45] mpage: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/45] block/fs/drivers: remove rw argument from submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/45] block: add REQ_OP definitions and helpers
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/45] pm: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/45] fs: have submit_bh users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/45] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/45] dm: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/45] bcache: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/45] block, drivers, cgroup: use op_is_write helper instead of checking for REQ_WRITE
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/45] drbd: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/45] dm: use op_is_write instead of checking for REQ_WRITE
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/45] bcache: use op_is_write instead of checking for REQ_WRITE
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/45] md: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/45] btrfs: use bio fields for op and flags
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/45] xen: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/45] xfs: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/45] block: copy bio op to request op
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/45] block: prepare request creation/destruction code to use REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/45] ocfs2: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/45] dm: pass dm stats data dir instead of bi_rw
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/45] block: prepare mq request creation to use REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/45] target: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/45] block: prepare elevator to use REQ_OPs.
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/45] blkg_rwstat: separate op from flags
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/45] block: convert merge/insert code to check for REQ_OPs.
  • From: mchristi@xxxxxxxxxx
• [PATCH 37/45] drivers: use req op accessor
  • From: mchristi@xxxxxxxxxx
• [PATCH 36/45] block: convert is_sync helpers to use REQ_OPs.
  • From: mchristi@xxxxxxxxxx
• [PATCH 38/45] blktrace: use op accessors
  • From: mchristi@xxxxxxxxxx
• [PATCH 39/45] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 40/45] block: move bio io prio to a new field
  • From: mchristi@xxxxxxxxxx
• [PATCH 41/45] block, drivers, fs: shrink bi_rw from long to int
  • From: mchristi@xxxxxxxxxx
• [PATCH 44/45] block: do not use REQ_FLUSH for tracking flush support
  • From: mchristi@xxxxxxxxxx
• [PATCH 45/45] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• [PATCH 43/45] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: mchristi@xxxxxxxxxx
• [PATCH 20/45] nilfs: use bio op accessors
  • From: mchristi@xxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH 1/3] dax: Take shared lock in dax_do_io()
  • From: Waiman Long <Waiman.Long@xxxxxxx>
• [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io
  • From: Waiman Long <Waiman.Long@xxxxxxx>
• [PATCH 2/3] ext4: Make cache hits/misses per-cpu counts
  • From: Waiman Long <Waiman.Long@xxxxxxx>
• [PATCH 0/3] dax, ext4: Improve DAX performance in ext4
  • From: Waiman Long <Waiman.Long@xxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: ext4 crash in 4.4.10
  • From: Jan Kara <jack@xxxxxxx>
• ext4 crash in 4.4.10
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Nikola Pajkovsky <nikola.pajkovsky@xxxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path
  • From: Lin Feng <linf@xxxxxxxxxxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Jan Kara <jack@xxxxxxx>
• [Bug 119491] New: UBSAN: Undefined behaviour in /home/vitti/1tb/vitti/rpmbuild/SOURCES/linux-4.5/fs/ext4/mballoc.c:1274
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 119481] New: UBSAN: Undefined behaviour in /home/vitti/1tb/vitti/rpmbuild/SOURCES/linux-4.5/fs/ext4/mballoc.c:2612
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
• Re: [PATCH] e2fsck: update j_tail_sequence after recovery
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• odd ext3/4 quota protection fault when running xfstests for xfs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• [PATCH v22 00/22] Richacls (Core and Ext4)
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 04/22] vfs: Make the inode passed to inode_change_ok non-const
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 05/22] vfs: Add permission flags for setting file attributes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 06/22] richacl: In-memory representation and helper functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 07/22] richacl: Permission mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 09/22] richacl: Permission check algorithm
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 12/22] vfs: Add get_richacl and set_richacl inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 10/22] posix_acl: Improve xattr fixup code
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 17/22] richacl: Automatic Inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 13/22] vfs: Cache richacl in struct inode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 14/22] richacl: Update the file masks in chmod()
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 16/22] richacl: Create-time inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 15/22] richacl: Check if an acl is equivalent to a file mode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 18/22] richacl: xattr mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 20/22] vfs: Add richacl permission checking
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 21/22] ext4: Add richacl support
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 22/22] ext4: Add richacl feature flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 19/22] richacl: Add richacl xattr handler
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 11/22] vfs: Cache base_acl objects in inodes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v22 08/22] richacl: Compute maximum file masks from an acl
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Jun He <jhe@xxxxxxxxxxx>
• [PATCH] EXT4: Avoid zeroout-ing and writting the same space
  • From: Jun He <jhe@xxxxxxxxxxx>
• [PATCH] Allow extents equal to max_zeroout to be zero-ed
  • From: Jun He <jhe@xxxxxxxxxxx>
• [Bug 118511] Corruption of VM qcow2 image file on EXT4 with crypto enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
• [PATCH 2/2] tests: fix f_pre_1970_date_encoding on systems with a 32-bit time_t
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH 1/2] e2fsck: always fix invalid extra field in timestamps if time_t is 32-bits
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: e2fsprogs-1.43 make check failures
  • From: Bruce Dubbs <bruce.dubbs@xxxxxxxxx>
• Re: [PATCH e2fsprogs] Apply LDFLAGS when building tests in lib/e2p
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: e2fsprogs-1.43 make check failures
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• e2fsprogs-1.43 make check failures
  • From: Bruce Dubbs <bruce.dubbs@xxxxxxxxx>
• Re: [PATCH e2fsprogs] Apply LDFLAGS when building tests in lib/e2p
  • From: Filipe Brandenburger <filbranden@xxxxxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2] generic/250: ignore xfs_io IO errors when writing to dmerror device
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH v2] generic/250: ignore xfs_io IO errors when writing to dmerror device
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [Bug 118511] Corruption of VM qcow2 image file on EXT4 with crypto enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] generic/250: ignore xfs_io IO errors when writing to dmerror device
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• Re: [PATCH v3] direct-io: fix direct write stale data exposure from concurrent buffered read
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH v3] direct-io: fix direct write stale data exposure from concurrent buffered read
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] generic/250: ignore xfs_io IO errors when writing to dmerror device
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• unexpected sync delays in dpkg for small pre-allocated files on ext4
  • From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
• Re: [PATCH v3] direct-io: fix direct write stale data exposure from concurrent buffered read
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• [GIT PULL] ext4 updates for 4.7
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [Bug 118511] Corruption of VM qcow2 image file on EXT4 with crypto enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH] generic/250: ignore xfs_io IO errors when writing to dmerror device
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• RE: ext4: what are possible causes of "zero length extent" ?
  • From: "Craske, Mark" <Mark_Craske@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] mke2fs: fix project quota creation
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 2/2] e2fsck: fix project quota support
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH 1/2] mke2fs: fix project quota creation
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 1/2] mke2fs: fix project quota creation
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH 2/2] e2fsck: fix project quota support
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: correct error value of function verifying dx checksum
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ext4: correct error value of function verifying dx checksum
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH] ext4: correct error value of function verifying dx checksum
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH] ext4: correct error value of function verifying dx checksum
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• [Bug 118511] New: Corruption of VM qcow2 image file on EXT4 with crypto enabled
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 5/7] dax: New fault locking
  • From: Jan Kara <jack@xxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [Bug 118401] New: Lenovo A740 gave up waiting for root device with kernels >= 4.3
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dax-misc branch for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Difference in jbd2 behavior between CentOS and Ubuntu while unmounting
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• [Bug 118041] My tricky script involving zram and device mapper hangs on "mount"
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• dax-misc branch for linux-next
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• [Bug 118041] My tricky script involving zram and device mapper hangs on "mount"
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118041] My tricky script involving zram and device mapper hangs on "mount"
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 118041] My tricky script involving zram and device mapper hangs on "mount"
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers
  • From: David Sterba <dsterba@xxxxxxx>
• [PATCH] fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: ext4: call out CRC and corruption errors with specific error codes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• re: ext4: call out CRC and corruption errors with specific error codes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] ext4: remove unused variable offset
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: Shuichi Ihara <sihara@xxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: add lazyinit stats support
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• [PATCH] ext4: add lazyinit stats support
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] mbcache: fix to detect failure of register_shrinker
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] mbcache: fix to detect failure of register_shrinker
  • From: Chao Yu <chao@xxxxxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3] direct-io: fix direct write stale data exposure from concurrent buffered read
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• [PATCH v3] direct-io: fix direct write stale data exposure from concurrent buffered read
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC][PATCH 0/6] Enhanced file stat system call
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC][PATCH 0/6] Enhanced file stat system call
  • From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 0/4] ext4: DAX fixes
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 5/7] dax: New fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/7] dax: Fix condition for filling of PMD holes
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/7] dax: Make huge page handling depend of CONFIG_BROKEN
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 4/6] dax: export a low-level __dax_zero_page_range helper
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• [PATCH 3/7] dax: Define DAX lock bit for radix tree exceptional entry
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 1/7] dax: Fix condition for filling of PMD holes
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 4/7] dax: Allow DAX code to replace exceptional entries
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 7/7] dax: Remove i_mmap_lock protection
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/7 v4] DAX page fault locking
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 6/7] dax: Use radix tree entry lock to protect cow faults
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 5/7] dax: New fault locking
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 2/7] dax: Make huge page handling depend of CONFIG_BROKEN
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 2/2] mke2fs: fix filesystem size calculation, if an offset is specified
  • From: Marcus Huewe <suse-tux@xxxxxx>
• [PATCH 1/2] tests: test "mke2fs -E offset=N" filesystem size calculation
  • From: Marcus Huewe <suse-tux@xxxxxx>
• [PATCH 0/2] mke2fs -E offset=N filessystem size calculation
  • From: Marcus Huewe <suse-tux@xxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v7 4/6] dax: export a low-level __dax_zero_page_range helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 5/6] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 16/18] dax: New fault locking
  • From: Jan Kara <jack@xxxxxxx>
• [Bug 118041] New: My tricky script involving zram and device mapper hangs on "mount"
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH v7 2/6] dax: enable dax in the presence of known media errors (badblocks)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 0/6] dax: handling media errors (clear-on-zero only)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 3/6] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 5/6] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 1/6] dax: fallback from pmd to pte on error
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 4/6] dax: export a low-level __dax_zero_page_range helper
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v7 6/6] dax: fix a comment in dax_zero_page_range and dax_truncate_page
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 16/18] dax: New fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: Remarks regarding sparse_super2 feature
  • From: Damien Guibouret <damien.guibouret@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 2/2] direct-io: fix stale data exposure from concurrent buffered read
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 1/2] direct-io: cleanup get_more_blocks()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] direct-io: fix stale data exposure from concurrent buffered read
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] direct-io: cleanup get_more_blocks()
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• ext4: what are possible causes of "zero length extent" ?
  • From: "Craske, Mark" <Mark_Craske@xxxxxxxxxx>
• [PATCH 2/7] dax: Remove complete_unwritten argument
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/7 v4] DAX cleanups and fixes
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 3/7] ext2: Avoid DAX zeroing to corrupt data
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 4/7] dax: Remove dead zeroing code from fault handlers
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 1/7] DAX: move RADIX_DAX_ definitions to dax.c
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 7/7] dax: Remove redundant inode size checks
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 5/7] dax: Remove zeroing from dax_io()
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 6/7] dax: Remove pointless writeback from dax_do_io()
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 2/4] ext4: Fix race in transient ENOSPC detection
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/4] ext4: DAX fixes
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 1/4] ext4: Handle transient ENOSPC properly for DAX
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 3/4] ext4: Refactor direct IO code
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 4/4] ext4: Pre-zero allocated blocks for DAX IO
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Jan Kara <jack@xxxxxxx>
• Re: Remarks regarding sparse_super2 feature
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [Bug 117421] e2fsprogs: mke2fs ignores sparse_super2 when also using extent or 64bit
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 117421] e2fsprogs: mke2fs ignores sparse_super2 when also using extent or 64bit
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v6 0/5] dax: handling media errors (clear-on-zero only)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v6 1/5] dax: fallback from pmd to pte on error
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v6 2/5] dax: enable dax in the presence of known media errors (badblocks)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v6 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v6 5/5] dax: fix a comment in dax_zero_page_range and dax_truncate_page
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/2] direct-io: cleanup get_more_blocks()
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• RE: [PATCH v21 00/22] Richacls
  • From: "Frank Filz" <ffilzlnx@xxxxxxxxxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 5/5] dax: fix a comment in dax_zero_page_range and dax_truncate_page
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 1/5] dax: fallback from pmd to pte on error
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
• Re: [PATCH 16/18] dax: New fault locking
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v21 00/22] Richacls
  • From: Volker Lendecke <Volker.Lendecke@xxxxxxxxx>
• Re: [PATCH v21 00/22] Richacls
  • From: Jeremy Allison <jra@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v21 00/22] Richacls
  • From: Volker Lendecke <Volker.Lendecke@xxxxxxxxx>
• [PATCH v21 00/22] Richacls
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 04/22] vfs: Make the inode passed to inode_change_ok non-const
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 05/22] vfs: Add permission flags for setting file attributes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 06/22] richacl: In-memory representation and helper functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 07/22] richacl: Permission mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 08/22] richacl: Compute maximum file masks from an acl
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 10/22] posix_acl: Improve xattr fixup code
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 09/22] richacl: Permission check algorithm
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 11/22] vfs: Cache base_acl objects in inodes
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 12/22] vfs: Add get_richacl and set_richacl inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 13/22] vfs: Cache richacl in struct inode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 14/22] richacl: Update the file masks in chmod()
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 15/22] richacl: Check if an acl is equivalent to a file mode
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 16/22] richacl: Create-time inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 17/22] richacl: Automatic Inheritance
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 18/22] richacl: xattr mapping functions
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 19/22] richacl: Add richacl xattr handler
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 20/22] vfs: Add richacl permission checking
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 21/22] ext4: Add richacl support
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v21 22/22] ext4: Add richacl feature flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v5 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] direct-io: fix stale data exposure from concurrent buffered read
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [RFC][PATCH 0/6] Enhanced file stat system call
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: Jan Kara <jack@xxxxxxx>
• [Bug 117421] e2fsprogs: mke2fs ignores sparse_super2 when also using extent or 64bit
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• RE: EXT4 bad block - ext4_xattr_block_get
  • From: "Lay, Kuan Loon" <kuan.loon.lay@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v5 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "hch@xxxxxxxxxxxxx" <hch@xxxxxxxxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "hch@xxxxxxxxxxxxx" <hch@xxxxxxxxxxxxx>
• Re: [PATCH v5 0/5] dax: handling media errors (clear-on-zero only)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v5 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 5/6] statx: Make windows attributes available for CIFS, NTFS and FAT to use
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 3/6] statx: Ext4: Return enhanced file attributes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v2 2/2] direct-io: fix stale data exposure from concurrent buffered read
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• [PATCH v2 1/2] direct-io: cleanup get_more_blocks()
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH] ext4 crypto: migrate into vfs's crypto engine
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: [PATCH] direct-io: fix stale data exposure from concurrent buffered read
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH] ext4 crypto: migrate into vfs's crypto engine
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH e2fsprogs] Apply LDFLAGS when building tests in lib/e2p
  • From: Filipe Brandenburger <filbranden@xxxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: tytso@xxxxxxx
• [PATCH v5 0/5] dax: handling media errors (clear-on-zero only)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 1/5] dax: fallback from pmd to pte on error
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 2/5] dax: enable dax in the presence of known media errors (badblocks)
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 3/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 5/5] dax: fix a comment in dax_zero_page_range and dax_truncate_page
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH] direct-io: fix stale data exposure from concurrent buffered read
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] direct-io: fix stale data exposure from concurrent buffered read
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
  • From: Daeho Jeong <daeho.jeong@xxxxxxxxxxx>
• Re: [PATCH 16/18] dax: New fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [RFC v3] [PATCH 0/18] DAX page fault locking
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] scop GFP_NOFS api
  • From: NeilBrown <mr@xxxxxxxxxxxxxxx>
• Re: [RESEND Patch] jbd2: remove excess descriptions for handle_s
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: remove unnecessary bio get/put
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC][PATCH 0/6] Enhanced file stat system call
  • From: Steve French <smfrench@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [Bug 114701] ubsan: "shift exponent -1 is negative" in fs/ext4/mballoc.c:2612:15
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 112161] UBSAN: Undefined behaviour in fs/ext4/mballoc.c:1274:11
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/1] Fix Ubsan error
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4 crypto: migrate into vfs's crypto engine
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v2 2/2] fs/ext4: ext4_mb_init(): silence UBSAN
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2 1/2] fs/ext4: mb_find_order_for_block(): silence UBSAN
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 3/3] xfs_io: support the new getfsmap ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 2/3] xfs: introduce the XFS_IOC_GETFSMAPX ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 1/3] document the XFS_IOC_GETFSMAPX ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [RFC 0/3] getfsmapx ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available
  • From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>