https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-16812 Lustre <p>On osd we don't check for new inode size before ldiskfs_truncate(), we could overflow the block counters in ext4_es_remove_extent().</p> LU-16812

ldiskfs osd_punch() should check new inode size does not exceed maximum size

Improvement Minor Open Unresolved Dongyang Li Dongyang Li Wed, 10 May 2023 00:12:42 +0000 Thu, 29 Jun 2023 22:04:06 +0000 0 3 <p>"Li Dongyang &lt;dongyangli@ddn.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/50898" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/50898</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16812" title="ldiskfs osd_punch() should check new inode size does not exceed maximum size" class="issue-link" data-issue-key="LU-16812">LU-16812</a> osd-ldiskfs: check inode new size before truncate<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: b68d6ea613477d39ecdadc8d8131554a1a5bf27d</p> <p>It seems kind of wrong that we allow <b>creating</b> a file with size=MAX_LFS_FILESIZE but then we cannot open it? It would probably make more sense that we would return an error for the truncate operation for files larger than <tt>LOV_MAX_STRIPE_COUNT * ocd_maxbytes</tt> at the client.</p> <p>Something like this is already in <a href="https://review.whamcloud.com/41365" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/41365</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-14384" title="data &quot;written&quot; to last stripe of very large ldiskfs object can not be &quot;read&quot;" class="issue-link" data-issue-key="LU-14384">LU-14384</a> tests: write and read last object stripe</tt>"</p> Duplicate LU-14384 Related LU-16537 Development Rank 1|i03kwf: Rank (Obsolete) 9223372036854775807 Severity