messages from 2025-04-29 14:48:41 to 2025-05-06 09:05:57 UTC [more...]
[PATCH v12 00/17] large atomic writes for xfs
2025-05-06 9:04 UTC (15+ messages)
` [PATCH v12 01/17] fs: add atomic write unit max opt to statx
` [PATCH v12 02/17] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v12 03/17] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v12 04/17] xfs: separate out setting buftarg atomic writes limits
` [PATCH v12 05/17] xfs: add helpers to compute log item overhead
` [PATCH v12 06/17] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v12 07/17] xfs: ignore HW which cannot atomic write a single block
` [PATCH v12 08/17] xfs: allow block allocator to take an alignment hint
` [PATCH v12 09/17] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v12 10/17] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v12 11/17] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v12 12/17] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v12 13/17] xfs: commit CoW-based atomic writes atomically
` [PATCH v12 17/17] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
[PATCH v3 0/2] common: Move exit related functions to common/exit
2025-05-06 8:49 UTC (10+ messages)
` [PATCH v3 1/2] common: Move exit related functions to a common/exit
` [PATCH v3 2/2] check: Replace exit with _fatal and _exit in check
[RFC PATCH v4 00/11] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag
2025-05-06 7:51 UTC (21+ messages)
` [RFC PATCH v4 01/11] block: introduce BLK_FEAT_WRITE_ZEROES_UNMAP to queue limits features
` [RFC PATCH v4 02/11] nvme: set BLK_FEAT_WRITE_ZEROES_UNMAP if device supports DEAC bit
` [RFC PATCH v4 03/11] nvme-multipath: add BLK_FEAT_WRITE_ZEROES_UNMAP support
` [RFC PATCH v4 04/11] nvmet: set WZDS and DRB if device supports BLK_FEAT_WRITE_ZEROES_UNMAP
` [RFC PATCH v4 07/11] fs: statx add write zeroes unmap attribute
` [RFC PATCH v4 08/11] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate
[PATCH v2 1/4] ext4: fix out of bounds punch offset
2025-05-06 7:42 UTC (8+ messages)
` [PATCH v2 2/4] ext4: fix incorrect punch max_end
` [PATCH v2 3/4] ext4: factor out ext4_get_maxbytes()
` [PATCH v2 4/4] ext4: ensure i_size is smaller than maxbytes
[PATCH v11 00/16] large atomic writes for xfs
2025-05-06 6:57 UTC (35+ messages)
` [PATCH v11 01/16] fs: add atomic write unit max opt to statx
` [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v11 03/16] xfs: add helpers to compute log item overhead
` [PATCH v11 04/16] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v11 05/16] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
` [PATCH v11 07/16] xfs: allow block allocator to take an alignment hint
` [PATCH v11 08/16] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v11 09/16] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v11 10/16] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v11 11/16] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v11 12/16] xfs: commit CoW-based atomic writes atomically
` [PATCH v11 13/16] xfs: add xfs_file_dio_write_atomic()
` [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
` [PATCH v11 15/16] xfs: update atomic write limits
` [PATCH v11 16/16] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
kernel BUG in zero_user_segments
2025-05-06 2:25 UTC (5+ messages)
[syzbot] [ext4?] kernel BUG in ext4_mb_normalize_request
2025-05-05 23:53 UTC
[PATCH AUTOSEL 5.4 18/79] ext4: reorder capability check last
2025-05-05 23:20 UTC
[PATCH AUTOSEL 5.10 024/114] ext4: reorder capability check last
2025-05-05 23:16 UTC
[PATCH AUTOSEL 5.15 033/153] ext4: reorder capability check last
2025-05-05 23:11 UTC
[PATCH AUTOSEL 6.1 046/212] ext4: reorder capability check last
2025-05-05 23:03 UTC (2+ messages)
` [PATCH AUTOSEL 6.1 063/212] ext4: reject the 'data_err=abort' option in nojournal mode
[PATCH AUTOSEL 6.6 035/294] ext4: on a remount, only log the ro or r/w state when it has changed
2025-05-05 22:55 UTC (7+ messages)
` [PATCH AUTOSEL 6.6 056/294] ext4: reorder capability check last
` [PATCH AUTOSEL 6.6 062/294] jbd2: do not try to recover wiped journal
` [PATCH AUTOSEL 6.6 079/294] ext4: reject the 'data_err=abort' option in nojournal mode
` [PATCH AUTOSEL 6.6 080/294] ext4: do not convert the unwritten extents if data writeback fails
` [PATCH AUTOSEL 6.6 246/294] ext4: don't write back data before punch hole in nojournal mode
` [PATCH AUTOSEL 6.6 247/294] ext4: remove writable userspace mappings before truncating page cache
[PATCH AUTOSEL 6.12 053/486] ext4: on a remount, only log the ro or r/w state when it has changed
2025-05-05 22:38 UTC (7+ messages)
` [PATCH AUTOSEL 6.12 094/486] ext4: reorder capability check last
` [PATCH AUTOSEL 6.12 102/486] jbd2: do not try to recover wiped journal
` [PATCH AUTOSEL 6.12 126/486] ext4: reject the 'data_err=abort' option in nojournal mode
` [PATCH AUTOSEL 6.12 127/486] ext4: do not convert the unwritten extents if data writeback fails
` [PATCH AUTOSEL 6.12 403/486] ext4: don't write back data before punch hole in nojournal mode
` [PATCH AUTOSEL 6.12 404/486] ext4: remove writable userspace mappings before truncating page cache
[PATCH AUTOSEL 6.14 065/642] ext4: on a remount, only log the ro or r/w state when it has changed
2025-05-05 22:12 UTC (8+ messages)
` [PATCH AUTOSEL 6.14 120/642] ext4: reorder capability check last
` [PATCH AUTOSEL 6.14 129/642] jbd2: do not try to recover wiped journal
` [PATCH AUTOSEL 6.14 159/642] ext4: reject the 'data_err=abort' option in nojournal mode
` [PATCH AUTOSEL 6.14 160/642] ext4: do not convert the unwritten extents if data writeback fails
` [PATCH AUTOSEL 6.14 455/642] jbd2: Avoid long replay times due to high number or revoke blocks
` [PATCH AUTOSEL 6.14 520/642] ext4: don't write back data before punch hole in nojournal mode
` [PATCH AUTOSEL 6.14 521/642] ext4: remove writable userspace mappings before truncating page cache
[PATCH -e2fsprogs] mke2fs: don't set the raid stripe for non-rotational devices by default
2025-05-05 17:27 UTC
[RFC PATCH] ext4: Error handling for ext4_get_inode_loc()
2025-05-05 14:00 UTC
[PATCH] ext4/002: make generic to support xfs
2025-05-05 9:20 UTC (3+ messages)
[PATCH] ext4: use writeback_iter in ext4_journalled_submit_inode_data_buffers
2025-05-05 9:16 UTC
[PATCH v10 00/15] large atomic writes for xfs
2025-05-05 5:22 UTC (24+ messages)
` [PATCH v10 01/15] fs: add atomic write unit max opt to statx
` [PATCH v10.1 1.1/15] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH v10 02/15] xfs: add helpers to compute log item overhead
` [PATCH v10 03/15] xfs: add helpers to compute transaction reservation for finishing intent items
` [PATCH v10 04/15] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
` [PATCH v10 05/15] xfs: ignore HW which cannot atomic write a single block
` [PATCH v10.1 "
` [PATCH v10 06/15] xfs: allow block allocator to take an alignment hint
` [PATCH v10 07/15] xfs: refactor xfs_reflink_end_cow_extent()
` [PATCH v10 08/15] xfs: refine atomic write size check in xfs_file_write_iter()
` [PATCH v10 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
` [PATCH v10 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
` [PATCH v10 11/15] xfs: commit CoW-based atomic writes atomically
` [PATCH v10 12/15] xfs: add xfs_file_dio_write_atomic()
` [PATCH v10 13/15] xfs: add xfs_calc_atomic_write_unit_max()
` [PATCH v10 14/15] xfs: update atomic write limits
` [PATCH v10 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
` [PATCH 16/15] xfs: only call xfs_setsize_buftarg once per buffer target
` [PATCH 17/15] xfs: move buftarg atomic write geometry config to setsize_buftarg
[PATCH] ext4: added missing kfree
2025-05-04 0:48 UTC (5+ messages)
[PATCH v3 0/1] xfs: Fail remount with noattr2 on a v5 xfs with v4 enabled kernel
2025-05-02 7:01 UTC (3+ messages)
` [PATCH v3 1/1] xfs: Fail remount with noattr2 on a v5 with v4 enabled
[PATCH v9 00/15] large atomic writes for xfs
2025-05-01 19:53 UTC (17+ messages)
` [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
` [PATCH v9.1 "
` [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
[PATCH v8 0/9] Ext4 Fast Commit Performance Patchset
2025-05-01 13:37 UTC (5+ messages)
[syzbot] [ext4?] possible deadlock in freeze_super (3)
2025-04-30 22:14 UTC
ext4 filesystem corruption (resize2fs bug)
2025-04-30 18:24 UTC (3+ messages)
[PATCH v2 0/2] common: Move exit related functions to common/exit
2025-04-30 12:13 UTC (7+ messages)
` [PATCH v2 1/2] common: Move exit related functions to a common/exit
` [PATCH v2 2/2] check: Replace exit with _exit in check
[PATCH 1/4] ext4: fix out of bounds punch offset
2025-04-30 10:54 UTC (14+ messages)
` [PATCH 2/4] ext4: fix incorrect punch max_end
` [PATCH 3/4] ext4: factor out ext4_get_maxbytes()
` [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
INFO_ task hung in jbd2_complete_transaction
2025-04-30 10:29 UTC
[RFC v2 0/2] ext4: Add multi-fsblock atomic write support using bigalloc
2025-04-30 5:20 UTC (3+ messages)
` [RFC v2 1/2] ext4: Add multi-fsblock atomic write support with bigalloc
` [RFC v2 2/2] ext4: Add support for EXT4_GET_BLOCKS_QUERY_LEAF_BLOCKS
[PATCH AUTOSEL 6.12 29/37] fs/jbd2: use sleeping version of __find_get_block()
2025-04-29 23:51 UTC (2+ messages)
` [PATCH AUTOSEL 6.12 30/37] fs/ext4: use sleeping version of sb_find_get_block()
[PATCH AUTOSEL 6.14 30/39] fs/jbd2: use sleeping version of __find_get_block()
2025-04-29 23:49 UTC (2+ messages)
` [PATCH AUTOSEL 6.14 31/39] fs/ext4: use sleeping version of sb_find_get_block()
[PATCH] ext4: Fix calculation of credits for extent tree modification
2025-04-29 17:55 UTC
[PATCH 5.4 132/179] ext4: fix OOB read when checking dotdot dir
2025-04-29 16:41 UTC
Question about fsck for ext4
2025-04-29 16:31 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox