Linux Ext4 Filesystem
[Prev Page][Next Page]
- Re: [RFC PATCH v2 1/5] jbd2: test case for ext4 data=journal/mmap() journal corruption
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: Fix comment typo "the the".
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: change to use fallthrough macro instead of fallthrough comments
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: remove unused parameter of ext4_generic_delete_entry function
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] mballoc: Replace seq_printf with seq_puts
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: optimize the implementation of ext4_mb_good_group()
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: delete invalid comments near ext4_mb_check_limits()
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: fix typos in ext4_mb_regular_allocator() comment
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: flag as supporting buffered async reads
- From: Jens Axboe <axboe@xxxxxxxxx>
- Re: [PATCH] ext4: flag as supporting buffered async reads
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Re: [RFC PATCH v2 2/5] jbd2: introduce journal callbacks j_submit|finish_inode_data_buffers
- From: Jan Kara <jack@xxxxxxx>
- Re: [RFC PATCH v2 1/5] jbd2: test case for ext4 data=journal/mmap() journal corruption
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass
- From: Shijie Luo <luoshijie1@xxxxxxxxxx>
- Re: [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v5 2/2] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v3] e2image: add option to ignore fs errors
- From: Artem Blagodarenko <artem.blagodarenko@xxxxxxxxx>
- Re: [PATCH v5 2/2] ext4: limit the length of per-inode prealloc list
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v5 2/2] ext4: limit the length of per-inode prealloc list
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: Generic questions about ext4
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] ext4: use kmemdup_nul() instead of kstrndup()
- From: Jan Kara <jack@xxxxxxx>
- [PATCH v5 2/2] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v5 1/2] ext4: reorganize if statement of ext4_mb_release_context()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Generic questions about ext4
- From: Rogério Brito <rbrito@xxxxxxxxxx>
- Re: [PATCH v3] ext4: fix log printing of ext4_mb_regular_allocator()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v3] ext4: fix log printing of ext4_mb_regular_allocator()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH v3] ext4: fix log printing of ext4_mb_regular_allocator()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: libext2fs: mkfs.ext3 really slow on centos 8.2
- From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
- Re: libext2fs: mkfs.ext3 really slow on centos 8.2
- From: Maciej Jablonski <mafjmafj@xxxxxxxxx>
- 答复: [PATCH] jbd2: fix descriptor block checksum failed after format with lazy_journal_init=1
- From: 常凤楠 <changfengnan@xxxxxxxxxxxxx>
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: 姜迎 <jiangying8582@xxxxxxx>
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: [PATCH v4 1/2] ext4: reorganize if statement of ext4_mb_release_context()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: Ritesh Harjani <ritesh.list@xxxxxxxxx>
- [PATCH v2] ext4: fix log printing of ext4_mb_regular_allocator()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH] ext4: fix log printing of ext4_mb_regular_allocator()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH] ext4: fix log printing of ext4_mb_regular_allocator()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH] ext4: Fix checking of entry validity
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Re: [PATCH v2 2/2] ext4: rename system_blks to s_system_blks inside ext4_sb_info
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v2 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: delete invalid comments near ext4_mb_check_limits()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: optimize the implementation of ext4_mb_good_group()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: put grp related checks into ext4_mb_good_group()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: fix log printing of ext4_mb_regular_allocator()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: fix typos in ext4_mb_regular_allocator() comment
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v2] ext4: delete invalid ac_b_extent backup inside ext4_mb_use_best_found()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: put grp related checks into ext4_mb_good_group()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] ext4: delete invalid ac_b_extent backup inside ext4_mb_use_best_found()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] ext4: delete invalid ac_b_extent backup inside ext4_mb_use_best_found()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [EXT4] orphaned inodes on RO device trigger "unable to handle kernel paging request at"
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] ext4: fix typos in ext4_mb_regular_allocator() comment
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: libext2fs: mkfs.ext3 really slow on centos 8.2
- From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
- Re: libext2fs: mkfs.ext3 really slow on centos 8.2
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] ext4: optimize the implementation of ext4_mb_good_group()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] ext4: fix log printing of ext4_mb_regular_allocator()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH] ext4: flag as supporting buffered async reads
- From: Jens Axboe <axboe@xxxxxxxxx>
- [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass
- From: Shijie Luo <luoshijie1@xxxxxxxxxx>
- Re: [PATCH] mballoc: Replace seq_printf with seq_puts
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Lots of free extents, lots of contiguous free space, and fragmentation lvl is ~15%?
- From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
- Re: [PATCH] ext4: change to use fallthrough macro instead of fallthrough comments
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- Re: libext2fs: mkfs.ext3 really slow on centos 8.2
- From: Maciej Jablonski <mafjmafj@xxxxxxxxx>
- [PATCH] ext4: change to use fallthrough macro instead of fallthrough comments
- From: Shijie Luo <luoshijie1@xxxxxxxxxx>
- [PATCH v3] fcntl: Add 32bit filesystem mode
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Re: [PATCH] ext4: remove unused parameter of ext4_generic_delete_entry function
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH] ext4: remove unused parameter of ext4_generic_delete_entry function
- From: Kyoungho Koo <rnrudgh@xxxxxxxxx>
- [PATCH] mballoc: Replace seq_printf with seq_puts
- From: Xu Wang <vulab@xxxxxxxxxxx>
- [RFC PATCH v2/TEST CASE]
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2/SETUP SCRIPT]
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 5/5] ext4/jbd2: debugging messages
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 4/5] ext4: data=journal: add inode to transaction inode list in ext4_page_mkwrite()
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 3/5] ext4: data=journal: write-protect pages on submit inode data buffers callback
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 2/5] jbd2: introduce journal callbacks j_submit|finish_inode_data_buffers
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 0/5] ext4/jbd2: data=journal: write-protect pages on transaction commit
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- [RFC PATCH v2 1/5] jbd2: test case for ext4 data=journal/mmap() journal corruption
- From: Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: Fix checking of entry validity
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- From: Andreas Dilger <adilger@xxxxxxxxx>
- [PATCH] ext4: use kmemdup_nul() instead of kstrndup()
- From: Xianting Tian <xianting_tian@xxxxxxx>
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- From: Wang Shilong <wangshilong1991@xxxxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] ext4: fix marking group trimmed if all blocks not trimmed
- Re: [PATCH] ext4: move buffer_mapped() to proper position
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [GIT PULL] Unicode patches for v5.9
- From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: Fix checking of entry validity
- Re: [PATCH] ext4: move buffer_mapped() to proper position
- Re: [PATCH v3 4/5] jbd2: abort journal if free a async write error metadata buffer
- Re: [PATCH v3 2/5] ext4: remove ext4_buffer_uptodate()
- Re: [PATCH v3 1/5] ext4: abort the filesystem if failed to async write metadata buffer
- [ext4:dev] BUILD SUCCESS 0f9be45c08148d3c9686671acaf08579b49ba2f0
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Ira Weiny <ira.weiny@xxxxxxxxx>
- Re: [PATCH v2] ext4/002: Test read-only external journal device
- [PATCH] ext4: fix typos in ext4_mb_regular_allocator() comment
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4: delete invalid comments near ext4_mb_check_limits()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4: put grp related checks into ext4_mb_good_group()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4: fix log printing of ext4_mb_regular_allocator()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4: optimize the implementation of ext4_mb_good_group()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [EXT4] orphaned inodes on RO device trigger "unable to handle kernel paging request at"
- From: Henk Kraal <h.kraal@xxxxxxxxx>
- [PATCH v2] ext4: delete invalid ac_b_extent backup inside ext4_mb_use_best_found()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [RFC 1/1] pmem: Add cond_resched() in bio_for_each_segment loop in pmem_make_request
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH v4 2/2] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v4 1/2] ext4: reorganize if statement of ext4_mb_release_context()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH v2 2/3] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v2 2/2] ext4: rename system_blks to s_system_blks inside ext4_sb_info
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v2 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [ext4:dev] BUILD SUCCESS fe1edafb90b34392aa1f6d8041faa4e404bb250c
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- Re: [PATCH 0/6 v3] ext4: Check journal inode extents more carefully
- Re: [GIT PULL v2] iomap: new code for 5.9-rc1
- From: pr-tracker-bot@xxxxxxxxxx
- Re: [GIT PULL] ext2, udf, reiserfs, quota cleanups and minor fixes for 5.9-rc1
- From: pr-tracker-bot@xxxxxxxxxx
- [ext4:dev 19/21] fs/ext4/super.c:3515:20: warning: variable 'lr_mode' set but not used
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: [PATCH v2] ext4: remove some redundant function declarations
- [PATCH v6] ext4: fix direct I/O read error for kernel stable rc 4.9
- From: Jiang Ying <jiangying8582@xxxxxxx>
- [GIT PULL v2] iomap: new code for 5.9-rc1
- From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
- Re: [PATCH v2] fcntl: Add 32bit filesystem mode
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Re: [PATCH] jbd2: fix descriptor block checksum failed after format with lazy_journal_init=1
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v6] ext4: fix direct I/O read error for kernel stable rc 4.9
- From: Greg KH <greg@xxxxxxxxx>
- Re: ext4: delete the invalid BUGON in ext4_mb_load_buddy_gfp()
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] ext4: export msg_count and warning_count via sysfs
- Re: [PATCH v5] ext4: fix direct I/O read error for kernel stable rc4.4
- From: Greg KH <greg@xxxxxxxxx>
- [PATCH v5] ext4: fix direct I/O read error for kernel stable rc4.4
- From: Jiang Ying <jiangying8582@xxxxxxx>
- Re: stable rc 4.4 - v4.4.232-33-g0b3898baf614 - build breaks on arm64, arm, x86_64 and i386.
- From: Jan Kara <jack@xxxxxxx>
- [PATCH v3 2/2] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v3 1/2] ext4: reorganize if statement of ext4_mb_release_context()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH] ext4: handle option set by mount flags correctly
- Re: [PATCH] jbd2: fix incorrect code style
- Re: [PATCH v2] ext4: handle read only external journal device
- Re: ext4: fix spelling typos in ext4_mb_initialize_context
- Re: [PATCH] ext4: use generic names for generic ioctls
- Re: [PATCH] ext4: don't hardcode bit values in EXT4_FL_USER_*
- Re: [PATCH v3] ext4: don't BUG on inconsistent journal feature
- Re: [PATCH] ext4: Do not block RWF_NOWAIT dio write on unallocated space
- Re: [PATCH] Replace HTTP links with HTTPS ones: Ext4
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_unlink
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_truncate
- Re: [PATCH v3 1/2] ext4: introduce EXT4_BG_WAS_TRIMMED to optimize trim
- Re: [PATCH] jbd2: add the missing unlock_buffer() in the error path of jbd2_write_superblock()
- Re: [PATCH] ext4: Delete unnecessary checks before brelse()
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: 姜迎 <jiangying8582@xxxxxxx>
- Re: [PATCH] ext4: Fix checking of entry validity
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Re: [PATCH] ext4: use generic names for generic ioctls
- From: Jan Kara <jack@xxxxxxx>
- Re: ext4: fix spelling typos in ext4_mb_initialize_context
- From: Jan Kara <jack@xxxxxxx>
- Re: [GIT PULL] iomap: new code for 5.9-rc1
- From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
- Re: [GIT PULL] iomap: new code for 5.9-rc1
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [GIT PULL] iomap: new code for 5.9-rc1
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH] mke2fs: Warn if fs block size is incompatible with DAX
- From: Jan Kara <jack@xxxxxxx>
- [GIT PULL] iomap: new code for 5.9-rc1
- From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
- Re: [PATCH v3] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: Greg KH <greg@xxxxxxxxx>
- Re: [PATCH] ext4: Do not block RWF_NOWAIT dio write on unallocated space
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 00/18] VFS: Filesystem information [ver #21]
- From: David Howells <dhowells@xxxxxxxxxx>
- stable rc 4.4 - v4.4.232-33-g0b3898baf614 - build breaks on arm64, arm, x86_64 and i386.
- From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
- Re: [PATCH] ext4: don't hardcode bit values in EXT4_FL_USER_*
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2 2/3] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [GIT PULL] ext2, udf, reiserfs, quota cleanups and minor fixes for 5.9-rc1
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2 3/3] ext4: add needed paramter to ext4_mb_discard_preallocations trace
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH v4] ext4: fix direct I/O read error
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2 2/3] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v4] ext4: fix direct I/O read error
- From: Jiang Ying <jiangying8582@xxxxxxx>
- [PATCH v4] ext4: fix direct I/O read error
- From: Jiang Ying <jiangying8582@xxxxxxx>
- [PATCH] ext4: fix direct I/O read error
- From: Jiang Ying <jiangying8582@xxxxxxx>
- Re: [PATCH v2 3/3] ext4: add needed paramter to ext4_mb_discard_preallocations trace
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2 2/3] ext4: limit the length of per-inode prealloc list
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2 1/3] ext4: reorganize if statement of ext4_mb_release_context()
- From: Andreas Dilger <adilger@xxxxxxxxx>
- [PATCH] ext4: delete duplicated words + other fixes
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
- [PATCH v2 3/3] ext4: add needed paramter to ext4_mb_discard_preallocations trace
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v2 2/3] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH v2 1/3] ext4: reorganize if statement of ext4_mb_release_context()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH 00/18] VFS: Filesystem information [ver #21]
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
- Re: [PATCH 00/18] VFS: Filesystem information [ver #21]
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v3] ext4: fix direct I/O read error
- From: Jan Kara <jack@xxxxxxx>
- [PATCH] ext4: delete invalid ac_b_extent backup inside ext4_mb_use_best_found()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH v2] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- [PATCH] ext4: flag as supporting buffered async reads
- From: Jens Axboe <axboe@xxxxxxxxx>
- Re: [RFC 1/1] pmem: Add cond_resched() in bio_for_each_segment loop in pmem_make_request
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] ext4: mballoc - limit scanning of uninitialized groups
- From: Jan Kara <jack@xxxxxxx>
- Re: [GIT PULL] fscrypt updates for 5.9
- From: pr-tracker-bot@xxxxxxxxxx
- Re: [GIT PULL] fsverity updates for 5.9
- From: pr-tracker-bot@xxxxxxxxxx
- [PATCH] ext4: fix marking group trimmed if all blocks not trimmed
- From: Lazar Beloica <lazarbeloica@xxxxxxxxx>
- [PATCH 14/18] fsinfo: Add support to ext4 [ver #21]
- From: David Howells <dhowells@xxxxxxxxxx>
- [PATCH 00/18] VFS: Filesystem information [ver #21]
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: Data exposure on IO error
- From: Jan Kara <jack@xxxxxxx>
- Re: [RFC 1/1] pmem: Add cond_resched() in bio_for_each_segment loop in pmem_make_request
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [GIT PULL] fsverity updates for 5.9
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [GIT PULL] fscrypt updates for 5.9
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [RFC 1/1] pmem: Add cond_resched() in bio_for_each_segment loop in pmem_make_request
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: Fix checking of entry validity
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Re: [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: Data exposure on IO error
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Data exposure on IO error
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 3/4] ext4: indicate via a block bitmap read is prefetched via a tracepoint
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 0/4] V2- ext4 block bitmap prefetch patches
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH] ext4: Fix checking of entry validity
- From: Jan Kara <jack@xxxxxxx>
- [PATCH] ext4: move buffer_mapped() to proper position
- From: Xianting Tian <xianting_tian@xxxxxxx>
- Re: [Cluster-devel] [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: ext4/xfs: about switching underlying 512B sector devices to 4K ones
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- [ext4:dev] BUILD SUCCESS 43c18181b7017c723fb057beb283e86e228416eb
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: [PATCH v2] create_inode: set xattrs to the root directory as well
- From: Antoine Tenart <antoine.tenart@xxxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- Re: [PATCH 1/1] ext4: fix potential negative array index in do_split()
- Re: ext4/xfs: about switching underlying 512B sector devices to 4K ones
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: check superblock mapped prior to get write access
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext4: fix spelling mistakes in extents.c
- Re: ext4/xfs: about switching underlying 512B sector devices to 4K ones
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 2/2] ext4: rename system_blks to s_system_blks inside ext4_sb_info
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] ext4: Fix comment typo "the the".
- From: Jan Kara <jack@xxxxxxx>
- Re: Changing a workload results in performance drop
- From: Jan Kara <jack@xxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- ext4/xfs: about switching underlying 512B sector devices to 4K ones
- From: Takuya Yoshikawa <takuya.yoshikawa@xxxxxxxxx>
- [RFC 1/1] pmem: Add cond_resched() in bio_for_each_segment loop in pmem_make_request
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH 2/2] ext4: rename system_blks to s_system_blks inside ext4_sb_info
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4: check superblock mapped prior to get write access
- From: Xianting Tian <xianting_tian@xxxxxxx>
- [PATCH 3/6] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 4/6] ext4: Fold ext4_data_block_valid_rcu() into the caller
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 6/6] ext4: Correctly restore system zone info when remount fails
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 2/6] ext4: Don't allow overlapping system zones
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 5/6] ext4: Handle add_system_zone() failure in ext4_setup_system_zone()
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 1/6] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 0/6 v3] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 3/6] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 3/6] ext4: Check journal inode extents more carefully
- From: luomeng <luomeng12@xxxxxxxxxx>
- [Bug 207729] Mounting EXT4 with data_err=abort does not abort journal on data block write failure
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [PATCH v2] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- [Bug 207729] Mounting EXT4 with data_err=abort does not abort journal on data block write failure
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- [Bug 207729] Mounting EXT4 with data_err=abort does not abort journal on data block write failure
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] ext4: handle option set by mount flags correctly
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH 0/4] e2fsprogs: fix and document the stable_inodes feature
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v6 6/7] fscrypt: document inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 0/5] fscrypt, fs-verity: one-time init fixes
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] chattr/lsattr: Support dax attribute
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH] chattr/lsattr: Support dax attribute
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 6/6] ext4: Correctly restore system zone info when remount fails
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 5/6] ext4: Handle add_system_zone() failure in ext4_setup_system_zone()
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- [PATCH 4/6] ext4: Fold ext4_data_block_valid_rcu() into the caller
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 5/6] ext4: Handle add_system_zone() failure in ext4_setup_system_zone()
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 6/6] ext4: Correctly restore system zone info when remount fails
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 3/6] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 2/6] ext4: Don't allow overlapping system zones
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 0/6 v2] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 1/6] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 3/4] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- [PATCH v2] ext4/002: Test read-only external journal device
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- [Bug 207729] Mounting EXT4 with data_err=abort does not abort journal on data block write failure
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH] ext4/309: Test read-only external journal device
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- [PATCH] chattr/lsattr: Support dax attribute
- From: Xiao Yang <yangx.jy@xxxxxxxxxxxxxx>
- Re: [PATCH] ext2: ext2.h: fix duplicated word + typos
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] jbd2: check bh2jh() before accessing it
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] jbd2: fix incorrect code style
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: ext4: delete the invalid BUGON in ext4_mb_load_buddy_gfp()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- ext4: delete the invalid BUGON in ext4_mb_load_buddy_gfp()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [f2fs-dev] [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] ext4/309: Test read-only external journal device
- From: Eryu Guan <guan@xxxxxxx>
- Re: [f2fs-dev] [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- [PATCH] ext4: export msg_count and warning_count via sysfs
- From: Dmitry Monakhov <dmtrmonakhov@xxxxxxxxxxxxxx>
- Re: [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- [PATCH v6 6/7] fscrypt: document inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 7/7] fscrypt: update documentation for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 1/7] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v6 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v5 1/7] fscrypt: Add functions for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options
- From: Благодаренко Артём <artem.blagodarenko@xxxxxxxxx>
- [PATCH 13/17] fsinfo: Add support to ext4 [ver #20]
- From: David Howells <dhowells@xxxxxxxxxx>
- [PATCH 00/17] VFS: Filesystem information [ver #20]
- From: David Howells <dhowells@xxxxxxxxxx>
- [PATCH v5 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 7/7] fscrypt: update documentation for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 6/7] fscrypt: document inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v5 1/7] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH 3/4] ext4: indicate via a block bitmap read is prefetched via a tracepoint
- From: Благодаренко Артём <artem.blagodarenko@xxxxxxxxx>
- Re: [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
- From: Благодаренко Артём <artem.blagodarenko@xxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v2] ext4: remove some redundant function declarations
- From: Shijie Luo <luoshijie1@xxxxxxxxxx>
- Re: [PATCH] ext4:remove some redundant function declarations
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH 3/3] ext4: add needed paramter to, ext4_mb_discard_preallocations trace
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH 2/3] ext4: limit the length of per-inode prealloc list
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH 1/3] ext4: reorganize if statement of, ext4_mb_release_context()
- From: brookxu <brookxu.cn@xxxxxxxxx>
- [PATCH] ext4:remove some redundant function declarations
- From: Shijie Luo <luoshijie1@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- [PATCH] ext4: handle option set by mount flags correctly
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- From: Shuichi Ihara <sihara@xxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH v4 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 1/7] fscrypt: Add functions for direct I/O support
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 6/7] fscrypt: document inline encryption support
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 7/7] fscrypt: update documentation for direct I/O support
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: Exporting ext4-specific information through fsinfo attributes
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [Cluster-devel] [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Bob Peterson <rpeterso@xxxxxxxxxx>
- Re: Exporting ext4-specific information through fsinfo attributes
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH] mke2fs: fix up check for hardlinks always false if inode > 0xFFFFFFFF
- From: Hongxu Jia <hongxu.jia@xxxxxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
- [PATCH 3/5] fscrypt: use smp_load_acquire() for ->s_master_keys
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 5/5] fs-verity: use smp_load_acquire() for ->i_verity_info
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 2/5] fscrypt: use smp_load_acquire() for fscrypt_prepared_key
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 4/5] fscrypt: use smp_load_acquire() for ->i_crypt_info
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 1/5] fscrypt: switch fscrypt_do_sha256() to use the SHA-256 library
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 0/5] fscrypt, fs-verity: one-time init fixes
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH 1/3] xfs: use ENOTBLK for direct I/O to buffered I/O fallback
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH v4 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- [PATCH v8 7/7] ext4: fast commit recovery path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 5/7] ext4: main fast-commit commit path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 6/7] jbd2: fast commit recovery path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 4/7] jbd2: add fast commit machinery
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 3/7] ext4 / jbd2: add fast commit initialization
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 2/7] ext4: add fast_commit feature and handling for extended mount options
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 1/7] doc: update ext4 and journalling docs to include fast commit feature
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v8 0/7] ext4: add fast commits feature
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- iomap write invalidation v2
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH 1/3] xfs: use ENOTBLK for direct I/O to buffered I/O fallback
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH 2/3] iomap: Only invalidate page cache pages on direct IO writes
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH] fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: RFC: iomap write invalidation
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- [PATCH v7 7/7] ext4: fast commit recovery path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 5/7] ext4: main fast-commit commit path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 6/7] jbd2: fast commit recovery path
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 3/7] ext4 / jbd2: add fast commit initialization
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 4/7] jbd2: add fast commit machinery
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 2/7] ext4: add fast_commit feature and handling for extended mount options
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 1/7] doc: update ext4 and journalling docs to include fast commit feature
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- [PATCH v7 0/7] ext4: add fast commits feature
- From: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: Exporting ext4-specific information through fsinfo attributes
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: Exporting ext4-specific information through fsinfo attributes
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: RFC: iomap write invalidation
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: RFC: iomap write invalidation
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH 4/4] ext4: Fold ext4_data_block_valid_rcu() into the caller
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 3/4] ext4: Check journal inode extents more carefully
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 2/4] ext4: Don't allow overlapping system zones
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: Exporting ext4-specific information through fsinfo attributes
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 3/4] ext4: indicate via a block bitmap read is prefetched via a tracepoint
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v4 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 7/7] fscrypt: update documentation for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v4 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 7/7] fscrypt: update documentation for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 6/7] fscrypt: document inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 1/7] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: [PATCH v3 1/7] fscrypt: Add functions for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v3 7/7] fscrypt: update documentation for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v3 6/7] fscrypt: document inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v3 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [GIT PULL] Unicode patches for v5.9
- From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
- [PATCH] ext2: ext2.h: fix duplicated word + typos
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v2] fcntl: Add 32bit filesystem mode
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- [PATCH] tests: replace perl usage with shell built-in
- From: Andreas Dilger <adilger@xxxxxxxxx>
- [PATCH] jbd2: check bh2jh() before accessing it
- From: Xianting Tian <xianting_tian@xxxxxxx>
- [PATCH] jbd2: fix incorrect code style
- From: Xianting Tian <xianting_tian@xxxxxxx>
- Re: [PATCH v2] fs/direct-io: fix one-time init of ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v2] fs/direct-io: fix one-time init of ->s_dio_done_wq
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: [PATCH v2] fs/direct-io: fix one-time init of ->s_dio_done_wq
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- [PATCH 4/4] ext4: add prefetch_block_bitmaps mount options
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 1/4] ext4: add prefetching for block allocation bitmaps
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 3/4] ext4: indicate via a block bitmap read is prefetched via a tracepoint
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 0/4] ex4 block bitmap prefetching
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- [PATCH 2/4] ext4: skip non-loaded groups at cr=0/1 when scanning for good groups
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH v2] create_inode: set xattrs to the root directory as well
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] ext4: handle read only external journal device
- From: Andreas Dilger <adilger@xxxxxxxxx>
- [PATCH v2] create_inode: set xattrs to the root directory as well
- From: Antoine Tenart <antoine.tenart@xxxxxxxxxxx>
- [PATCH v2] ext4: handle read only external journal device
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH] ext4: handle read only external journal device
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH] create_inode: set xattrs to the root directory as well
- From: Antoine Tenart <antoine.tenart@xxxxxxxxxxx>
- Re: [PATCH] ext4: handle read only external journal device
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] create_inode: set xattrs to the root directory as well
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] create_inode: set xattrs to the root directory as well
- From: Antoine Tenart <antoine.tenart@xxxxxxxxxxx>
- Re: [PATCH v2] fs/direct-io: fix one-time init of ->s_dio_done_wq
- From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
- [PATCH v2] fs/direct-io: fix one-time init of ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 2/5] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 7/7] fscrypt: update documentation for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 6/7] fscrypt: document inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 1/7] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- [PATCH v2 7/7] fscrypt: update documentation for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 6/7] fscrypt: document inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 3/7] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 4/7] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 2/7] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 1/7] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 0/7] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH] ext4: handle read only external journal device
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents
- From: Wolfgang Frisch <wolfgang.frisch@xxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 3/4] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 4/4] ext4: Fold ext4_data_block_valid_rcu() into the caller
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 2/4] ext4: Don't allow overlapping system zones
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 0/4] ext4: Check journal inode extents more carefully
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- ext4: fix spelling typos in ext4_mb_initialize_context
- From: brookxu <brookxu.cn@xxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: RFC: iomap write invalidation
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- [PATCH] ext4: use generic names for generic ioctls
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH] fs: i_version mntopt gets visible through /proc/mounts
- From: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH] fs: i_version mntopt gets visible through /proc/mounts
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
- Re: [PATCH] fs: i_version mntopt gets visible through /proc/mounts
- From: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Re: [PATCH 2/5] direct-io: add support for fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: David Sterba <dsterba@xxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH] ext4: catch integer overflow in ext4_cache_extents
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH 1/2] iomap: Only invalidate page cache pages on direct IO writes
- From: Christoph Hellwig <hch@xxxxxx>
- RFC: iomap write invalidation
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH] fs/direct-io: avoid data race on ->s_dio_done_wq
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH] ext4: don't hardcode bit values in EXT4_FL_USER_*
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v3 0/5] ext4: fix inconsistency since async write metadata buffer error
- From: "zhangyi (F)" <yi.zhang@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: [PATCH] ext2: initialize quota info in ext2_xattr_set()
- From: Chengguang Xu <cgxu519@xxxxxxxxxxxx>
- [RFC] quiet "inode nnn extent tree could be narrower"?
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH v2] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- [PATCH v3] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2] ext4: don't BUG on inconsistent journal feature
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- Re: [PATCH 2/5] direct-io: add support for fscrypt using blk-crypto
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: [PATCH 5/5] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 5/5] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Chao Yu <yuchao0@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH 0/5] add support for direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 4/5] ext4: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 3/5] iomap: support direct I/O with fscrypt using blk-crypto
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 1/5] fscrypt: Add functions for direct I/O support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 1/5] fscrypt: Add functions for direct I/O support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH 2/5] direct-io: add support for fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH 4/5] ext4: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH 5/5] f2fs: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH 3/5] iomap: support direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH 0/5] add support for direct I/O with fscrypt using blk-crypto
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH] generic/530: Require metadata journaling
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: [xfstests-bld PATCH v2] test-appliance: exclude generic/587 from the encrypt tests
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [xfstests-bld PATCH v2] test-appliance: exclude generic/587 from the encrypt tests
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [xfstests-bld PATCH] test-appliance: exclude generic/587 from the encrypt tests
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [xfstests-bld PATCH] test-appliance: exclude generic/587 from the encrypt tests
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [Bug 207165] Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end
- From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
- Re: [PATCH v2] ext4: don't BUG on inconsistent journal feature
- From: kernel test robot <lkp@xxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- [PATCH v2] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- [PATCH] mke2fs: Warn if fs block size is incompatible with DAX
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext4: don't BUG on inconsistent journal feature
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
- [PATCH] ext4: don't BUG on inconsistent journal feature
- From: Jan Kara <jack@xxxxxxx>
- [PATCH] generic/530: Require metadata journaling
- From: Jan Kara <jack@xxxxxxx>
- Re: [Cluster-devel] always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Steven Whitehouse <swhiteho@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- [PATCH 6/6] btrfs: split btrfs_direct_IO to read and write part
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 5/6] btrfs: remove BTRFS_INODE_READDIO_NEED_LOCK
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 4/6] fs: remove dio_end_io()
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 3/6] btrfs: switch to iomap_dio_rw() for dio
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 1/6] iomap: Convert wait_for_completion to flags
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH 0/6 v11] btrfs direct-io using iomap
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: [PATCH] ext4: Do not block RWF_NOWAIT dio write on unallocated space
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v4 4/4] ext4: add inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 4/4] ext4: add inline encryption support
- Re: [PATCH v4 2/4] fscrypt: add inline encryption support
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: [PATCH v12 3/4] f2fs: Use generic casefolding support
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH v4 1/4] fs: introduce SB_INLINECRYPT
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Christoph Hellwig <hch@xxxxxx>
- Re: [PATCH 1/1] ext4: fix potential negative array index in do_split()
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v12 2/4] fs: Add standard casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH] ext4: Do not block RWF_NOWAIT dio write on unallocated space
- From: Jan Kara <jack@xxxxxxx>
- Re: RWF_NOWAIT writes not failing when writing to a range with holes
- From: Jan Kara <jack@xxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: [PATCH] ext4: fix spelling mistakes in extents.c
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext2: initialize quota info in ext2_xattr_set()
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH] ext4: Delete unnecessary checks before brelse()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] jbd2: add the missing unlock_buffer() in the error path of jbd2_write_superblock()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH] ext2: initialize quota info in ext2_xattr_set()
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_unlink
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_truncate
- From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
- [PATCH v12 1/4] unicode: Add utf8_casefold_hash
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v12 2/4] fs: Add standard casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v12 3/4] f2fs: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v12 4/4] ext4: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: [PATCH v11 2/4] fs: Add standard casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: [PATCH v11 2/4] fs: Add standard casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v11 1/4] unicode: Add utf8_casefold_hash
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v11 4/4] ext4: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v11 3/4] f2fs: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v11 2/4] fs: Add standard casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v11 0/4] Prepare for upcoming Casefolding/Encryption patches
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: [PATCH v10 4/4] ext4: Use generic casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v10 3/4] f2fs: Use generic casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v10 1/4] unicode: Add utf8_casefold_hash
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v10 2/4] fs: Add standard casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v2] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 1/3] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v4 0/4] Inline Encryption Support for fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v10 1/4] unicode: Add utf8_casefold_hash
- From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Christoph Hellwig <hch@xxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- [PATCH v10 2/4] fs: Add standard casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v10 4/4] ext4: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v10 1/4] unicode: Add utf8_casefold_hash
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v10 0/4] Prepare for upcoming Casefolding/Encryption patches
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- [PATCH v10 3/4] f2fs: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: [PATCH v9 4/4] ext4: Use generic casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: [PATCH 1/3] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Florian Schmaus <flo@xxxxxxxxxxxx>
- [PATCH v2] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Florian Schmaus <flo@xxxxxxxxxxxx>
- Re: [PATCH 2/3] e4crypt: refactor set_policy a little
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH 1/3] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH 3/3] Clarify in e4crypt man page that -S is an optional argument
- From: Florian Schmaus <flo@xxxxxxxxxxxx>
- [PATCH 1/3] e4crypt: if salt is explicitly provided to add_key, then use it
- From: Florian Schmaus <flo@xxxxxxxxxxxx>
- [PATCH 2/3] e4crypt: refactor set_policy a little
- From: Florian Schmaus <flo@xxxxxxxxxxxx>
- [PATCH] Replace HTTP links with HTTPS ones: Ext4
- From: "Alexander A. Klimov" <grandmaster@xxxxxxxxxxxx>
- Re: [PATCH v2] fcntl: Add 32bit filesystem mode
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_truncate
- From: Andreas Dilger <adilger@xxxxxxxxx>
- BUG: Bad page state (7)
- From: syzbot <syzbot+d518e502e242315e777c@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v9 2/4] fs: Add standard casefolding support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v2] ext2: fix some incorrect comments in inode.c
- From: Jan Kara <jack@xxxxxxx>
- [PATCH v2] ext2: fix some incorrect comments in inode.c
- From: Chengguang Xu <cgxu519@xxxxxxxxxxxx>
- Re: [PATCH] ext2: delete incorrect comment for ext2_blks_to_allocate()
- From: cgxu <cgxu519@xxxxxxxxxxxx>
- Re: [PATCH] ext2: delete incorrect comment for ext2_blks_to_allocate()
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v9 2/4] fs: Add standard casefolding support
- From: Daniel Rosenberg <drosen@xxxxxxxxxx>
- Re: Grow ext4 filesystem on mounted device
- From: Alok Jain <jain.alok103@xxxxxxxxx>
- Re: Grow ext4 filesystem on mounted device
- From: Alok Jain <jain.alok103@xxxxxxxxx>
- Re: Grow ext4 filesystem on mounted device
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Grow ext4 filesystem on mounted device
- From: Alok Jain <jain.alok103@xxxxxxxxx>
- [PATCH] ext2: delete incorrect comment for ext2_blks_to_allocate()
- From: Chengguang Xu <cgxu519@xxxxxxxxxxxx>
- [PATCH v4 4/4] ext4: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 2/4] fscrypt: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 3/4] f2fs: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 1/4] fs: introduce SB_INLINECRYPT
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v4 0/4] Inline Encryption Support for fscrypt
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [BUG] invalid superblock checksum possibly due to race
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v3] ext4: fix direct I/O read error
- From: 姜迎 <jiangying8582@xxxxxxx>
- [PATCH] create_inode: set xattrs to the root directory as well
- From: Antoine Tenart <antoine.tenart@xxxxxxxxxxx>
- always fall back to buffered I/O after invalidation failures, was: Re: [PATCH 2/6] iomap: IOMAP_DIO_RWF_NO_STALE_PAGECACHE return if page invalidation fails
- From: Christoph Hellwig <hch@xxxxxx>
- [PATCH v2] ext4: lost matching-pair of trace in ext4_truncate
- From: zhengliang <zhengliang6@xxxxxxxxxx>
- Re: [PATCH v3 3/4] f2fs: add inline encryption support
- From: Chao Yu <yuchao0@xxxxxxxxxx>
- Re: [BUG] invalid superblock checksum possibly due to race
- From: Costa Sapuntzakis <costa@xxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/4] fscrypt: add inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v3 3/4] f2fs: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 4/4] ext4: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 2/4] fscrypt: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 1/4] fs: introduce SB_INLINECRYPT
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3 0/4] Inline Encryption Support for fscrypt
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [BUG] invalid superblock checksum possibly due to race
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2 2/4] fscrypt: add inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v2 3/4] f2fs: add inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v2 4/4] ext4: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH v2] ext4: fix direct I/O read error
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- [PATCH v2 3/4] f2fs: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 0/4] Inline Encryption Support for fscrypt
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v2 1/4] fs: introduce SB_INLINECRYPT
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- [PATCH v3] ext4: fix direct I/O read error
- From: Jiang Ying <jiangying8582@xxxxxxx>
- Re: [PATCH v2] ext4: fix direct I/O read error
- From: Markus Elfring <Markus.Elfring@xxxxxx>
- [PATCH v2] ext4: lost matching-pair of trace in ext4_unlink
- From: Yi Zhuang <zhuangyi1@xxxxxxxxxx>
- Re: [PATCH] ext4: lost matching-pair of trace in ext4_truncate
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH v2] ext4: lost matching-pair of trace in ext4_unlink
- From: Andreas Dilger <adilger@xxxxxxxxx>
- Re: [PATCH] ext4: fix direct I/O read error
- From: Ira Weiny <ira.weiny@xxxxxxxxx>
- [PATCH v2 2/4] fscrypt: add inline encryption support
- From: Satya Tangirala <satyat@xxxxxxxxxx>
- Re: [PATCH v2 4/4] ext4: add inline encryption support
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Re: [PATCH v2 1/4] fs: introduce SB_INLINECRYPT
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- [PATCH v2] ext4: fix direct I/O read error
- From: Jiang Ying <jiangying8582@xxxxxxx>
- [PATCH] ext4: lost matching-pair of trace in ext4_truncate
- From: zhengliang <zhengliang6@xxxxxxxxxx>
[Index of Archives]
[Kernel Announce]
[IETF Annouce]
[Security]
[Netfilter]
[Bugtraq]