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-2546 Lustre <p>== sanity test 140: Check reasonable stack depth (shouldn't LBUG) ==================================== 17:37:58 (1356658678)<br/> The symlink depth = 40<br/> sanity test_140: @@@@@@ FAIL: Invalid symlink depth</p> <p>The test_logs are uploaded as 'sanity.test_140.tgz'.<br/> The test was run on service331.</p> server: 2.1.3-1nasS, centos 6.3, 2.6.32_279.2.1.el6<br/> client: 2.3.0-1nasC, sles11sp2, 3.0.42_0.7.3<br/> 1 mds, 2 oss, 2 clients. LU-2546

test: sanity FAIL: test_140 Invalid symlink depth

Bug Minor Resolved Duplicate Nathaniel Clark Jay Lan sles11 Fri, 28 Dec 2012 18:45:45 +0000 Thu, 3 Jan 2013 12:30:35 +0000 Thu, 3 Jan 2013 12:30:35 +0000 Lustre 2.3.0 0 3 <p>Nathaniel</p> <p>I think that you have worked in this area recently so could you please comment on this one?</p> <p>Thanks</p> <p>Peter</p> <p>I think this is due to the 3.6 kernel in sles11 sp2 having the commit b356379a020bb7197603118bb1cbc903963aa198. This restructures the handling of trailing symlinks in pathnames. They are now recognized and handled as iterative, not as nested and recursive. Iterative sequences of symlinks have the much higher limit of 40, not MAX_NESTED_LINKS (8) in vfs code.<br/> Either the test can be changed to accept 40 as a valid loop count, or the test can be changed to create symlink sequences that will be recognized as recursive in even the newest kernel versions of vfs code.</p> <p>sorry, got a bit confused about kernel versions. It's 3.0 kernel in sles11 sp2, not 3.6. My point about the commit changing symlink handling is valid anyway. It's there in 3.0 too.</p> <p>Do you have a link to the commit, Bob? Thanks!</p> <p>This is the link I found: <a href="http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=b356379a020bb7197603118bb1cbc903963aa198" class="external-link" target="_blank" rel="nofollow noopener">http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=b356379a020bb7197603118bb1cbc903963aa198</a></p> <p>It appears to be one of a series of related commits revising symlink handling in vfs path walk code from ~3/2011</p> <p>This was fixed in master by bug <a href="https://jira.whamcloud.com/browse/LU-2020" title="sanity 140 should allow 40 consecutive symlinks" class="issue-link" data-issue-key="LU-2020"><del>LU-2020</del></a></p> <p>The following change can be cleanly cherry-picked onto both 2.1 and 2.3<br/> <a href="http://review.whamcloud.com/4079" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4079</a></p> <p>Thanks, Nathaniel. Test_140 passed with this patch.</p> Duplicate LU-2020 Development Rank 1|hzvedj: Rank (Obsolete) 5969 Severity