Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp3688757ybv; Mon, 10 Feb 2020 04:44:55 -0800 (PST) X-Google-Smtp-Source: APXvYqzlci7o4DB0SrocbdmNgBlie0R8iEl+wiwziQbb4DlNtLyAqdYFlnfXWKs5woGZIMJgBnVR X-Received: by 2002:a9d:4c8c:: with SMTP id m12mr953124otf.312.1581338695419; Mon, 10 Feb 2020 04:44:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581338695; cv=none; d=google.com; s=arc-20160816; b=oEi53VcRxtrOle6PL/2jpNLxS2Ag9mDkYgrz+efnj9RQgENV5HtiwHMqhjZHdXKRRw KUSb7s7ckloDRi9TaYsmwEhFAoD4rVlKbzH3FR/kFNQICT0pJuKH8wh5VXPFPLZlM14o xijwWXJpBq4UBEnCIxlFZEEIYkkuHR646mEZRc44Gg9UsT9LegkAIqX6j1SG0Xihzc96 ndmDPKjhUW/xHAKRM3f+1VRUSTCUXUDMPRkC6xe6DZu2DWE4e3VKZ2XPOhBImC/cB185 uPD8+t6AGZ6LjXA3t8GDf2B5Cj+/EPp1jGxGYFTljgY/kTW9vAt+7f75qY8csC8zS3oY CMpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=jEbpp6dCT357hgv2FbTqLU7qUrr3IJxOUwBUO2/xtBU=; b=TV1YFn9QiR5fSZbKlX6IJsTdUoXU7O7Ept++qpl7uO1IJIsCn8YLJd01vXYUzkwo/b PmabTHLNsgZg3m1zLKlXZ8UsD91bp5WEjBMpF91kzrXRY+aJ5FVvh1einNGGkP1bb+4c uzaFccHFnOFI8Z3sd0RKMOrStwGlAJFklGoPn1V2nu9SU9aQhyamxB/2JALbWNqnveum uhnnYYnTkcd5H7+lMJ2597roGi1NKWnb3tKYlr0BV7XozeLleU4/hiAWNKe1Uc9rUtz1 RIXmdOuhYuaIHLW5pH0xC7CysNhhLuIMY2vU0sLtv0VJpNfhG+kSSPyjmIcavhKUzzbl VY/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YP+rFEmG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t70si120497oif.99.2020.02.10.04.44.43; Mon, 10 Feb 2020 04:44:55 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YP+rFEmG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730129AbgBJMne (ORCPT + 99 others); Mon, 10 Feb 2020 07:43:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:38920 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728813AbgBJMkD (ORCPT ); Mon, 10 Feb 2020 07:40:03 -0500 Received: from localhost (unknown [209.37.97.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 70CE82085B; Mon, 10 Feb 2020 12:40:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581338403; bh=BvFCv21X/M3zlOubwmJLJSz0U2M68Y+y6binuJ8WJEo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=YP+rFEmGPFzoQNEPKv9fkj8cIXeywO9+A7HPkuv4YbovC3obHDDl3iJSBPlFwHCBG pdDRFaXlyLEWf4HqPdtw2gy65KQ0qGlQbi1LF7YxTm4XmXNg/SQj637E01hiJtyZhl qjJQBvKbutY2DRCC+hYFkNlbUkT3fMOqdwBUr7fI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Eric Biggers , Richard Weinberger Subject: [PATCH 5.5 104/367] ubifs: Fix FS_IOC_SETFLAGS unexpectedly clearing encrypt flag Date: Mon, 10 Feb 2020 04:30:17 -0800 Message-Id: <20200210122433.984203459@linuxfoundation.org> X-Mailer: git-send-email 2.25.0 In-Reply-To: <20200210122423.695146547@linuxfoundation.org> References: <20200210122423.695146547@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Eric Biggers commit 2b57067a7778484c10892fa191997bfda29fea13 upstream. UBIFS's implementation of FS_IOC_SETFLAGS fails to preserve existing inode flags that aren't settable by FS_IOC_SETFLAGS, namely the encrypt flag. This causes the encrypt flag to be unexpectedly cleared. Fix it by preserving existing unsettable flags, like ext4 and f2fs do. Test case with kvm-xfstests shell: FSTYP=ubifs KEYCTL_PROG=keyctl . fs/ubifs/config . ~/xfstests/common/encrypt dev=$(__blkdev_to_ubi_volume /dev/vdc) ubiupdatevol -t $dev mount $dev /mnt -t ubifs k=$(_generate_session_encryption_key) mkdir /mnt/edir xfs_io -c "set_encpolicy $k" /mnt/edir echo contents > /mnt/edir/file chattr +i /mnt/edir/file chattr -i /mnt/edir/file With the bug, the following errors occur on the last command: [ 18.081559] fscrypt (ubifs, inode 67): Inconsistent encryption context (parent directory: 65) chattr: Operation not permitted while reading flags on /mnt/edir/file Fixes: d475a507457b ("ubifs: Add skeleton for fscrypto") Cc: # v4.10+ Signed-off-by: Eric Biggers Signed-off-by: Richard Weinberger Signed-off-by: Greg Kroah-Hartman --- fs/ubifs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/fs/ubifs/ioctl.c +++ b/fs/ubifs/ioctl.c @@ -113,7 +113,8 @@ static int setflags(struct inode *inode, if (err) goto out_unlock; - ui->flags = ioctl2ubifs(flags); + ui->flags &= ~ioctl2ubifs(UBIFS_SUPPORTED_IOCTL_FLAGS); + ui->flags |= ioctl2ubifs(flags); ubifs_set_inode_flags(inode); inode->i_ctime = current_time(inode); release = ui->dirty;