From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756411AbcHCHxm (ORCPT ); Wed, 3 Aug 2016 03:53:42 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:42941 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753119AbcHCHxG (ORCPT ); Wed, 3 Aug 2016 03:53:06 -0400 Date: Wed, 3 Aug 2016 09:45:06 +0200 From: Greg Kroah-Hartman To: Eryu Guan Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Vivek Goyal , Miklos Szeredi Subject: Re: [PATCH 4.4 133/146] ovl: Copy up underlying inodes ->i_mode to overlay inode Message-ID: <20160803074506.GA23998@kroah.com> References: <20160725203521.340401316@linuxfoundation.org> <20160725203526.838883455@linuxfoundation.org> <20160803073644.GH27776@eguan.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160803073644.GH27776@eguan.usersys.redhat.com> User-Agent: Mutt/1.6.2 (2016-07-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 03, 2016 at 03:36:44PM +0800, Eryu Guan wrote: > On Mon, Jul 25, 2016 at 01:56:28PM -0700, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Vivek Goyal > > > > commit 07a2daab49c549a37b5b744cbebb6e3f445f12bc upstream. > > > > Right now when a new overlay inode is created, we initialize overlay > > inode's ->i_mode from underlying inode ->i_mode but we retain only > > file type bits (S_IFMT) and discard permission bits. > > > > This patch changes it and retains permission bits too. This should allow > > overlay to do permission checks on overlay inode itself in task context. > > > > [SzM] It also fixes clearing suid/sgid bits on write. > > This patch introduced a hang when writing to suid file, fstests > generic/355 could reproduce the hang easily, it only failed the test > without this patch and didn't hang the kernel. > > Should we skip it for now and wait for a further fix? Does Linus's tree have the same problem? > (The 4.6-stable tree faces the same question) Are we just missing a patch to be applied here? And this is already in the released stable kernels... thanks, greg k-h