From mboxrd@z Thu Jan 1 00:00:00 1970 From: Artem Bityutskiy Subject: Re: [PATCH 1/2] ubifs: Remove dead xattr code Date: Thu, 20 Aug 2015 09:42:53 +0300 Message-ID: <1440052973.31419.191.camel@linux.intel.com> References: <1440016553-26481-1-git-send-email-richard@nod.at> <55D54006.9030700@cn.fujitsu.com> Reply-To: artem.bityutskiy@linux.intel.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Subodh Nijsure , Marc Kleine-Budde , Brad Mouring , Gratian Crisan To: Dongsheng Yang , Richard Weinberger , linux-mtd@lists.infradead.org Return-path: In-Reply-To: <55D54006.9030700@cn.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2015-08-20 at 10:48 +0800, Dongsheng Yang wrote: > On 08/20/2015 04:35 AM, Richard Weinberger wrote: > > This is a partial revert of commit > > d7f0b70d30ffb9bbe6b8a3e1035cf0b79965ef53 > > ("UBIFS: Add security.* XATTR support for the UBIFS"). > > Hi Richard, > What about a full reverting of this commit. In ubifs, we > *can* support any namespace of xattr including user, trusted, > security > or other anyone prefixed by any words. But we have a > check_namespace() > in xattr.c to limit what we want to support. That said, if we want to > "Add security.* XATTR support for the UBIFS", what we need to do is > just extending the check_namespace() to allow security namespace > pass. > And yes, check_namespace() have been supporting security namespace. > > So, IMHO, we do not depend on the generic mechanism at all, and we > can > fully revert this commit. We just weren't careful enough. -- Best Regards, Artem Bityutskiy