From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FSL_HELO_FAKE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 30C87C32767 for ; Fri, 3 Jan 2020 17:08:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 03511215A4 for ; Fri, 3 Jan 2020 17:08:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1578071321; bh=LRI0fj+VA2I4+uKI4FIhQqiYK3mZfwRLgeKo7n8eJQU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=zs4WtTWW+jx2kLAlNpwCfXvgQoizQg9t8o2eskEdpGBRlFrTq1g5tiDBOICl3DXBj SxEa4kwWKfrKtXNvoKm9J/pByVtSAF+D55ScRxUKy1rNdzmgRk8PctJIHa0eG7jE8F E0LBjnVXH+2BdMjTjWg9AQeZX7mqMTt1LglSu4uQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728021AbgACRIk (ORCPT ); Fri, 3 Jan 2020 12:08:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:39990 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727912AbgACRIk (ORCPT ); Fri, 3 Jan 2020 12:08:40 -0500 Received: from gmail.com (unknown [104.132.1.77]) (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 67A7520866; Fri, 3 Jan 2020 17:08:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1578071319; bh=LRI0fj+VA2I4+uKI4FIhQqiYK3mZfwRLgeKo7n8eJQU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gYhwY5A5asqoJvfgyTKNS2fl83jrU1n44A3+2bqqDGF1oPbLjlCiJzuQjnEsMDlvr YoBqjpp2V0MQHiMlC3y6igAb2GOd1dONSFaQqTpTB0j3+BK+oebKW9jbT0uicQIMk6 stxTya8Mw+Fcw5y/JaUWWBalvg11gLqyiAWLfrwI= Date: Fri, 3 Jan 2020 09:08:37 -0800 From: Eric Biggers To: Richard Weinberger , linux-mtd@lists.infradead.org Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 0/2] ubifs: fixes for FS_IOC_GETFLAGS and FS_IOC_SETFLAGS Message-ID: <20200103170837.GN19521@gmail.com> References: <20191209222325.95656-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191209222325.95656-1-ebiggers@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, Dec 09, 2019 at 02:23:23PM -0800, Eric Biggers wrote: > On ubifs, fix FS_IOC_SETFLAGS to not clear the encrypt flag, and update > FS_IOC_GETFLAGS to return the encrypt flag like ext4 and f2fs do. > > Eric Biggers (2): > ubifs: fix FS_IOC_SETFLAGS unexpectedly clearing encrypt flag > ubifs: add support for FS_ENCRYPT_FL > > fs/ubifs/ioctl.c | 14 +++++++++++--- > 1 file changed, 11 insertions(+), 3 deletions(-) > Richard, can you consider applying this series to the UBIFS tree for 5.6? - Eric