<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:52:34 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-5564] open handle leak after setuid()</title>
                <link>https://jira.whamcloud.com/browse/LU-5564</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;MDS_CLOSE RPCs are sent with the current_fs{uid,gid}(). If this id cannot be resolved on the MDT then mdt_close() fails in unpack and the open handle is never released.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;# MOUNT_2=y llmount.sh
...
# id 42
id: 42: No such user
# cp /bin/sleep /mnt/lustre/sleep
# chown 42:42 /mnt/lustre/sleep
# chmod ug+s /mnt/lustre/sleep
# /mnt/lustre/sleep 0
# echo &amp;gt; /mnt/lustre2/sleep
-bash: /mnt/lustre2/sleep: Text file busy
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;[  475.032992] LustreError: 6559:0:(file.c:186:ll_close_inode_openhandle()) lustre-clilmv-ffff8802173141c8: inode [0x200000400:0x3:0x0] mdc close failed: rc = -13
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Seems a bit broken this way. With the exception of HSM release why check process permissions at close? The open FD (open handle) gives us permission.&lt;/p&gt;</description>
                <environment></environment>
        <key id="26237">LU-5564</key>
            <summary>open handle leak after setuid()</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="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="hongchao.zhang">Hongchao Zhang</assignee>
                                    <reporter username="jhammond">John Hammond</reporter>
                        <labels>
                            <label>mdt</label>
                    </labels>
                <created>Fri, 29 Aug 2014 17:37:37 +0000</created>
                <updated>Thu, 14 Jun 2018 21:41:18 +0000</updated>
                            <resolved>Wed, 22 Jun 2016 15:21:47 +0000</resolved>
                                    <version>Lustre 2.7.0</version>
                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>10</watches>
                                                                            <comments>
                            <comment id="120544" author="pjones" created="Tue, 7 Jul 2015 11:11:45 +0000"  >&lt;p&gt;Hongchao&lt;/p&gt;

&lt;p&gt;Could you please look into this issue?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="120718" author="gerrit" created="Wed, 8 Jul 2015 16:41:25 +0000"  >&lt;p&gt;Hongchao Zhang (hongchao.zhang@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/15534&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/15534&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5564&quot; title=&quot;open handle leak after setuid()&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5564&quot;&gt;&lt;del&gt;LU-5564&lt;/del&gt;&lt;/a&gt; llite: use original uid,gid to close file&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: b0ee3878dad8fa1d98b2d191983c0baa1f751b8d&lt;/p&gt;</comment>
                            <comment id="155489" author="hongchao.zhang" created="Mon, 13 Jun 2016 13:59:26 +0000"  >&lt;p&gt;status update:&lt;br/&gt;
the patch &lt;a href=&quot;http://review.whamcloud.com/15534&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/15534&lt;/a&gt; has been updated&lt;/p&gt;</comment>
                            <comment id="156179" author="gerrit" created="Mon, 20 Jun 2016 00:59:01 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/15534/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/15534/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5564&quot; title=&quot;open handle leak after setuid()&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5564&quot;&gt;&lt;del&gt;LU-5564&lt;/del&gt;&lt;/a&gt; mdt: skip permission check for close&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: abedce670d4f396443164bb582c7b58ec78ae7b7&lt;/p&gt;</comment>
                            <comment id="156505" author="jgmitter" created="Wed, 22 Jun 2016 15:21:47 +0000"  >&lt;p&gt;Patch has landed to master for 2.9.0&lt;/p&gt;</comment>
                            <comment id="222581" author="ahkumarsmu" created="Tue, 6 Mar 2018 17:45:11 +0000"  >&lt;p&gt;Dear All,&lt;/p&gt;

&lt;p&gt;I am running into this exact same issue on our setup of this version of Lustre-2.7.20. We will be looking for upgrading to Lustre 2.10 in summer. Until then what would one recommend to avoid this issue from happening? &lt;/p&gt;

&lt;p&gt;Is there a patch that I can apply in production? &lt;/p&gt;

&lt;p&gt;Alternatively I was looking if I could mount the SSSD cache on the Lustre servers to a /tmpfs, in case if it helped. &lt;/p&gt;

&lt;p&gt;Any comments are help here is greatly appreciated. &lt;/p&gt;

&lt;p&gt;Thank you,&lt;br/&gt;
Amit&lt;/p&gt;</comment>
                            <comment id="222582" author="pjones" created="Tue, 6 Mar 2018 17:49:26 +0000"  >&lt;p&gt;Amit&lt;/p&gt;

&lt;p&gt;Please direct that question through your support channels - this project is for matters relating to the community releases.&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </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|hzwuz3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15516</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>