On Fri, Feb 26, 2021 at 05:51:44PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> When we have smack enabled, during the creation of a directory smack may
> attempt to add a "smack transmute" xattr on the inode, which results in
> the following warning and trace:
>
> [ 220.732359]
On 2021/2/27 上午9:01, Qu Wenruo wrote:
On 2021/2/27 上午1:51, fdman...@kernel.org wrote:
From: Filipe Manana
When we have smack enabled, during the creation of a directory smack may
attempt to add a "smack transmute" xattr on the inode, which results in
the following warning and trace:
[ 2
On 2021/2/27 上午1:51, fdman...@kernel.org wrote:
From: Filipe Manana
When we have smack enabled, during the creation of a directory smack may
attempt to add a "smack transmute" xattr on the inode, which results in
the following warning and trace:
[ 220.732359] [ cut here ]--
On 2/26/2021 9:51 AM, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> When we have smack enabled, during the creation of a directory smack may
> attempt to add a "smack transmute" xattr on the inode, which results in
> the following warning and trace:
>
> [ 220.732359] [ cut here
From: Filipe Manana
When we have smack enabled, during the creation of a directory smack may
attempt to add a "smack transmute" xattr on the inode, which results in
the following warning and trace:
[ 220.732359] [ cut here ]
[ 220.732398] WARNING: CPU: 3 PID: 2548 at fs
