Hi Ilya,
thank you very much for the information. I will switch to 5.4.
Regards
Felix
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Am 14.02.20, 16:29 schrieb "Ilya Dryomov" <idryomov@xxxxxxxxx>:
On Fri, Feb 14, 2020 at 12:20 PM Stolte, Felix <f.stolte@xxxxxxxxxxxxx> wrote:
>
> Hi guys,
>
> I am exporting cephfs with samba using the vfs acl_xattr which stores ntfs acls in the security extended attributes. This works fine using cephfs kernel mount wither kernel version 4.15.
>
> Using kernel 5.3 I cannot access the security.ntacl attributes anymore. Attributes in user or ceph namespace is still working.
>
> Can someone enlighten me on this issue (or even better tell me how to fix it)?
Hi Felix,
I think this issue was introduced by [1] in 5.3 and fixed by [2] in
5.4. Looks like Jeff didn't realise he was fixing a regression and
didn't flag the fix for backporting.
There is nothing we can do about 5.3 now, so upgrading to 5.4 or 5.5
is probably the only option.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac6713ccb5a6d13b59a2e3fda4fb049a2c4e0af2
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8fe918b090442447d821b32b7dd6e17d5b5dfc1
Thanks,
Ilya
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
