Linux Overlay Filesystem development
 help / color / mirror / Atom feed
 messages from 2026-05-16 00:53:07 to 2026-06-05 10:17:03 UTC [more...]

[PATCH] backing-file: fix backing_file_open() kerneldoc parameter
 2026-06-05 10:16 UTC  (4+ messages)
` [PATCH v2] "

[syzbot] [overlayfs?] [ext4?] possible deadlock in lock_two_nondirectories (2)
 2026-06-04 21:33 UTC 

[PATCH v10 00/22] fs-verity support for XFS with post EOF merkle tree
 2026-06-04 12:08 UTC  (42+ messages)
` [PATCH v10 01/22] fsverity: report validation errors through fserror to fsnotify
` [PATCH v10 02/22] fsverity: expose ensure_fsverity_info()
` [PATCH v10 03/22] ovl: use core fsverity ensure info interface
` [PATCH v10 04/22] fsverity: generate and store zero-block hash
` [PATCH v10 05/22] fsverity: pass digest size and hash of the all-zeroes block to ->write
` [PATCH v10 06/22] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity
` [PATCH v10 07/22] iomap: introduce IOMAP_F_FSVERITY and teach writeback to handle fsverity
` [PATCH v10 08/22] iomap: teach iomap to read files with fsverity
` [PATCH v10 09/22] iomap: introduce iomap_fsverity_write() for writing fsverity metadata
` [PATCH v10 10/22] xfs: introduce fsverity on-disk changes
` [PATCH v10 11/22] xfs: initialize fs-verity on file open
` [PATCH v10 12/22] xfs: don't allow to enable DAX on fs-verity sealed inode
` [PATCH v10 13/22] xfs: disable direct read path for fs-verity files
` [PATCH v10 14/22] xfs: handle fsverity I/O in write/read path
` [PATCH v10 15/22] xfs: use read ioend for fsverity data verification
` [PATCH v10 16/22] xfs: add fs-verity support
` [PATCH v10 17/22] xfs: remove unwritten extents after preallocations in fsverity metadata
` [PATCH v10 18/22] xfs: add fs-verity ioctls
` [PATCH v10 19/22] xfs: advertise fs-verity being available on filesystem
` [PATCH v10 20/22] xfs: check and repair the verity inode flag state
` [PATCH v10 21/22] xfs: introduce health state for corrupted fsverity metadata
` [PATCH v10 22/22] xfs: enable ro-compat fs-verity flag

[syzbot] [overlayfs?] possible deadlock in ovl_copy_up_flags (2)
 2026-05-29  9:34 UTC 

[PATCH v2 00/21] fuse: extend passthrough to inode operations
 2026-05-19 22:07 UTC  (45+ messages)
` [PATCH v2 02/21] fuse: prepare for passthrough of "
` [PATCH v2 06/21] fuse: implement passthrough for getattr/statx
` [PATCH v2 08/21] fuse: handle zero ops_mask in FUSE_DEV_IOC_BACKING_OPEN
` [PATCH v2 09/21] fuse: handle partial io passthrough for read/write, splice, and mmap
` [PATCH v2 12/21] fuse: add struct fuse_entry2_out and helpers for extended entry replies
    `  "
` [PATCH v2 13/21] fuse: add passthrough lookup
` [PATCH v2 16/21] fuse: allow backing_id=0 in open to inherit inode's backing file
` [PATCH v2 17/21] backing-inode: add backing_inode_copyattr()
` [PATCH v2 18/21] backing-inode: add backing_inode_setattr()
` [PATCH v2 19/21] fuse: add passthrough setattr
` [PATCH v2 20/21] fuse: use passthrough getattr in setattr suid/sgid handling
` [PATCH v2 21/21] docs: fuse: document extended passthrough (FUSE_PASSTHROUGH_INO)

[PATCH] err_ptr.h: introduce ERR_PTR_SAFE()
 2026-05-18 14:51 UTC  (15+ messages)

[PATCH v2] ovl: keep err zero after successful ovl_cache_get()
 2026-05-18 12:57 UTC  (2+ messages)


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox