On Mon, Aug 28, 2023 at 08:03:33AM +0200, Felix Palmen wrote: > * Cy Schubert <cy.schub...@cschubert.com> [20230827 16:59]: > > On August 27, 2023 12:55:23 PM PDT, Felix Palmen <zir...@freebsd.org> wrote: > > >* Dmitry Chagin <dcha...@freebsd.org> [20230827 22:46]: > > >> On Sun, Aug 27, 2023 at 07:59:32PM +0200, Felix Palmen wrote: > > >> > * Dmitry Chagin <dcha...@freebsd.org> [20230827 20:54]: > > >> > > 1. which fs are you using? > > >> > > > >> > ZFS. > > >> > > > >> > > 2. jailed? > > >> > > > >> > Yes, this is during building ports with poudriere. > > >> > > > >> > > >> I think it's a weird prohibition on changing system namespace extattr > > >> attributes, look to comments in extattr_check_cred() > > > > > >Maybe that's when I should finally start trying to understand the stuff > > >in src.git ;) > > > > > >> I can fix this completely disabling exttatr for jailed proc, > > >> however, it's gonna be bullshit, though > > > > > >Would probably be better than nothing. AFAIK, "Linux jails" are used a > > >lot, probably with userlands from distributions actually using xattr. > > > > > >Cheers, Felix > > > > > > > If we are to break it to fix a problem, maybe a sysctl to enable/disable > > then? > > IMHO depends on the exact nature of the problem. If it's confirmed that > it (always and only) breaks for jailed processes, just disabling it for > them would be the better workaround. "No-op" calls won't break anything. >
please, try: https://people.freebsd.org/~dchagin/xattrerror.patch
