From nobody Tue Aug 29 14:45:51 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RZqx54xXSz4rs1g for ; Tue, 29 Aug 2023 14:46:01 +0000 (UTC) (envelope-from dchagin@heemeyer.club) Received: from heemeyer.club (heemeyer.club [195.93.173.158]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RZqx415N8z3S9l for ; Tue, 29 Aug 2023 14:45:59 +0000 (UTC) (envelope-from dchagin@heemeyer.club) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of dchagin@heemeyer.club has no SPF policy when checking 195.93.173.158) smtp.mailfrom=dchagin@heemeyer.club; dmarc=none Received: from heemeyer.club (localhost [127.0.0.1]) by heemeyer.club (8.17.2/8.16.1) with ESMTP id 37TEjp7h071573 for ; Tue, 29 Aug 2023 17:45:51 +0300 (MSK) (envelope-from dchagin@heemeyer.club) Received: (from dchagin@localhost) by heemeyer.club (8.17.2/8.16.1/Submit) id 37TEjp5V071572 for current@freebsd.org; Tue, 29 Aug 2023 17:45:51 +0300 (MSK) (envelope-from dchagin) Date: Tue, 29 Aug 2023 17:45:51 +0300 From: Dmitry Chagin To: current@freebsd.org Subject: Re: Possible issue with linux xattr support? Message-ID: References: <3q2k3tje2ig2s6wzy4hzvjmoyejiecminvcvevivumtukxrgki@btnpjbztyfa6> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: / X-Spamd-Result: default: False [-0.77 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_SHORT(-0.97)[-0.971]; FORGED_SENDER(0.30)[dchagin@freebsd.org,dchagin@heemeyer.club]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:61400, ipnet:195.93.173.0/24, country:RU]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FROM_NEQ_ENVFROM(0.00)[dchagin@freebsd.org,dchagin@heemeyer.club]; FREEFALL_USER(0.00)[dchagin]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4RZqx415N8z3S9l On Tue, Aug 29, 2023 at 12:59:11PM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230828 18:57]: > > On Mon, Aug 28, 2023 at 08:03:33AM +0200, Felix Palmen wrote: > > > * Cy Schubert [20230827 16:59]: > > > > > > > > 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 > > Thanks, I can confirm this avoids the issue in both cases I experienced > (install from GNU coreutils and python). > thanks, this is the first half of the fix, it works for you due to you are running tools under unprivileged user, afaiu. The second I have tested by myself :) > If I understand this patch correctly, it completely avoids EPERM, > masking it as not supported, so callers should consider it non-fatal, > allowing to silently ignore writing of "system" attributes while still > keeping other functionality? > system namespace is accessible only for privileged user, for others Linux returns ENOTSUP. So many tools ignores this error, eg ls. the second: https://people.freebsd.org/~dchagin/sea_jailed.patch Try this under privileged user, please. > I wonder whether this could cause trouble in other scenarios (like a > read-only fs or actually missing file permissions)? > > Cheers, Felix > > -- > Felix Palmen {private} felix@palmen-it.de > -- ports committer -- {web} http://palmen-it.de > {pgp public key} http://palmen-it.de/pub.txt > {pgp fingerprint} 6936 13D5 5BBF 4837 B212 3ACC 54AD E006 9879 F231