<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:31:32 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-3165] umask broken on master</title>
                <link>https://jira.whamcloud.com/browse/LU-3165</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;umask handling appears to be broken again on master.  With x86_64 servers running &lt;a href=&quot;http://github.com/chaos/lustre/commits/2.3.63-5chaos&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;2.3.63-5chaos&lt;/a&gt;, and ppc64 clients at either 2.3.58 or 2.3.63, umask does not appear to be honored.&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;vulcanlac2:/p/lscratchv/morrone$ mkdir foo
vulcanlac2:/p/lscratchv/morrone$ touch bar
vulcanlac2:/p/lscratchv/morrone$ ls -la
total 298
drwx------    3 morrone morrone   5632 Apr 12 15:51 .
drwxr-xr-x 2121 root    root    293376 Apr 12 15:05 ..
-rw-rw-rw-    1 morrone morrone      0 Apr 12 15:51 bar
drwxrwxrwx    2 morrone morrone   5632 Apr 12 15:51 foo
vulcanlac2:/p/lscratchv/morrone$ umask
0077
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Servers are running ZFS.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18397">LU-3165</key>
            <summary>umask broken on master</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.whamcloud.com/images/icons/priorities/blocker.svg">Blocker</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="laisiyao">Lai Siyao</assignee>
                                    <reporter username="morrone">Christopher Morrone</reporter>
                        <labels>
                            <label>LB</label>
                    </labels>
                <created>Fri, 12 Apr 2013 22:52:38 +0000</created>
                <updated>Fri, 19 Apr 2013 12:17:26 +0000</updated>
                            <resolved>Fri, 19 Apr 2013 12:17:26 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="56233" author="morrone" created="Fri, 12 Apr 2013 23:01:31 +0000"  >&lt;p&gt;Perhaps another swabbing bug introduced in the umask handling code when it was recently reworked?  An x86_64 client running lustre 2.1.4-3chaos does not see the umask problem.  So either the server behaves differently for the older client, or the different is the architecture of the client.&lt;/p&gt;
</comment>
                            <comment id="56236" author="pjones" created="Fri, 12 Apr 2013 23:26:47 +0000"  >&lt;p&gt;Lai&lt;/p&gt;

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

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="56238" author="nedbass" created="Sat, 13 Apr 2013 01:55:03 +0000"  >&lt;p&gt;It looks like mdt_rec_create.cr_umask uses the rr_padding_3 field from the template struct mdt_rec_reint, but lustre_swab_mdt_rec_reint() was never updated to swab that field.&lt;/p&gt;</comment>
                            <comment id="56294" author="laisiyao" created="Mon, 15 Apr 2013 05:54:13 +0000"  >&lt;p&gt;Both rr_flags_h and rr_umask are missing in mdt_rec_reint, the patch is on &lt;a href=&quot;http://review.whamcloud.com/#change,6054&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,6054&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="56399" author="nedbass" created="Tue, 16 Apr 2013 15:44:46 +0000"  >&lt;p&gt;Lai, your patch takes care of the umask problem.  Thanks&lt;/p&gt;</comment>
                            <comment id="56619" author="pjones" created="Fri, 19 Apr 2013 12:17:26 +0000"  >&lt;p&gt;Landed for 2.4&lt;/p&gt;</comment>
                    </comments>
                    <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|hzvnzr:</customfieldvalue>

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