Re: [PATCH v3 00/17] Xattr inode operation removal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/30/16, Andreas Gruenbacher <agruenba@xxxxxxxxxx> wrote:
> On Mon, May 30, 2016 at 6:02 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:
>> I contacted the LTP mailing-list on the acl_test01 issues - WIP.
>>
>> From the LTP-ML I got the impulse to test with the xattr testcase...
>>
>> root# cd /opt/ltp ; LC_ALL=C ./runltp -s xattr | tee xattr.log
>>
>> ...this fails only in the cgroup_xattr testcase.
>> [...]
>
> The test seems to try getting/setting an xattr named "trusted." (no
> suffix). That's an invalid name; such invalid names are rejected since
> commit 98e9cb571 "vfs: Distinguish between full xattr names and proper
> prefixes" (v4.5-rc1).
>
> Could you try removing that from the LTP test and rerun it?
>

AFAICS I need to re-compile...

[ testcases/kernel/controllers/cgroup_xattr/cgroup_xattr.c ]
...
/* only security.* & trusted.* are valid key names */
static struct tst_key tkeys[] = {
        { .name = "security.",          .good = 1,      },
        { .name = "trusted.test",       .good = 1,      },
        { .name = "trusted.",           .good = 1,      }, <--- XXX:
This one only?
        { .name = "user.",              .good = 0,      },
        { .name = "system.",            .good = 0,      },
};
...

Which "trusted." line or lines shall I remove?

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Crypto]     [Device Mapper Crypto]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux