From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CBCF61A29D; Fri, 20 Oct 2023 14:25:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="LJ/3joCf" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C7265C433CC; Fri, 20 Oct 2023 14:25:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1697811923; bh=wldg2zwOkncbKRJtGFBFpmkGBwcFXywZnG13CG3zHhc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LJ/3joCf+5FMJaprCbr89oaXtaFok28cVqNP3CRzEhEVviVmSBnfJEbf9nyriexnS kyIo8D2DFuBycYxVqzbD0Folujn5QAbqFEUqMSbxuUnEi4CIGcomqNtXAcZAdshQS4 oL+F3/lLdsPNrI1aA6ZpIXh3qpjnRQeYFi0xTIBA= Date: Fri, 20 Oct 2023 16:25:17 +0200 From: Greg KH To: Christian Brauner Cc: Linus Torvalds , Jesse Hathaway , Christoph Hellwig , Florian Weimer , Aleksa Sarai , linux-fsdevel@vger.kernel.org, Al Viro , stable@vger.kernel.org, Linux regressions mailing list , giuseppe@scrivano.org Subject: Re: [PATCH] attr: block mode changes of symlinks Message-ID: <2023102034-atlas-obligate-46bb@gregkh> References: <2023101819-satisfied-drool-49bb@gregkh> <38bf9c2b-25e2-498e-ae50-362792219e50@leemhuis.info> <20231020-allgegenwart-torbogen-33dc58e9a7aa@brauner> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231020-allgegenwart-torbogen-33dc58e9a7aa@brauner> On Fri, Oct 20, 2023 at 01:01:44PM +0200, Christian Brauner wrote: > The other option to consider would be to revert the backport of the attr > changes to stable kernels. I'm not sure what Greg's stance on this is > but given that crun versions in -testing already include that fix that > means all future Debian releases will already have a fixed crun version. I will be glad to revert a change in a stable tree that is also reverted in Linus's tree, but to just "delay" a change getting into the tree, that's not ok (either the change is good or not.) thanks, greg k-h