From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1781921CF951F for ; Mon, 31 Jul 2017 09:30:20 -0700 (PDT) Message-Id: <1501518747.586018.1058450568.4B6F28FB@webmail.messagingengine.com> From: Colin Walters MIME-Version: 1.0 In-Reply-To: Subject: Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE Date: Mon, 31 Jul 2017 12:32:27 -0400 References: <150135740948.35318.10730072114996910905.stgit@dwillia2-desk3.amr.corp.intel.com> <150135741519.35318.16765137368329971936.stgit@dwillia2-desk3.amr.corp.intel.com> <1501516968.579311.1058393288.0714478A@webmail.messagingengine.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: Jan Kara , linux-nvdimm@lists.01.org, "Darrick J. Wong" , Dave Chinner , linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, Alexander Viro , Andy Lutomirski , linux-fsdevel , Christoph Hellwig List-ID: On Mon, Jul 31, 2017, at 12:29 PM, Dan Williams wrote: > > How is S_CONTENTS_IMMUTABLE different than S_IMMUTABLE? We still want the ability to make hardlinks. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm