From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. R. Okajima" <hooanon05g@gmail.com>
Subject: Re: [PATCH] overlayfs: copyup security inode field
Date: Thu, 27 Mar 2014 13:58:57 +0900
Message-ID: <28590.1395896337@jrobl>
References: <20140319152007.GF7642@w-fr-zakariae> <3324.1395292633@jrobl> <20140326190002.GB20615@w-fr-zakariae>
Cc: "miklos@szeredi.hu" <miklos@szeredi.hu>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
To: Zakaria ElQotbi <zakaria.elqotbi@redbend.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail03-md.ns.itscom.net ([175.177.155.113]:56803 "EHLO
	mail03-md.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750879AbaC0E7A (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 27 Mar 2014 00:59:00 -0400
In-Reply-To: <20140326190002.GB20615@w-fr-zakariae>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>


Zakaria ElQotbi:
> Thanks for your feedback. Below another patch that set the inode_security_struct
> correctly with help of security API.

I don't know much about LSM, but don't we need to acquire i_mutex to
get/set (actually notify) i_security?


J. R. Okajima