<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:44:25 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-11501] use the dcache properly with .lustre/fid</title>
                <link>https://jira.whamcloud.com/browse/LU-11501</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;While addressing several bugs for how Lustre handles the dcache a bug was exposed with sanity test 233. In the testing with newer kernels the following was seen:&lt;/p&gt;

&lt;p&gt;VFS: Lookup of &apos;&lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000002:0x1:0x0&amp;#93;&lt;/span&gt;&apos; in lustre lustre would have caused loop&lt;/p&gt;

&lt;p&gt;In older kernels it is an outright crash of the node. After some debugging it was discovered why. If a name in .lustre/fid refers to a directory, then that directory will (could) have 2 names in the dcache - the name in .lustre/fid, and the &quot;real&quot; name. The dcache does not permit this. You cannot have two dentries pointing the the same directory inode. Multiple hard links to directories are forbidden. Currently lustre attempts to break this rule by spinning its own dcache routines but that does not guarantee in the future that some core dcache functionality will change that breaks lustre. Due to the having multiple hard links you can form loops like reported above or if some core dcache functionality does an assert of dancestor() that will crash the node. &#160;It could even be possible that in the future the dcache core code might even prune its cache of broken dentries.&lt;/p&gt;</description>
                <environment></environment>
        <key id="53572">LU-11501</key>
            <summary>use the dcache properly with .lustre/fid</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="3" iconUrl="https://jira.whamcloud.com/images/icons/statuses/inprogress.png" description="This issue is being actively worked on at the moment by the assignee.">In Progress</status>
                    <statusCategory id="4" key="indeterminate" colorName="inprogress"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="simmonsja">James A Simmons</assignee>
                                    <reporter username="simmonsja">James A Simmons</reporter>
                        <labels>
                    </labels>
                <created>Wed, 10 Oct 2018 23:24:27 +0000</created>
                <updated>Fri, 1 Apr 2022 22:38:56 +0000</updated>
                                                            <fixVersion>Upstream</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="234815" author="pjones" created="Fri, 12 Oct 2018 12:38:47 +0000"  >&lt;p&gt;James&lt;/p&gt;

&lt;p&gt;Do I understand correctly that this is a longer-term task relating to the upstream kernel work?&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="234823" author="simmonsja" created="Fri, 12 Oct 2018 13:31:00 +0000"  >&lt;p&gt;Yes its a longer term project. Currently the way lustre handles .lustre/fid in relation to the dcache is starting to show up with tickets like &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9735&quot; title=&quot;Sles12Sp2 and 2.9 getcwd() sometimes fails&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9735&quot;&gt;&lt;del&gt;LU-9735&lt;/del&gt;&lt;/a&gt;. I&apos;m working around the issues but in the future we can expect more breakage. Will look into other solutions&lt;/p&gt;</comment>
                            <comment id="312127" author="gerrit" created="Sun, 5 Sep 2021 01:53:56 +0000"  >&lt;p&gt;&quot;James Simmons &amp;lt;jsimmons@infradead.org&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/44846&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/44846&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11501&quot; title=&quot;use the dcache properly with .lustre/fid&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11501&quot;&gt;LU-11501&lt;/a&gt; llite: use d_real for directories in fid cache.&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 26e52756fe807e23d1c76ad5d257ae1f0c81e989&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="47785">LU-9868</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="24566">LU-5008</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="39648">LU-8585</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="46611">LU-9629</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="54891">LU-11970</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i00413:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>