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-660 Lustre <p>some OSC procfs functions use osc_device which is lu_device. It must be linked with obd_device given not NULL obd-&gt;obd_lu_dev. It is done at the end of obd_setup() function. But procfs files are accessible before that because obd procfs data is initialized inside OSC o_setup. Solution can be artificial setting obd-&gt;obd_lu_dev to the osc_device inside osc_setup().</p> <p>The same problem exists during obd_cleanup - first it free osc_device therefore obd-&gt;obd_lu_dev is NULL again but OBD procfs data is cleaned up after that in osc_cleanup(). Solution can be moving lprocfs_obd_cleanup to the precleanup function.</p> LU-660

OSC procfs data is accessible when OSC is not ready to process it

Bug Minor Resolved Low Priority WC Triage Mikhail Pershin Mon, 5 Sep 2011 03:21:05 +0000 Wed, 11 Oct 2017 19:58:03 +0000 Wed, 11 Oct 2017 19:58:03 +0000 Lustre 2.1.0 0 1 <p>forgot to mention - this issue can be seen during test 57 from recovery-small. There is such code:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">test_57_helper() { # no oscs means no client or mdt <span class="code-keyword">while</span> lctl get_param osc.*.* &gt; /dev/<span class="code-keyword">null</span> 2&gt;&amp;1; <span class="code-keyword">do</span> : # loop until proc file is removed done } </pre> </div></div> <p>this scans OSC procfs data in cycle and may sneak to that window when obb_lu_dev is NULL</p> <p>Hi Mike, I think <a href="https://jira.whamcloud.com/browse/LU-106" title="unable to handle kernel paging request in lprocfs_stats_collect()" class="issue-link" data-issue-key="LU-106"><del>LU-106</del></a> has covered this, and you're one of an inspector also.</p> <p>Lai, yes, it will cover problems during umount, but it may exist during setup also. For example, in so OSC procfs functions use not obd_device but osc_device. It is taken from OBD throught obd-&gt;obd_lu_dev, the problem is that obd_setup() calls osc_init() before set obd_lu_dev, so there is short window when proc data is accessible but obd_lu_dev is NULL. I would suggest to set obd_lu_dev right inside osc_init() but not sure is it safe or not. Need to look at that code closely</p> Development Rank 1|hzw3af: Rank (Obsolete) 10617 Severity