ocfs2-allow-xattr-bucket-entries-to-span-multiple-blocks.patch removed from -mm tree
The quilt patch titled
Subject: ocfs2: allow xattr bucket entries to span multiple blocks
has been removed from the -mm tree. Its filename was
ocfs2-allow-xattr-bucket-entries-to-span-multiple-blocks.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Joseph Qi <[email protected]>
Subject: ocfs2: allow xattr bucket entries to span multiple blocks
Date: Thu, 3 Sep 2026 21:13:12 +0800
Patch series "ocfs2: xattr bucket validation fixes", v2.
This series fixes two problems around xattr bucket validation.
Patch 1 fixes a false-corruption failure on blocksize-512 volumes: the bucket validator limited the entry array to the first bucket block while the write path stores entries across the whole 4096-byte bucket region, so a legitimately written, fsck-clean bucket could be rejected and force the filesystem read-only. It also adds an alignment check on the bucket block number, since the entry array is accessed as one contiguous region and a corrupted xattr tree could otherwise point a bucket at blocks straddling a page boundary.
Patch 2 converts two mlog_bug_on_msg() checks in the bucket defrag path to ocfs2_error() returns, so that a corrupt bucket holding overlapping entries or an inflated xh_free_start marks the filesystem read-only and fails the setxattr instead of panicking the kernel.
Both patches have been tested in QEMU: the blocksize-512 reproducer (40 xattrs with 100-byte values, previously failing with "entry count 32 exceeds maximum 31") now passes with a clean fsck.ocfs2 result, and the ocfs2 testsuite xattr tests pass 48/48 across blocksize combinations.
This patch (of 2):
ocfs2_validate_xattr_bucket() limits the entry array to the first bucket block, but the write path stores entries across the whole OCFS2_XATTR_BUCKET_SIZE region. With 512-byte blocks a bucket spans eight blocks, and a bucket filled with small xattrs places its last entries past offset 512. Reading such a bucket back errors out:
OCFS2: ERROR (device loop0): ocfs2_validate_xattr_bucket: Invalid xattr bucket 86072: entry count 32 exceeds maximum 31 On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
This is reproducible by setting ~33 xattrs with 100-byte values on a file on a blocksize-512 volume; fsck.ocfs2 reports the resulting image clean.
Check the entry count against the full bucket region instead. The per-block bounds checks for names and values stay as they are, since ocfs2_bucket_align_free_start() keeps each name+value pair within a single block.
The entry array is one contiguous region, so a bucket from a corrupted xattr tree whose first block is not aligned to OCFS2_XATTR_BUCKET_SIZE could straddle a page and make the validation loop read out of bounds. Buckets allocated within clusters are always aligned, so reject any other block number while validating.
---
fs/ocfs2/xattr.c | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-)
fs/ocfs2/xattr.c renamed from fs/ocfs2/xattr.c~ocfs2-allow-xattr-bucket-entries-to-span-multiple-blocks +20 -1
@@ -1150,11 +1150,30 @@ static int ocfs2_validate_xattr_bucket(sstruct ocfs2_xattr_header *xh =bucket_xh (bucket);u16 xattr_count =le16_to_cpu (xh->xh_count);size_t region_size = (size_t )sb->s_blocksize * bucket->bu_blocks; -size_t entries_limit = sb->s_blocksize; +/* +* The entry array grows up from the header across the whole +* bucket region, so it may extend beyond the first bucket block +* when the blocksize is smaller than OCFS2_XATTR_BUCKET_SIZE. +* Name/value pairs, however, always live within a single block. +*/ +size_t entries_limit = region_size;size_t nv_limit = sb->s_blocksize;size_t max_entries;int i, ret; +/* +* The entry array is one contiguous region that may span the +* bucket's buffer_heads. Buckets are allocated within clusters, +* so their first block is always aligned to +* OCFS2_XATTR_BUCKET_SIZE and the whole bucket fits in one page. +* A corrupted xattr tree can point a bucket at blocks straddling +* a page, so reject it before touching the entry array. +*/ +if (blkno & (bucket->bu_blocks -1 )) +return ocfs2_error (sb, +"Invalid xattr bucket %llu: unaligned block number\n" , + (unsigned long long )blkno); +if (region_size <sizeof (*xh)) return ocfs2_error(sb, "Invalid xattr bucket %llu: region size %zu is too small\n",
_
Patches currently in -mm which might be from [email protected] are
ocfs2-retain-all-security-xattrs-during-inode-creation.patch ocfs2-restore-erange-check-in-ocfs2_xattr_tree_list_index_block.patch ocfs2-fix-possible-deadlock-between-nfs_sync_rwlock-and-fs_reclaim.patch