回合上游社区补丁,补丁数量：3

【是否新引入rpm包，是否进行了安全编译选项扫描】

否

【定位分析】

<table><tbody><tr><td>软件包</td><td>CommitId</td><td>描述</td><td>说明</td></tr><tr><td>e2fsprogs</td><td>b31d5b582b4189a0ed27bced22276dd3f68c50a7</td><td>e2fsprogs: modify dumpe2fs to report free block ranges for bigalloc
dumpe2fs has never been modified to correctly report block rangescorresponding to free clusters in block allocation bitmaps from bigallocfile systems. Rather than reporting block ranges covering all theblocks in free clusters found in a block bitmap, it either reports justthe first block number in a cluster for a single free cluster, or arange beginning with the first block number in the first cluster in aseries of free clusters, and ending with the first block number in thelast cluster in that series.
This behavior causes xfstest shared/298 to fail when run on a bigallocfile system with a 1k block size. The test uses dumpe2fs to collecta list of the blocks freed when files are deleted from a file system.When the test deletes a file containing blocks located after the firstblock in the last cluster in a series of clusters, dumpe2fs does notreport those blocks as free per the test's expectations.
Modify dumpe2fs to report full block ranges for free clusters. At thesame time, fix a small bug causing unnecessary !in_use retests whileiterating over a block bitmap.

Add a test for the commit e2fsck: fix handling of a invalid symlinkin an inline_data directory

If there is an inline directory that contains a directory entry to aninvalid symlink, and that invalid symlink is the portion of the inlinedirectory stored in an xattr portion of the inode, this can result ina buffer overrun.
When check_dir_block.
This commit fixes this by using the original cd-&gt;buf instead of buf,since it can get modified when handling inline directories.
Fixes: 0ac4b3973f31 Signed-off-by: Theodore Ts'o</td><td>修复e2fsck在处理inline目录包含无效链接的情况下可能存在的缓冲区溢出问题</td></tr></tbody></table>

【对外部是否有影响】

否

src-openEuler/e2fsprogs
关闭

内容风险标识

评论 (1)

src-openEuler/e2fsprogs关闭 .gitee-modal { width: 500px !important; }

内容风险标识