<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:17:01 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-1482] attribute not permitted on Lustre versions 2.x</title>
                <link>https://jira.whamcloud.com/browse/LU-1482</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Attribute are not permitted on version 2.x but works on version 1.8.x &lt;/p&gt;


&lt;p&gt;to reproduce the problem&lt;/p&gt;

&lt;p&gt;Lustre clients are mounted with option acl,user_xattr&lt;br/&gt;
wipp-mds2@tcp:/WIPP /mnt/Lustre lustre defaults,acl, 0 0&lt;/p&gt;


&lt;p&gt;#!/bin/bash&lt;br/&gt;
rm -f dummy_file_test_xattr&lt;br/&gt;
touch dummy_file_test_xattr&lt;br/&gt;
chown nobody:nobody dummy_file_test_xattr&lt;br/&gt;
su -s/bin/bash nobody -c &quot;setfacl -m g:bin:rw dummy_file_test_xattr&quot;&lt;br/&gt;
su -s/bin/bash nobody -c &quot;getfacl dummy_file_test_xattr&quot;&lt;br/&gt;
su -s/bin/bash bin -c &quot;setfattr -n user.test.xattr -v 123456 dummy_file_test_xattr&quot;&lt;br/&gt;
su -s/bin/bash bin -c &quot;getfattr -d dummy_file_test_xattr&quot;&lt;/p&gt;

&lt;p&gt;the output&lt;br/&gt;
setfattr: dummy_file_test_xattr: Operation not permitted&lt;/p&gt;</description>
                <environment>MDS Redhat 6 64 bit with Lustre version 2.2&lt;br/&gt;
3 OSSs Redhat 5 64 bit with Lustre version 2.2&lt;br/&gt;
Clients Redhat 5 64 bit with Lustre version 2.2 </environment>
        <key id="14746">LU-1482</key>
            <summary>attribute not permitted on Lustre versions 2.x</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="dmiter">Dmitry Eremin</assignee>
                                    <reporter username="pierrec">Pierre Choukroun</reporter>
                        <labels>
                    </labels>
                <created>Tue, 5 Jun 2012 15:36:08 +0000</created>
                <updated>Thu, 8 Sep 2016 04:19:38 +0000</updated>
                            <resolved>Thu, 8 Sep 2016 04:19:38 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                    <version>Lustre 2.2.0</version>
                    <version>Lustre 2.1.1</version>
                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>4</votes>
                                    <watches>16</watches>
                                                                            <comments>
                            <comment id="40795" author="adilger" created="Mon, 18 Jun 2012 18:40:37 +0000"  >&lt;p&gt;This does appear to be a valid test case.  Looking at the kernel code, it seems that users that do not own a file should still be able to create user.* xattrs on a file they have write permission on.  I suspect some strange interaction between ACLs and the xattr permission checking is the cause.  Is this reproducible with a RHEL6 client (filesystem could be mounted temporarily on the MDS for testing purposes)?&lt;/p&gt;

&lt;p&gt;However, I&apos;m reducing the severity of this problem, since it is a relatively obscure use case, and is unlikely to be fixed in the short term.&lt;/p&gt;</comment>
                            <comment id="43618" author="pierrec" created="Wed, 22 Aug 2012 10:11:23 +0000"  >&lt;p&gt;The attribute problem may be a corner case for you, but it is a show stopper for users of the LHC Computing Grid&#8217;s STORM storage resource manager (&lt;a href=&quot;http://storm.forge.cnaf.infn.it/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://storm.forge.cnaf.infn.it/&lt;/a&gt;) that want to upgrade to Lustre 2.X Attributes are used to store checksums of every file which, after every gridftp transfer, are compared between source and destination. As long as this bug remains unfixed, we cannot upgrade Lustre. I hope you will upgrade the priority for fixing this bug so that we and the other STORM sites around the world using Lustre can upgrade. &lt;/p&gt;</comment>
                            <comment id="58275" author="goncalo" created="Mon, 13 May 2013 14:32:08 +0000"  >&lt;p&gt;This issue seems to be stalled since June 2012 with no evolution whatsoever. The attribute issue is really a showstopper in our case since it is avoiding the migration to lustre 2.1 and its interaction with the StoRM SRM system. We are a Tier-2 for WLCG with a storage capacity of about 600 TB. As we, there are a couple of more sites in the same situation, and therefore, the impact of this issue is not small. &lt;/p&gt;

&lt;p&gt;I&apos;ve just tried it with a lustre 1.8 client in RH6:&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;touch dummy_file_test_xattr&lt;/li&gt;
	&lt;li&gt;chown storm:storm dummy_file_test_xattr&lt;/li&gt;
	&lt;li&gt;su -s /bin/bash storm -c &quot;setfacl -m g:auger:rw dummy_file_test_xattr&quot;&lt;/li&gt;
	&lt;li&gt;su -s/bin/bash storm -c &quot;getfacl dummy_file_test_xattr&quot;&lt;/li&gt;
	&lt;li&gt;file: dummy_file_test_xattr&lt;/li&gt;
	&lt;li&gt;owner: storm&lt;/li&gt;
	&lt;li&gt;group: storm&lt;br/&gt;
user::rw-&lt;br/&gt;
group::r--&lt;br/&gt;
group:auger:rw-&lt;br/&gt;
mask::rw-&lt;br/&gt;
other::r--&lt;/li&gt;
	&lt;li&gt;su -s/bin/bash auger001 -c &quot;setfattr -n user.test.xattr -v 123456 dummy_file_test_xattr&quot;&lt;br/&gt;
setfattr: dummy_file_test_xattr: Operation not supported&lt;/li&gt;
&lt;/ol&gt;

</comment>
                            <comment id="59067" author="goncalo" created="Wed, 22 May 2013 15:22:05 +0000"  >&lt;p&gt;Dear All&lt;/p&gt;

&lt;p&gt;After some investigation, mostly from two of my colleagues, we were able to pinpoint the problem. &lt;/p&gt;

&lt;p&gt;The main difference between lustre 1.8 and 2.x series is that the acls are now checked on the server side, while in the older 1.8 versions, these was done in the client side. This lead to some restructure of the code, and the current implementation relies on very simple validations. &lt;/p&gt;

&lt;p&gt;These very simple validations are done in mdd_xattr_sanity_check function under lustre/mdd/mdd_object.c. The fundamental piece of code is&lt;/p&gt;

&lt;p&gt;        if ((uc-&amp;gt;mu_fsuid != tmp_la-&amp;gt;la_uid) &amp;amp;&amp;amp;&lt;br/&gt;
            !mdd_capable(uc, CFS_CAP_FOWNER))&lt;br/&gt;
                RETURN(-EPERM);&lt;/p&gt;

&lt;p&gt;which basically tells you that only the owner of the file is allowed to change the extended atributes. &lt;/p&gt;

&lt;p&gt;We have developed a dirty hack to overcome this issue but we do not want to make it public since it may not be general enough, or may have hidden problems since I&apos;m sure we do not have a full understanding of the code. I&apos;m certain that Whamcloud people can do it much better, and now that we have identified the problem, maybe the fix could be delivered faster than expected. &lt;/p&gt;

&lt;p&gt;Thank you&lt;br/&gt;
Goncalo&lt;/p&gt;</comment>
                            <comment id="84351" author="jeremym" created="Sun, 18 May 2014 22:36:38 +0000"  >&lt;p&gt;We are also a Tier-2 for WLCG, and have held off upgrading from Lustre 1.8.9 because of this problem. &lt;br/&gt;
We really do need to move to Lustre 2.x!!&lt;/p&gt;

&lt;p&gt;The bug is is still there in v2.4.1; tested with ext4/ldiskfs back-end:&lt;br/&gt;
-----------&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;rpm -qa | grep lustre-2&lt;br/&gt;
lustre-2.4.1-2.6.32_358.18.1.el6_lustre.x86_64.x86_64&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;./testscript&lt;/li&gt;
	&lt;li&gt;file: dummy_file_test_xattr&lt;/li&gt;
	&lt;li&gt;owner: nobody&lt;/li&gt;
	&lt;li&gt;group: nobody&lt;br/&gt;
user::rw-&lt;br/&gt;
group::r--&lt;br/&gt;
group:bin:rw-&lt;br/&gt;
mask::rw-&lt;br/&gt;
other::r--&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;setfattr: dummy_file_test_xattr: Operation not permitted&lt;/p&gt;

&lt;p&gt;-----------&lt;/p&gt;

&lt;p&gt;Wil this problem ever be addressed?&lt;/p&gt;

&lt;p&gt;Jeremy&lt;/p&gt;</comment>
                            <comment id="123918" author="wangshilong" created="Wed, 12 Aug 2015 00:57:53 +0000"  >&lt;p&gt;I think maybe something like this should fix issue?&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;diff --git a/lustre/mdd/mdd_object.c b/lustre/mdd/mdd_object.c
index 5938bc9..441c3db 100644
--- a/lustre/mdd/mdd_object.c
+++ b/lustre/mdd/mdd_object.c
@@ -951,8 +951,8 @@ &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; mdd_xattr_sanity_check(&lt;span class=&quot;code-keyword&quot;&gt;const&lt;/span&gt; struct lu_env *env,
                    !md_capable(uc, CFS_CAP_FOWNER))
                        RETURN(-EPERM);
        } &lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; {
-               &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; ((uc-&amp;gt;uc_fsuid != tmp_la-&amp;gt;la_uid) &amp;amp;&amp;amp;
-                   !md_capable(uc, CFS_CAP_FOWNER))
+               &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (uc-&amp;gt;uc_fsuid != tmp_la-&amp;gt;la_uid &amp;amp;&amp;amp;
+                     !md_capable(uc, CFS_CAP_CHOWN))
                        RETURN(-EPERM);
        }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt; We don&apos;t need OWNER rights always..&lt;/p&gt;</comment>
                            <comment id="123919" author="gerrit" created="Wed, 12 Aug 2015 01:52:39 +0000"  >&lt;p&gt;Wang Shilong (wshilong@ddn.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/15959&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/15959&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1482&quot; title=&quot;attribute not permitted on Lustre versions 2.x&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1482&quot;&gt;&lt;del&gt;LU-1482&lt;/del&gt;&lt;/a&gt; mdd: remove owner rights check for xattr permission&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: cd58efc71705edb7ab96bc64d295d22948312d28&lt;/p&gt;</comment>
                            <comment id="147423" author="gerrit" created="Thu, 31 Mar 2016 09:15:10 +0000"  >&lt;p&gt;Wang Shilong (wshilong@ddn.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/19258&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19258&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1482&quot; title=&quot;attribute not permitted on Lustre versions 2.x&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1482&quot;&gt;&lt;del&gt;LU-1482&lt;/del&gt;&lt;/a&gt; mdd: Setting xattr are properly checked with and without ACLs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 8d29a17482ed41ef654d538dd3a667834b5dcf37&lt;/p&gt;</comment>
                            <comment id="159724" author="gerrit" created="Mon, 25 Jul 2016 14:15:03 +0000"  >&lt;p&gt;Dmitry Eremin (dmitry.eremin@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/21496&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/21496&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1482&quot; title=&quot;attribute not permitted on Lustre versions 2.x&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1482&quot;&gt;&lt;del&gt;LU-1482&lt;/del&gt;&lt;/a&gt; mdd: Setting xattr are properly checked with and without ACLs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 2bd076858bd40532985d7caa1609266a7fe88927&lt;/p&gt;</comment>
                            <comment id="165228" author="gerrit" created="Thu, 8 Sep 2016 02:05:57 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/21496/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/21496/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1482&quot; title=&quot;attribute not permitted on Lustre versions 2.x&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1482&quot;&gt;&lt;del&gt;LU-1482&lt;/del&gt;&lt;/a&gt; mdd: Setting xattr are properly checked with and without ACLs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 93e459f4d0604cccb31e5cc0a1677499d48fff0b&lt;/p&gt;</comment>
                            <comment id="165254" author="pjones" created="Thu, 8 Sep 2016 04:19:38 +0000"  >&lt;p&gt;Landed for 2.9&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="14175">LU-1343</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                        </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|hzvrlb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8361</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>