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-3353 Lustre <p>We started getting many of these messages on our 2.1.4 MDS. The timing corresponded with client reconnection problems, i.e. <a href="https://jira.whamcloud.com/browse/LU-1934" title="still busy with active RPCs for days" class="issue-link" data-issue-key="LU-1934"><del>LU-1934</del></a>.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>2013-05-15 15:54:44 Lustre: lsd-MDT0000: Client a22a8a8a-754a-c1ab-859d-eda3c476a27d (at 192.168.112.1@o2ib6) reconnecting 2013-05-15 15:54:44 Lustre: Skipped 143 previous similar messages 2013-05-15 15:54:44 Lustre: lsd-MDT0000: Client a22a8a8a-754a-c1ab-859d-eda3c476a27d (at 192.168.112.1@o2ib6) refused reconnection, still busy with 1 active RPCs 2013-05-15 15:54:44 Lustre: Skipped 143 previous similar messages 2013-05-15 15:56:31 LustreError: 5204:0:(sec.c:385:import_sec_validate_get()) import ffff88061d4a7000 (FULL) with no sec 2013-05-15 15:56:31 LustreError: 5204:0:(sec.c:385:import_sec_validate_get()) Skipped 2399 previous similar messages </pre> </div></div> <p>The MDS was just rebooted without a crash dump so, unless this reproduces, we won't be able to tell much about the imports in question.</p> LU-3353

import_sec_validate_get() import ffff88061d4a7000 (FULL) with no sec

Bug Critical Resolved Fixed Niu Yawei Ned Bass llnl Wed, 15 May 2013 23:28:39 +0000 Thu, 14 Jun 2018 21:41:38 +0000 Wed, 11 Feb 2015 17:14:46 +0000 Lustre 2.1.4 Lustre 2.7.0 Lustre 2.5.5 0 11 <p>Niu</p> <p>Could you please comment on this one?</p> <p>Thanks</p> <p>Peter</p> <p>I'm not familiar with lustre security. Ned, do you know what kind of security flavor was specified for the cluster? Thanks.</p> <p>I don't think we specify any security flavor, so it should be null.</p> <p>This looks like a race: when the export is being destroyed, it'll kill the imp_sec on it's reverse import, and in the meantime, there is still some inflight requests on it's reverse import, which triggered the error message of "import_sec_validate_get() import ... with no sec". I don't think it could cause any serious damange so far.</p> <p>it's bug in reconnect logic, we are disconnect an rev import but lack an invalidate list of requests on import.<br/> in that case lock cancel callback may still in sending queue with waiting sec context state and don't killed at all but it's need some network flap also.<br/> i have crash dump with such situation.</p> <p>the core reason for the race condition, where a reverse import is destroyed while there are client bound requests in flight, is when a client reconnects. The area in the code where I could identify is in:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">target_handle_connect() { ... spin_lock(&amp;export-&gt;exp_lock); <span class="code-keyword">if</span> (export-&gt;exp_imp_reverse != NULL) <span class="code-comment">/* destroyed <span class="code-keyword">import</span> can be still referenced in ctxt */</span> tmp_imp = export-&gt;exp_imp_reverse; export-&gt;exp_imp_reverse = revimp; spin_unlock(&amp;export-&gt;exp_lock); ... } </pre> </div></div> <p>later on the tmp_imp is destroyed.</p> <p>While it's being destroyed import_sec_validate_get() could be getting called, and the security could've been cleared already.</p> <p>the suggested solution is to suppress the error message in import_sec_validate_get() if the import is being destroyed</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/10200/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10200/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-3353" title="import_sec_validate_get() import ffff88061d4a7000 (FULL) with no sec" class="issue-link" data-issue-key="LU-3353"><del>LU-3353</del></a> ptlrpc: Suppress error message when imp_sec is freed<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: edf6116663724467207422dcc0c6120320055cac</p> <p>Can a patch be landed for 2.5? We still see this on our production clusters, and it would be nice to reduce unneeded log messages.</p> <p>James Simmons (uja.ornl@gmail.com) uploaded a new patch: <a href="http://review.whamcloud.com/13254" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13254</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-3353" title="import_sec_validate_get() import ffff88061d4a7000 (FULL) with no sec" class="issue-link" data-issue-key="LU-3353"><del>LU-3353</del></a> ptlrpc: Suppress error message when imp_sec is freed<br/> Project: fs/lustre-release<br/> Branch: b2_5<br/> Current Patch Set: 1<br/> Commit: 2d6469ec1a1ffc820cb7d5a6e18006a4e41bad19</p> <p>Patch landed to Master. Patch for other branches will be tracked outside of this ticket.</p> Related LU-7030 Development Rank 1|hzvr53: Rank (Obsolete) 8288 Severity