Description
In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb In clustermd, separate write-intent-bitmaps are used for each cluster node: 0 4k 8k 12k ------------------------------------------------------------------- | idle | md super | bm super [0] + bits | | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] | | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits | | bm bits [3, contd] | | | So in node 1, pg_index in __write_sb_page() could equal to bitmap->storage.file_pages. Then bitmap_limit will be calculated to 0. md_super_write() will be called with 0 size. That means the first 4k sb area of node 1 will never be updated through filemap_write_page(). This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize. Here use (pg_index % bitmap->storage.file_pages) to make calculation of bitmap_limit correct.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
655cc01889fa9b65441922565cddee64af49e6d6 to < 5eaf57fdfa37c869e61e9908e03edd707f9145b8affectedab99a87542f194f28e2364a42afbf9fb48b1c724 to < 60196f92bbc7901eb5cfa5d456651b87ea50a4a3affectedab99a87542f194f28e2364a42afbf9fb48b1c724 to < bc3a9788961631359527763d7e1fcf26554c7cb1affectedab99a87542f194f28e2364a42afbf9fb48b1c724 to < 6130825f34d41718c98a9b1504a79a23e379701eaffected5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2affected6.6.44 to < 6.6.157affected6.10.3 to < 6.11affected
Linux Linux
Default version status: affected
6.11affected0 to < 6.11unaffected6.6.157 to ≤ 6.6.*unaffected6.12.46 to ≤ 6.12.*unaffected6.14.2 to ≤ 6.14.*unaffected6.15 to ≤ *unaffected