From nobody Wed Aug 30 08:57:33 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 4RbJ8g25wgz4rtKD for ; Wed, 30 Aug 2023 08:57:39 +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 4RbJ8d55MHz3MW7 for ; Wed, 30 Aug 2023 08:57:37 +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 37U8vX05010518 for ; Wed, 30 Aug 2023 11:57:33 +0300 (MSK) (envelope-from dchagin@heemeyer.club) Received: (from dchagin@localhost) by heemeyer.club (8.17.2/8.16.1/Submit) id 37U8vXaN010517 for current@freebsd.org; Wed, 30 Aug 2023 11:57:33 +0300 (MSK) (envelope-from dchagin) Date: Wed, 30 Aug 2023 11:57:33 +0300 From: Dmitry Chagin To: current@freebsd.org Subject: Re: Possible issue with linux xattr support? Message-ID: References: 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 [1.18 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.98)[0.981]; FORGED_SENDER(0.30)[dchagin@freebsd.org,dchagin@heemeyer.club]; MIME_GOOD(-0.10)[text/plain]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[current@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[dchagin@freebsd.org,dchagin@heemeyer.club]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[dchagin]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:61400, ipnet:195.93.173.0/24, country:RU] X-Rspamd-Queue-Id: 4RbJ8d55MHz3MW7 On Tue, Aug 29, 2023 at 08:58:13PM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230829 21:12]: > > On Tue, Aug 29, 2023 at 07:02:22PM +0200, Felix Palmen wrote: > > > So, using user.* works, using system.* doesn't, and maybe a bit > > > surprising(?), dumping all attributes which by default excludes the > > > system namespace doesn't work either. > > > > > > > As expected, the second patch intended to allow access to system > > namespace in jailed env. > > Not exactly, according to the manual, 'getfattr -d' *excludes* the > system namespace by default, so I would have expected it to work. But > maybe that's an issue with the getfattr tool itself. > > > > I still wonder, is the first patch needed anyways? Maybe I fail to > > > understand something here. Won't it map *every* EPERM to ENOSUP and > > > can't this be an issue? > > > > > > > fine, thanks. Gnu tools running under unprivileged user will fail, eg > > ls, which uses getfattr() to get the posix acl > > Ah, I see, that would still break "Linux jails" then... > > Thanks again for quickly fixing this! Can this still make 14.0-RELEASE? > I think yes, thanks for testing, I revised the error handling and made it more precise, can you test new patch in your environment. https://people.freebsd.org/~dchagin/xattr.patch Revert previous patches