Linux Ext4 Filesystem

• Thread Index

• Re: [PATCH 38/42] isdn: replace ->proc_fops with ->proc_show
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] tests: add raw/e2i/qcow2 image create/install test
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH v4 5/7] ext2fs: Add helper functions to access inode numbers
  • From: Alexey Lyashkov <alexey.lyashkov@xxxxxxxxx>
• Release of e2fsprogs 1.44.2
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v4 5/7] ext2fs: Add helper functions to access inode numbers
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 5/7] ext4: pass -ESHUTDOWN code to jbd2 layer
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v4 5/7] ext2fs: Add helper functions to access inode numbers
  • From: Artem Blagodarenko <artem.blagodarenko@xxxxxxxxx>
• Re: [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH 34/40] atm: simplify procfs code
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] ext4: add an interface to load block bitmaps
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [PATCH 14/14] mm: turn on vm_fault_t type checking
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: vm_fault_t conversion, for real
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH 14/14] mm: turn on vm_fault_t type checking
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: simplify procfs code for seq_file instances V3
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: vm_fault_t conversion, for real
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [Jfs-discussion] [PATCH 25/42] jfs: simplify procfs code
  • From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
• Re: [PATCH 10/14] vgem: separate errno from VM_FAULT_* values
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/14] mm: turn on vm_fault_t type checking
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: vm_fault_t conversion, for real
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 10/14] vgem: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 14/14] mm: turn on vm_fault_t type checking
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: vm_fault_t conversion, for real
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH 01/14] orangefs: don't return errno values from ->fault
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH 06/14] btrfs: separate errno from VM_FAULT_* values
  • From: David Sterba <dsterba@xxxxxxx>
• simplify procfs code for seq_file instances V3
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/42] net/can: single_open_net needs to be paired with single_release_net
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/42] proc: don't detour through seq->private to get the inode
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/42] proc: introduce proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/42] ipv{4,6}/udp{,lite}: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/42] proc: introduce proc_create_seq{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/42] ipv{4,6}/tcp: simplify procfs registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/42] proc: simplify proc_register calling conventions
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 14/42] net/kcm: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 11/42] ipv{4,6}/ping: simplify proc file creation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/42] proc: add a proc_create_reg helper
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 12/42] ipv{4,6}/raw: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 15/42] netfilter/x_tables: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 16/42] net: move seq_file_single_net to <linux/seq_file_net.h>
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 19/42] acpi/battery: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 18/42] proc: introduce proc_create_net_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 20/42] sgi-gru: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 13/42] ipv6/flowlabel: simplify pid namespace lookup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 22/42] sg: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 21/42] megaraid: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 17/42] proc: introduce proc_create_net{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 28/42] drbd: switch to proc_create_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 31/42] hostap: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 24/42] ext4: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 41/42] tty: replace ->proc_fops with ->proc_show
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 23/42] afs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 26/42] staging/rtl8192u: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 27/42] resource: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 34/42] netfilter/x_tables: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 25/42] jfs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 29/42] rtc/proc: switch to proc_create_single_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 36/42] atm: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 30/42] bonding: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 10/14] vgem: separate errno from VM_FAULT_* values
  • From: Daniel Vetter <daniel@xxxxxxxx>
• [PATCH 39/42] ide: remove ide_driver_proc_write
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 32/42] neigh: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 38/42] isdn: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 40/42] ide: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 41/42] tty: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 33/42] netfilter/xt_hashlimit: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 42/42] proc: update SIZEOF_PDE_INLINE_NAME for the new pde fields
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 35/42] bluetooth: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 37/42] atm: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/42] proc: introduce a proc_pid_ns helper
  • From: Christoph Hellwig <hch@xxxxxx>
• vm_fault_t conversion, for real
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/14] dax: make the dax_iomap_fault prototype consistent
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/14] mm: remove the unused device_private_entry_fault export
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/14] ceph: untangle ceph_filemap_fault
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/14] btrfs: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/14] ext4: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/14] vgem: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/14] ubifs: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/14] ocfs2: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 11/14] ttm: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 12/14] lustre: separate errno from VM_FAULT_* values
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 14/14] mm: turn on vm_fault_t type checking
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 13/14] mm: move arch specific VM_FAULT_* flags to mm.h
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/14] fs: make the filemap_page_mkwrite prototype consistent
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/14] orangefs: don't return errno values from ->fault
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] ext4: add an interface to load block bitmaps
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [RFC PATCH 0/5] ext4: rework delayed allocated cluster accounting
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] ext4: add an interface to load block bitmaps
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 04/40] proc: introduce proc_create_seq{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 34/40] atm: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: simplify procfs code for seq_file instances V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 06/40] proc: introduce proc_create_single{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH] ext4: add an interface to load block bitmaps
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: INFO: task hung in blk_queue_enter
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: INFO: task hung in ext4_direct_IO
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• INFO: task hung in ext4_direct_IO
  • From: syzbot <syzbot+45843822635038f93354@xxxxxxxxxxxxxxxxxxxxxxxxx>
• [PATCH v2] generic/488: Add SEEK_DATA tests for offsets in the middle of holes
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4/309: Add SEEK_DATA tests for offsets in the middle of holes
  • From: Jan Kara <jack@xxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• [PATCH 3/3] generic: test first read with freeze right after mount
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH 2/3] fstests: define and use TIMEOUT_PROG
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH 1/3] generic/459: use xfs_freeze instead of fsfreeze
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH 0/3] ext4 freeze regression test
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3] ext4: handle errors on ext4_commit_super
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 3/3] ext4: do not update s_last_mounted of a frozen fs
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 2/3] ext4: factor out helper ext4_sample_last_mounted()
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 1/3] vfs: add the sb_start_intwrite_trylock() helper
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: Use @AR@ instead of hardcoded 'ar'
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: update mtime in ext4_punch_hole even if no blocks are released
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [RFC v2 3/4] ext4: add verifier check for symlink with append/immutable flags
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2] fs: ext4: Adding new return type vm_fault_t
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: Fix hole length detection in ext4_ind_map_blocks()
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [RFC PATCH 5/5] ext4: don't release delalloc clusters when invalidating page
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• [RFC PATCH 3/5] ext4: adjust reserved cluster count when removing extents
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• [RFC PATCH 4/5] ext4: release delayed allocated clusters when removing block ranges
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• [RFC PATCH 2/5] ext4: reduce reserved cluster count by number of allocated clusters
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• [RFC PATCH 1/5] ext4: fix reserved cluster accounting at delayed write time
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• [RFC PATCH 0/5] ext4: rework delayed allocated cluster accounting
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• Re: [PATCH] Fstests: ext4: test block reservation leak with bigalloc
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [PATCH 4/4] ext4: mark block bitmap corrupted when found
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 3/4] ext4: mark inode bitmap corrupted when found
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 2/4] ext4: new ext4_mark_group_bitmap_corrupted() helper
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] Fstests: ext4: test block reservation leak with bigalloc
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: [PATCH 0/2] bigalloc + delalloc reservation leak fixes
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [RFC v2 3/4] ext4: add verifier check for symlink with append/immutable flags
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC v2 4/4] btrfs: verify symlinks with append/immutable flags
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 10/10] misc: add e2mmpstatus utility via debugfs
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• RE: [PATCH 2/4] ext4: new ext4_mark_group_bitmap_corrupted() helper
  • From: Wang Shilong <wshilong@xxxxxxx>
• Re: [RFC v2 2/4] xfs: add verifier check for symlink with append/immutable flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ext4/309: Add SEEK_DATA tests for offsets in the middle of holes
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• [RFC v2 0/4] vfs: detect symlink corruption with attributes
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [RFC v2 2/4] xfs: add verifier check for symlink with append/immutable flags
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [RFC v2 1/4] vfs: skip extra attributes check on removal for symlinks
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [RFC v2 3/4] ext4: add verifier check for symlink with append/immutable flags
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [RFC v2 4/4] btrfs: verify symlinks with append/immutable flags
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH] Ext4: tracepoint: fix broken print due to 0%o format
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] Ext4: tracepoint: fix broken print due to 0%o format
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: make function ‘ext4_getfsmap_find_fixed_metadata’ static
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 2/2] ext4: use raw i_version value for ea_inode
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/2] ext4: use XATTR_CREATE in ext4_initxattrs()
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4/309: Add SEEK_DATA tests for offsets in the middle of holes
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] ext4: make function ‘ext4_getfsmap_find_fixed_metadata’ static
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [PATCH] ext4/309: Add SEEK_DATA tests for offsets in the middle of holes
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: Fix hole length detection in ext4_ind_map_blocks()
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH v2] fs: ext4: Adding new return type vm_fault_t
  • From: Souptick Joarder <jrdr.linux@xxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 0/2] bigalloc + delalloc reservation leak fixes
  • From: Eric Whitney <enwlinux@xxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: simplify procfs code for seq_file instances V2
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: David Sterba <dsterba@xxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH] Ext4: df: fix df to report reserved bytes in quota
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• Re: journal_async_commit and external journal
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 0/2] bigalloc + delalloc reservation leak fixes
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• [PATCH v2] fscrypt: add Speck128/256 support
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [RFC PATCH] Ext4: bigalloc: __ext4_es_find_range_type() can be static
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/2] Ext4: bigalloc: do not reserve space for delalloc extents if there is an available cluster
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: e2fsck running for days ?
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• e2fsck running for days ?
  • From: Daniel Beck <am500@xxxxxxxxxxxxxx>
• [Bug 199635] New: UBSAN: Undefined behaviour in fs/ext4/readpage.c
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• INFO: task hung in ext4_file_write_iter
  • From: syzbot <syzbot+ef7ef285f528e7ccbbcc@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] bigalloc + delalloc reservation leak fixes
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [PATCH 1/2] Ext4: bigalloc: fix overreservation on quota accounting
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• [PATCH 2/2] Ext4: bigalloc: do not reserve space for delalloc extents if there is an available cluster
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• [PATCH 0/2] bigalloc + delalloc reservation leak fixes
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• [PATCH] Fstests: ext4: test block reservation leak with bigalloc
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: simplify procfs code for seq_file instances V2
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: simplify procfs code for seq_file instances V2
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• kernel panic: EXT4-fs (device loop0): panic forced after error
  • From: syzbot <syzbot+a9a45987b8b2daabdc88@xxxxxxxxxxxxxxxxxxxxxxxxx>
• [Bug 199629] New: kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0)
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH] ext4: make function ‘ext4_getfsmap_find_fixed_metadata’ static
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: [PATCH 38/40] ide: remove ide_driver_proc_write
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 34/40] atm: simplify procfs code
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v3 3/3] ext4: do not update s_last_mounted of a frozen fs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• journal_async_commit and external journal
  • From: Niklas Hambüchen <mail@xxxxxx>
• Re: [PATCH 04/10] tests: replace perl usage with shell built-in
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 10/10] misc: add e2mmpstatus utility via debugfs
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 10/10] misc: add e2mmpstatus utility via debugfs
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH v4 7/7] e2fsck: INODE64 high part is more important then LUFID
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v4 6/7] ext2fs: add EXT4_FEATURE_INCOMPAT_64INODE support
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v4 5/7] ext2fs: Add helper functions to access inode numbers
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 04/10] tests: replace perl usage with shell built-in
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH v4 1/7] e2fsck: add support for dirdata feature
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v4 1/7] e2fsck: add support for dirdata feature
  • From: Artem Blagodarenko <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 7/7] e2fsck: INODE64 high part is more important then LUFID
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 6/7] ext2fs: add EXT4_FEATURE_INCOMPAT_64INODE support
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 5/7] ext2fs: Add helper functions to access inode numbers
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 2/7] tests: add basic tests for dirdata feature
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 3/7] debugfs: 64bit inode support
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 1/7] e2fsck: add support for dirdata feature
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• [PATCH v4 0/7] 64bit inode e2fsprogs support
  • From: c17828 <artem.blagodarenko@xxxxxxxxx>
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Jan Kara <jack@xxxxxxx>
• KASAN: use-after-free Read in ext4_data_block_valid
  • From: syzbot <syzbot+1e470567330b7ad711d5@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Reg: logical volume file system is getting corrupted after multiple reboots.
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: Reg: logical volume file system is getting corrupted after multiple reboots.
  • From: RAJESH DASARI <raajeshdasari@xxxxxxxxx>
• Re: [PATCH] ext4: fix bitmap position validation
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH] fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: [PATCH v3 2/5] dumpe2fs: add JSON output of block groups
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 10/10] misc: add e2mmpstatus utility via debugfs
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 09/10] e2fsck: set dir_nlink feature if large dir exists
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 08/10] tests: remove pre-generated f_extent_htree image
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 06/10] tests: remove redundant sed filtering
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 05/10] ext2fs: annotate superblock/inode offsets
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 03/10] tests: clean up $DEBUGFS_EXE usage in scripts
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 04/10] tests: replace perl usage with shell built-in
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 00/10] test cleanups and minor improvements
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 02/10] tests: don't unlink test image if SKIP_UNLINK set
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH 01/10] tests: don't use a sparse test file
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH] generic: test XATTR_REPLACE doesn't take the fs down
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: Reg: loical volume file system is getting corrupted after multiple reboots.
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Reg: loical volume file system is getting corrupted after multiple reboots.
  • From: Eric Sandeen <esandeen@xxxxxxxxxx>
• Re: Reg: logical volume file system is getting corrupted after multiple reboots.
  • From: RAJESH DASARI <raajeshdasari@xxxxxxxxx>
• [PATCH 04/15] fscrypt: remove error messages for skcipher_request_alloc() failure
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 03/15] fscrypt: remove unnecessary NULL check when allocating skcipher
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 05/15] fscrypt: remove stale comment from fscrypt_d_revalidate()
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 12/15] fscrypt: remove internal key size constants
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 11/15] fscrypt: remove unnecessary check for non-logon key type
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 01/15] fs, fscrypt: only define ->s_cop when FS_ENCRYPTION is enabled
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 13/15] fscrypt: use a common logging function
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 15/15] fscrypt: only derive the needed portion of the key
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 14/15] fscrypt: separate key lookup from key derivation
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 07/15] fscrypt: don't special-case EOPNOTSUPP from fscrypt_get_encryption_info()
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 10/15] fscrypt: make fscrypt_operations.max_namelen an integer
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 08/15] fscrypt: drop max_namelen check from fname_decrypt()
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 09/15] fscrypt: drop empty name check from fname_decrypt()
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 06/15] fscrypt: don't clear flags on crypto transform
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 02/15] fscrypt: clean up after fscrypt_prepare_lookup() conversions
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH v2 00/15] fscrypt: improved logging and other cleanups
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: Reg: loical volume file system is getting corrupted after multiple reboots.
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Reg: loical volume file system is getting corrupted after multiple reboots.
  • From: RAJESH DASARI <raajeshdasari@xxxxxxxxx>
• Re: [PATCH] ext4: fix bitmap position validation
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: simplify procfs code for seq_file instances V2
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 04/40] proc: introduce proc_create_seq{,_data}
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] ext4: fix bitmap position validation
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: Append and fsync performance in ext4 DAX
  • From: Vijay Chidambaram <vvijay03@xxxxxxxxx>
• Re: Append and fsync performance in ext4 DAX
  • From: Rohan Kadekodi <kadekodirohan@xxxxxxxxx>
• [PATCH] Ext4: tracepoint: fix broken print due to 0%o format
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• [Bug 56821] an ext4 commit ee0906f causes weird disk hangs
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [GIT PULL] ext4 fixes for 4.17-rc3
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: Append and fsync performance in ext4 DAX
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [Bug 199183] Invalid pointer dereference in ext4_xattr_inode_hash when mounting and later operating on a crafted image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH] ext4: add crc32c soft dependency
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Append and fsync performance in ext4 DAX
  • From: Vijay Chidambaram <vvijay03@xxxxxxxxx>
• Re: generic quota vs xfs quota
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: generic quota vs xfs quota
  • From: "cgxu519@xxxxxxx" <cgxu519@xxxxxxx>
• Re: generic quota vs xfs quota
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [PATCH 2/2] ext4: use raw i_version value for ea_inode
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• [PATCH 1/2] ext4: use XATTR_CREATE in ext4_initxattrs()
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• [PATCH 0/2] random ext4 ea_inode fixes
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• generic quota vs xfs quota
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: Boot fail - Cannot load crc32c driver
  • From: James Blanford <jhblanford@xxxxxxxxx>
• Re: Boot fail - Cannot load crc32c driver
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 06/40] proc: introduce proc_create_single{,_data}
  • From: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx>
• Re: simplify procfs code for seq_file instances
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: [PATCH 27/40] rtc/proc: switch to proc_create_single_data
  • From: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx>
• Boot fail - Cannot load crc32c driver
  • From: James Blanford <jhblanford@xxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH 03/40] proc: add a proc_create_reg helper
  • From: Christoph Hellwig <hch@xxxxxx>
• simplify procfs code for seq_file instances V2
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/40] proc: introduce proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/40] ipv{4,6}/udp{,lite}: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/40] proc: introduce proc_create_seq{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/40] proc: simplify proc_register calling conventions
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/40] ipv{4,6}/raw: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 15/40] proc: introduce proc_create_net{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 11/40] ipv6/flowlabel: simplify pid namespace lookup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 13/40] netfilter/x_tables: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 14/40] net: move seq_file_single_net to <linux/seq_file_net.h>
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 12/40] net/kcm: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 16/40] proc: introduce proc_create_net_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/40] ipv{4,6}/ping: simplify proc file creation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 17/40] acpi/battery: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 22/40] ext4: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 21/40] afs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 19/40] megaraid: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 20/40] sg: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 18/40] sgi-gru: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 29/40] hostap: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 23/40] jfs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 30/40] neigh: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 25/40] resource: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 24/40] staging/rtl8192u: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 26/40] drbd: switch to proc_create_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 28/40] bonding: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 27/40] rtc/proc: switch to proc_create_single_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 31/40] netfilter/xt_hashlimit: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 38/40] ide: remove ide_driver_proc_write
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 36/40] isdn: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 34/40] atm: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 33/40] bluetooth: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 40/40] tty: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 37/40] proc: don't detour through seq->private to get the inode
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 35/40] atm: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 39/40] ide: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 32/40] netfilter/x_tables: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/40] ipv{4,6}/tcp: simplify procfs registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/40] net/can: single_open_net needs to be paired with single_release_net
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] ext4: fix bitmap position validation
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH] generic: test XATTR_REPLACE doesn't take the fs down
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] generic: test XATTR_REPLACE doesn't take the fs down
  • From: Eryu Guan <guaneryu@xxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Richard Weinberger <richard@xxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Steven Whitehouse <swhiteho@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Richard Weinberger <richard@xxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: vmalloc with GFP_NOFS
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• vmalloc with GFP_NOFS
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: simplify procfs code for seq_file instances
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] ext4: fix bitmap position validation
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: simplify procfs code for seq_file instances
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 02/39] proc: introduce proc_create_seq{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 03/39] proc: introduce proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: simplify procfs code for seq_file instances
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 03/39] proc: introduce proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 16/39] ipmi: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 26/39] rtc/proc: switch to proc_create_single_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH] ext4: update mtime in ext4_punch_hole even if no blocks are released
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• [PATCH] ext4: fix bitmap position validation
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: ext4_validate_block_bitmap regression on ext3 with stride=X
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• [Bug 199347] buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199347] buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH v3 3/3] ext4: do not update s_last_mounted of a frozen fs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 2/3] ext4: factor out helper ext4_sample_last_mounted()
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 1/3] vfs: add the sb_start_intwrite_trylock() helper
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 0/3] Fix ext4 freeze protection bypass
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3] ext4: handle errors on ext4_commit_super
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v2 3/3] ext4: do not update s_last_mounted of a frozen fs
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 2/3] ext4: factor out helper ext4_sample_last_mounted()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 1/3] vfs: add the sb_start_intwrite_trylock() helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] tests: add raw/e2i/qcow2 image create/install test
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• [PATCH v2 3/3] ext4: do not update s_last_mounted of a frozen fs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 2/3] ext4: factor out helper ext4_sample_last_mounted()
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 1/3] vfs: add the sb_start_intwrite_trylock() helper
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 0/3] Fix ext4 freeze protection bypass
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] ext4: do not update s_last_mounted of a frozen fs
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] ext4: do not update s_last_mounted of a frozen fs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] ext4: do not update s_last_mounted of a frozen fs
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] ext4: do not update s_last_mounted of a frozen fs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 15/39] acpi/battery: simplify procfs code
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2] ext4: handle errors on ext4_commit_super
  • From: Jan Kara <jack@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jan Kara <jack@xxxxxxx>
• Mapping bad sectors to damaged files and metadata with debugfs
  • From: Fedja Beader <fedja@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/2] ext4: wrap error handling and corrupted bitmaps setting
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 2/2] ext4: don't RO for bitmaps error in default
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH] ext4 : fix comments in ext4_swap_extents
  • From: Jan Kara <jack@xxxxxxx>
• Re: simplify procfs code for seq_file instances
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: [PATCH 03/39] proc: introduce proc_create_seq_private
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• ext4_validate_block_bitmap regression on ext3 with stride=X
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: [PATCH 14/39] proc: introduce proc_create_net_single
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: [PATCH 02/39] proc: introduce proc_create_seq{,_data}
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] ext4 : fix comments in ext4_swap_extents
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: WARNING in ext4_set_page_dirty
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2] ext4: handle errors on ext4_commit_super
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] ext4: handle errors on ext4_commit_super
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v3 0/5] dumpe2fs: add JSON output format
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] e2fsprogs: fix Free Software Foundation address
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 16/39] ipmi: simplify procfs code
  • From: Corey Minyard <minyard@xxxxxxx>
• Re: [PATCH] ext4: handle errors on ext4_commit_super
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3 3/5] dumpe2fs: add JSON output of superblock
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4 : fix comments in ext4_swap_extents
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 03/39] proc: introduce proc_create_seq_private
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• [PATCH 2/2] ext4: don't RO for bitmaps error in default
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 1/2] ext4: wrap error handling and corrupted bitmaps setting
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• Re: [PATCH 26/39] rtc/proc: switch to proc_create_single_data
  • From: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx>
• [PATCH 05/39] ipv{4,6}/udp{,lite}: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/39] ipv{4,6}/tcp: simplify procfs registration
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/39] proc: introduce proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• simplify procfs code for seq_file instances
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/39] net/can: single_open_net needs to be paired with single_release_net
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/39] ipv{4,6}/raw: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/39] ipv{4,6}/ping: simplify proc file creation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/39] ipv6/flowlabel: simplify pid namespace lookup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/39] net/kcm: simplify proc registration
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 20/39] afs: simplify procfs code
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 11/39] netfilter/x_tables: simplify ѕeq_file code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 12/39] net: move seq_file_single_net to <linux/seq_file_net.h>
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 15/39] acpi/battery: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 14/39] proc: introduce proc_create_net_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 13/39] proc: introduce proc_create_net{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 21/39] ext4: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 18/39] megaraid: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 20/39] afs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 16/39] ipmi: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 19/39] sg: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 17/39] sgi-gru: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 22/39] jfs: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 27/39] bonding: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 24/39] resource: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 23/39] staging/rtl8192u: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 25/39] drbd: switch to proc_create_single
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 31/39] netfilter/x_tables: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 32/39] bluetooth: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 34/39] atm: switch to proc_create_seq_private
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 33/39] atm: simplify procfs code
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 28/39] hostap: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 29/39] neigh: switch to proc_create_seq_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 35/39] isdn: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 30/39] netfilter/xt_hashlimit: switch to proc_create_{seq,single}_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 36/39] proc: don't detour through seq->private to get the inode
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 39/39] tty: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 38/39] ide: replace ->proc_fops with ->proc_show
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 37/39] ide: remove ide_driver_proc_write
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 26/39] rtc/proc: switch to proc_create_single_data
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/39] proc: introduce proc_create_seq{,_data}
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] ext4: set h_journal if there is a failure starting a reserved handle
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] ext4: set h_journal if there is a failure starting a reserved handle
  • From: Jan Kara <jack@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Eric Sandeen <esandeen@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] libext2fs: try to always use PUNCH_HOLE for unix_discard
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: fsync() errors is unsafe and risks data loss
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH] ext4: set h_journal if there is a failure starting a reserved handle
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH] ext4: set h_journal if there is a failure starting a reserved handle
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 2/2] libext2fs: try to always use PUNCH_HOLE for unix_discard
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 1/2] libext2fs: use ZERO_RANGE before PUNCH_HOLE in unix_zeroout
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• RE: [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: Wang Shilong <wshilong@xxxxxxx>
• Re: [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 4/4] ext4: mark block bitmap corrupted when found
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 3/4] ext4: mark inode bitmap corrupted when found
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 2/4] ext4: new ext4_mark_group_bitmap_corrupted() helper
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 4/4] ext4: mark block bitmap corrupted when found
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• RE: [PATCH] Ext4: Set BBITMAP_CORRUPT_BIT when failing to read the allocation bitmaph
  • From: Wang Shilong <wshilong@xxxxxxx>
• [PATCH 4/4] ext4: mark block bitmap corrupted when found
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 3/4] ext4: mark inode bitmap corrupted when found
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 2/4] ext4: new ext4_mark_group_bitmap_corrupted() helper
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 1/4] ext4: fix wrong return value in ext4_read_inode_bitmap()
  • From: Wang Shilong <wangshilong1991@xxxxxxxxx>
• [PATCH 1/2] libext2fs: use ZERO_RANGE before PUNCH_HOLE in unix_zeroout
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 2/2] libext2fs: try to always use PUNCH_HOLE for unix_discard
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 0/2] e2fprogs: block zero/discard cleanups
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: mke2fs and -E no discard
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• mke2fs and -E no discard
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [Bug 199417] out-of-bound access in ext4_ext_drop_refs() when operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199417] New: out-of-bound access in ext4_ext_drop_refs() when operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 194567] ext4 no longer mounts
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] Ext4: Set BBITMAP_CORRUPT_BIT when failing to read the allocation bitmap
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] Ext4: Set BBITMAP_CORRUPT_BIT when failing to read the allocation bitmaph
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: Filesystem crashes due to pages without buffers
  • From: Gavin Guo <gavin.guo@xxxxxxxxxxxxx>
• Re: [PATCH] fs: ext2: Adding new return type vm_fault_t
  • From: Jan Kara <jack@xxxxxxx>
• [Bug 199403] use-after-free in ext4_ext_remove_space() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• RE: [PATCH] Ext4: Set BBITMAP_CORRUPT_BIT when failing to read the allocation bitmap
  • From: Wang Shilong <wshilong@xxxxxxx>
• [Bug 199403] New: use-after-free in ext4_ext_remove_space() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199403] use-after-free in ext4_ext_remove_space() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [PATCH] fs: ext4: Adding new return type vm_fault_t
  • From: Souptick Joarder <jrdr.linux@xxxxxxxxx>
• [PATCH] fs: ext2: Adding new return type vm_fault_t
  • From: Souptick Joarder <jrdr.linux@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH] Ext4: Set BBITMAP_CORRUPT_BIT when failing to read the allocation bitmap
  • From: Liu Bo <bo.liu@xxxxxxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [Bug 199275] Invalid pointer dereference in ext4_get_group_info() when mounting a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199333] use-after-free in ext4_group_desc_csum() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199321] use-after-free in jbd2_journal_commit_transaction() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH] chattr.1: 'a' and 'i' attribute do not affect existing file descriptors
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: Filesystem crashes due to pages without buffers
  • From: Jan Kara <jack@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: Filesystem crashes due to pages without buffers
  • From: Gavin Guo <gavin.guo@xxxxxxxxxxxxx>
• [PATCH] chattr.1: 'a' and 'i' attribute do not affect existing file descriptors
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC
  • From: Jan Kara <jack@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH] ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• delayed allocation vs WRITE SAME issue
  • From: Nikola Ciprich <nikola.ciprich@xxxxxxxxxxx>
• Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Query about reflink support for EXT4
  • From: "Du, Fan" <fan.du@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH] tests: add raw/e2i/qcow2 image create/install test
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• RE: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: "Bhattacharya, Suparna" <suparna.bhattacharya@xxxxxxx>
• Re: [PATCH] e2fsprogs: fix Free Software Foundation address
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• [Bug 199347] buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199347] buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199347] New: buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] e2fsprogs: fix Free Software Foundation address
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH] ext4: Fix return value for direct io reads at or beyond eof
  • From: Ashish Samant <ashish.samant@xxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx>
• Re: fsync() errors is unsafe and risks data loss
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• fsync() errors is unsafe and risks data loss
  • From: "Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx>
• fsync() errors is unsafe and risks data loss
  • From: "Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH] e2fsprogs: fix Free Software Foundation address
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: Directory unremovable on ext4 no_journal mode
  • From: Jayashree Mohan <jayashree2912@xxxxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [PATCH] ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [Bug 199333] use-after-free in ext4_group_desc_csum() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199337] BUG() in ext4_mb_mark_diskspace_used() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199335] BUG() in ext4_mb_normalize_request when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199301] BUG() in ext4_mark_recovery_complete() can be triggered when mounting crafted image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199277] BUG() in ext4_mb_find_by_goal() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199337] BUG() in ext4_mb_mark_diskspace_used() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199335] BUG() in ext4_mb_normalize_request when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199301] BUG() in ext4_mark_recovery_complete() can be triggered when mounting crafted image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199277] BUG() in ext4_mb_find_by_goal() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199275] Invalid pointer dereference in ext4_get_group_info() when mounting a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199321] use-after-free in jbd2_journal_commit_transaction() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199321] use-after-free in jbd2_journal_commit_transaction() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199337] BUG() in ext4_mb_mark_diskspace_used() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199337] BUG() in ext4_mb_mark_diskspace_used() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199337] New: BUG() in ext4_mb_mark_diskspace_used() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199335] BUG() in ext4_mb_normalize_request when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199335] New: BUG() in ext4_mb_normalize_request when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199333] use-after-free in ext4_group_desc_csum() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199333] use-after-free in ext4_group_desc_csum() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Directory unremovable on ext4 no_journal mode
  • From: Vijay Chidambaram <vijay@xxxxxxxxxxxxx>
• [Bug 199333] New: use-after-free in ext4_group_desc_csum() when mounting and operating on a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: Directory unremovable on ext4 no_journal mode
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: kernel BUG at fs/ext4/mballoc.c:1911!
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: Directory unremovable on ext4 no_journal mode
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Directory unremovable on ext4 no_journal mode
  • From: Jayashree Mohan <jayashree2912@xxxxxxxxx>
• Re: kernel BUG at fs/ext4/mballoc.c:1911!
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] e2fsck: warn if checkinterval and broken_system_clock both set
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• Re: kernel BUG at fs/ext4/mballoc.c:1911!
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [PATCH] e2fsprogs: fix metadata image handling on big endian systems
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] e2fsck: warn if checkinterval and broken_system_clock both set
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [Bug 199321] use-after-free in jbd2_journal_commit_transaction() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199321] New: use-after-free in jbd2_journal_commit_transaction() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: WARNING in ext4_superblock_csum_set
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [PATCH 1/2] libext2fs: add sanity checks for ea_in_inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH 2/2] tests: add new test f_ea_inode_self_ref
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH] fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: [Patch 4/4] Support for obtaining reduced view of a graded file
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [Patch 3/4] Memory-mapped writing and reading of a graded file spanning over two media types
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [Patch 2/4] Controlling block allocation of a file with respect to grading information
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [Patch 4/4] Support for obtaining reduced view of a graded file
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [Patch 3/4] Memory-mapped writing and reading of a graded file spanning over two media types
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [Patch 2/4] Controlling block allocation of a file with respect to grading information
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [Patch 1/4] Support for checking and reading block grade information in kernel
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [Patch 0/4] RFC : Support for data gradation of a single file.
  • From: Sayan Ghosh <sgdgp.2014@xxxxxxxxx>
• [Bug 199301] New: BUG() in ext4_mark_recovery_complete() can be triggered when mounting crafted image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 2/5] dumpe2fs: add JSON output of block groups
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v3 1/5] libsupport: add JSON output helpers
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: BUG: KASAN: use-after-free in bt_for_each+0x1ea/0x29f
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v3 3/5] dumpe2fs: add JSON output of superblock
  • From: Viktor Prutyanov <viktor.prutyanov@xxxxxxxxxxxxx>
• Re: [PATCH v3 2/5] dumpe2fs: add JSON output of block groups
  • From: Viktor Prutyanov <viktor.prutyanov@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/5] libsupport: add JSON output helpers
  • From: Viktor Prutyanov <viktor.prutyanov@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/5] dumpe2fs: add JSON output format
  • From: Viktor Prutyanov <viktor.prutyanov@xxxxxxxxxxxxx>
• [PATCH] e2fsprogs: fix metadata image handling on big endian systems
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• Re: BUG: KASAN: use-after-free in bt_for_each+0x1ea/0x29f
  • From: Jens Axboe <axboe@xxxxxxxxx>
• BUG: KASAN: use-after-free in bt_for_each+0x1ea/0x29f
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [RFC PATCH 33/79] fs/journal: add struct super_block to jbd2_journal_forget() arguments.
  • From: jglisse@xxxxxxxxxx
• [RFC PATCH 34/79] fs/journal: add struct inode to jbd2_journal_revoke() arguments.
  • From: jglisse@xxxxxxxxxx
• [RFC PATCH 69/79] fs/journal: add struct address_space to jbd2_journal_try_to_free_buffers() arguments
  • From: jglisse@xxxxxxxxxx
• [User_question] Unexpected behaviour on data=journal commit=large_number mount options
  • From: Lipusz Bálint <lipusz.balint@xxxxxxxxxxx>
• [GIT PULL] ext4 updates for 4.17
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Use @AR@ instead of hardcoded 'ar'
  • From: bjornpagen@xxxxxxxxx
• [Bug 199277] BUG() in ext4_mb_find_by_goal() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199277] New: BUG() in ext4_mb_find_by_goal() when mounting and operating a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• [Bug 199275] New: Invalid pointer dereference in ext4_get_group_info() when mounting a crafted ext4 image
  • From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH v8 05/18] ext4, dax: introduce ext4_dax_aops
  • From: Jan Kara <jack@xxxxxxx>
• Re: e2fsprogs-1.44.1 self-tests f_bigalloc_badinode and f_bigalloc_orphan_list fail for me
  • From: Somchai Smythe <buraphalinuxserver@xxxxxxxxx>
• Re: [PATCH] f2fs: reserve bits for fs-verity
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH] f2fs: reserve bits for fs-verity
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] f2fs: reserve bits for fs-verity
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• WARNING in ext4_superblock_csum_set
  • From: syzbot <syzbot+f3b1a2c79758f3eec76c@xxxxxxxxxxxxxxxxxxxxxxxxx>
• KASAN: use-after-free Write in __ext4_expand_extra_isize
  • From: syzbot <syzbot+f584efa0ac7213c226b7@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: kernel BUG at fs/ext4/extents.c:LINE!
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• kernel BUG at fs/ext4/extents.c:LINE!
  • From: syzbot <syzbot+06c885be0edcdaeab40c@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] ext4: always initialize the crc32c checksum driver
  • From: Nikolay Borisov <n.borisov.lkml@xxxxxxxxx>
• WARNING in ext4_set_page_dirty
  • From: syzbot <syzbot+9a44753ac327c557796a@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: KASAN: slab-out-of-bounds Read in __ext4_check_dir_entry
  • From: syzbot <syzbot+730517f1d3fbe54a17c7@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: KASAN: slab-out-of-bounds Read in __ext4_check_dir_entry
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: KASAN: use-after-free Read in __ext4_check_dir_entry
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• KASAN: use-after-free Read in __ext4_check_dir_entry
  • From: syzbot <syzbot+1236ce66f79263e8a862@xxxxxxxxxxxxxxxxxxxxxxxxx>
• KASAN: slab-out-of-bounds Read in __ext4_check_dir_entry
  • From: syzbot <syzbot+730517f1d3fbe54a17c7@xxxxxxxxxxxxxxxxxxxxxxxxx>
• KASAN: slab-out-of-bounds Read in __ext4_check_dir_entry
  • From: syzbot <syzbot+730517f1d3fbe54a17c7@xxxxxxxxxxxxxxxxxxxxxxxxx>
• KASAN: use-after-free Read in __ext4_check_dir_entry
  • From: syzbot <syzbot+1236ce66f79263e8a862@xxxxxxxxxxxxxxxxxxxxxxxxx>