messages from 2019-05-07 07:48:26 to 2019-05-16 08:16:43 UTC [more...]
[PATCH 00/17] Add support for SHA-256 checksums
2019-05-16 8:16 UTC (51+ messages)
` [PATCH 01/17] btrfs: use btrfs_csum_data() instead of directly calling crc32c
` [PATCH 02/17] btrfs: resurrect btrfs_crc32c()
` [PATCH 03/17] btrfs: use btrfs_crc32c() instead of btrfs_extref_hash()
` [PATCH 04/17] btrfs: use btrfs_crc32c() instead of btrfs_name_hash()
` [PATCH 05/17] btrfs: don't assume ordered sums to be 4 bytes
` [PATCH 06/17] btrfs: dont assume compressed_bio "
` [PATCH 07/17] btrfs: use btrfs_crc32c{,_final}() in for free space cache
` [PATCH 08/17] btrfs: format checksums according to type for printing
` [PATCH 09/17] btrfs: add common checksum type validation
` [PATCH 10/17] btrfs: check for supported superblock checksum type before checksum validation
` [PATCH 11/17] btrfs: Simplify btrfs_check_super_csum() and get rid of size assumptions
` [PATCH 12/17] btrfs: add boilerplate code for directly including the crypto framework
` [PATCH 13/17] btrfs: pass in an fs_info to btrfs_csum_{data,final}()
` [PATCH 14/17] btrfs: directly call into crypto framework for checsumming
` [PATCH 15/17] btrfs: remove assumption about csum type form btrfs_csum_{data,final}()
` [PATCH 16/17] btrfs: remove assumption about csum type form btrfs_print_data_csum_error()
` [PATCH 17/17] btrfs: add sha256 as another checksum algorithm
[PATCH] fstests: generic, fsync fuzz tester with fsstress
2019-05-16 8:09 UTC (3+ messages)
[PATCH 2/3] Btrfs: fix wrong ctime and mtime of a directory after log replay
2019-05-16 7:09 UTC (2+ messages)
[PATCH 1/3] Btrfs: fix fsync not persisting changed attributes of a directory
2019-05-16 7:03 UTC (2+ messages)
storm-of-soft-lockups: spinlocks running on all cores, preventing forward progress (4.14- to 5.0+)
2019-05-16 6:57 UTC (2+ messages)
[PATCH v6] btrfs-progs: dump-tree: add noscan option
2019-05-16 2:10 UTC
[PATCH v5 RESEND] btrfs-progs: dump-tree: add noscan option
2019-05-16 2:10 UTC (5+ messages)
WARNING at fs/btrfs/delayed-ref.c:296 btrfs_merge_delayed_refs+0x3dc/0x410 (new on 5.0.4, not in 5.0.3)
2019-05-15 20:27 UTC (3+ messages)
` btrfs + KASAN + SLAB + lvmcache + rsync + kernel 5.0 = page allocation failure and/or OOM kills (solved...ish)
[PATCH] btrfs: fiemap: preallocate ulists for btrfs_check_shared
2019-05-15 17:24 UTC (4+ messages)
[PATCH] Btrfs: avoid fallback to transaction commit during fsync of files with holes
2019-05-15 17:08 UTC (3+ messages)
[PATCH 0/8] Misc improvements to dev-replace code
2019-05-15 16:52 UTC (16+ messages)
` [PATCH 1/8] btrfs: Don't opencode sync_blockdev in btrfs_init_dev_replace_tgtdev
` [PATCH 2/8] btrfs: Reduce critical section "
` [PATCH 3/8] btrfs: Remove impossible WARN_ON
` [PATCH 4/8] btrfs: Ensure btrfs_init_dev_replace_tgtdev sees up to date values
` [PATCH 5/8] btrfs: Streamline replace sem unlock in btrfs_dev_replace_start
` [PATCH 6/8] btrfs: Explicitly reserve space for devreplace item
` [PATCH 7/8] btrfs: Ensure replaced device doesn't have pending chunk allocation
` [PATCH 8/8] btrfs: Remove redundant assignment of tgt_device->commit_total_bytes
[PATCH 3/3] Btrfs: fix race updating log root item during fsync
2019-05-15 15:03 UTC
[PATCH v3] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation
2019-05-15 14:56 UTC (5+ messages)
[PATCH 1/2] btrfs-progs: check: run delayed refs after writing out dirty block groups
2019-05-15 14:45 UTC (5+ messages)
[PATCH 1/2] btrfs-progs: scan: cleanup, return errno when we have one
2019-05-15 14:29 UTC (4+ messages)
` [PATCH 2/2] btrfs-progs: scan: pass blkid_get_cache error code
[PATCH] Btrfs-progs: receive, add debug information to write and clone commands
2019-05-15 14:21 UTC (2+ messages)
[PATCH] btrfs: extent-tree: Refactor add_pinned_bytes() to add|sub_pinned_bytes()
2019-05-15 11:37 UTC (2+ messages)
[PATCH] btrfs: extent-tree: Fix a bug that btrfs is unable to add pinned bytes
2019-05-14 23:08 UTC (4+ messages)
[PATCH V9] Btrfs: enhance raid1/10 balance heuristic
2019-05-14 21:11 UTC (5+ messages)
[PATCH v3 0/3] btrfs-progs: provide command to dump checksums
2019-05-14 14:00 UTC (6+ messages)
` [PATCH v3 1/3] btrfs-progs: factor out super_block reading from load_and_dump_sb
` [PATCH v3.1 "
` [PATCH v3 2/3] btrfs-progs: add 'btrfs inspect-internal csum-dump' command
` [PATCH v3 3/3] btrfs-progs: completion: wire-up dump-csum
[PATCH] Btrfs: fix race between send and deduplication that lead to failures and crashes
2019-05-13 22:06 UTC (9+ messages)
` [PATCH v2] "
[PATCH] Btrfs: prevent send failures and crashes due to concurrent relocation
2019-05-13 18:00 UTC (6+ messages)
[PATCH 0/2] Fix kobject error path memleaks
2019-05-13 17:47 UTC (9+ messages)
` [PATCH 1/2] fs: btrfs: Fix error path kobject memory leak
` [PATCH 2/2] fs: btrfs: Don't leak memory when failing add fsid
[PATCH 0/3] btrfs-progs: Handle error properly in btrfs_commit_transaction()
2019-05-13 13:55 UTC (2+ messages)
[PATCH AUTOSEL 5.0 92/99] btrfs: Switch memory allocations in async csum calculation path to kvmalloc
2019-05-13 13:37 UTC (3+ messages)
[PATCH v2 0/3] btrfs-progs: provide command to dump checksums
2019-05-13 13:05 UTC (5+ messages)
` [PATCH v2 1/3] btrfs-progs: factor out super_block reading from load_and_dump_sb
` [PATCH v2 2/3] btrfs-progs: add 'btrfs inspect-internal csum-dump' command
Howto read btrfs stack trace?
2019-05-13 12:37 UTC (5+ messages)
interest in post-mortem examination of a BTRFS system and improving the btrfs-code?
2019-05-13 12:19 UTC (20+ messages)
Bad tree block start, can't mount but data seems intact
2019-05-12 19:46 UTC
Btrfs Samba and Quotas
2019-05-12 12:45 UTC (3+ messages)
` Re[2]: "
[PATCH 0/3] readmirror feature
2019-05-11 15:24 UTC (2+ messages)
reading/writing btrfs volume regularly freezes system
2019-05-11 11:21 UTC (4+ messages)
[PATCH 12/18] btrfs: allow MAP_SYNC mmap
2019-05-10 15:59 UTC (4+ messages)
` [PATCH for-goldwyn] btrfs: disallow MAP_SYNC outside of DAX mounts
[PATCH v2 0/3] Ordered extent flushing refactor
2019-05-10 12:05 UTC (5+ messages)
` [PATCH v2 3/3] btrfs: Always use a cached extent_state in btrfs_lock_and_flush_ordered_range
[PATCH] btrfs: Return EAGAIN if we can't start no snpashot write in check_can_nocow
2019-05-10 12:03 UTC (2+ messages)
[PATCH] btrfs: Add comments on locking of several device-related fields
2019-05-10 11:51 UTC (6+ messages)
` [PATCH v2] "
Hibernation into swap file
2019-05-09 17:04 UTC (6+ messages)
[PATCH] btrfs: run delayed iput at unlink time
2019-05-09 14:27 UTC (4+ messages)
[PATCH] btrfs: extent-io: Remove the incorrect comment on RO fs when btrfs_run_delalloc_range() fails
2019-05-09 13:14 UTC (3+ messages)
[PATCH 1/2] btrfs: extent-tree: Add lockdep assert when updating space info
2019-05-09 10:42 UTC (3+ messages)
` [PATCH 2/2] btrfs: extent-tree: Add trace events for space info numbers update
[PATCH] Btrfs: do not abort transaction at btrfs_update_root() after failure to COW path
2019-05-09 9:26 UTC (2+ messages)
[PATCH v4] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs
2019-05-08 17:02 UTC (2+ messages)
[PATCH v3] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs
2019-05-08 13:40 UTC (2+ messages)
[PATCH v2] fstests: generic: Test if we can still do operations which don't take extra data space on a fs without data space
2019-05-08 10:44 UTC (3+ messages)
[PATCH] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation
2019-05-08 8:59 UTC (2+ messages)
[PATCH] fstests: generic: Test if fsync will fail after NOCOW write and reflink
2019-05-08 8:43 UTC (2+ messages)
[PATCH 2/2] Btrfs: teach tree-checker to detect file extent items with overlapping ranges
2019-05-08 8:00 UTC (3+ messages)
[GIT PULL] Btrfs updates for 5.2
2019-05-07 19:55 UTC (2+ messages)
[PATCH 1/2] Btrfs: fix race between ranged fsync and writeback of adjacent ranges
2019-05-07 19:31 UTC (4+ messages)
[PATCH RFC] btrfs: reflink: Flush before reflink any extent to prevent NOCOW write falling back to CoW without data reservation
2019-05-07 17:36 UTC (10+ messages)
can I change NAME_MAX limit
2019-05-07 10:57 UTC (2+ messages)
page: next (older) | prev (newer) | latest
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).