Comment # 1 on bug 1192027 from Jiri Slaby

(In reply to Guillaume GARDET from comment #0)
> statx04.c:144: TBROK: ioctl(3, FS_IOC_SETFLAGS, 1619672317): EINVAL (22)

That is sum of these flags:
FS_SECRM_FL                     0x00000001 /* Secure deletion */
FS_COMPR_FL                     0x00000004 /* Compress file */
FS_SYNC_FL                      0x00000008 /* Synchronous updates */
FS_IMMUTABLE_FL                 0x00000010 /* Immutable file */
FS_APPEND_FL                    0x00000020 /* writes to file may only append */
FS_NODUMP_FL                    0x00000040 /* do not dump file */
FS_NOATIME_FL                   0x00000080 /* do not update atime */
FS_NOCOMP_FL                    0x00000400 /* Don't compress */
FS_ENCRYPT_FL                   0x00000800 /* Encrypted file */
FS_BTREE_FL                     0x00001000 /* btree format dir */
FS_INDEX_FL                     0x00001000 /* hash-indexed directory */
FS_IMAGIC_FL                    0x00002000 /* AFS directory */
FS_TOPDIR_FL                    0x00020000 /* Top of directory hierarchies*/
FS_EXTENT_FL                    0x00080000 /* Extents */
FS_NOCOW_FL                     0x00800000 /* Do not cow file */
FS_PROJINHERIT_FL               0x20000000 /* Create with parents projid */
FS_CASEFOLD_FL                  0x40000000 /* Folder is case insensitive */

And (likely) fileattr_set_prepare() denies this combination. Why the test
thinks it's a valid combination of flags?

Anyway, is this still an issue?