From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kees Cook Subject: Re: [PATCH 2/2] ecryptfs: Print inode on metadata error Date: Wed, 11 Jan 2012 12:38:37 -0800 Message-ID: <20120111203837.GS2618@outflux.net> References: <1326301242-5817-1-git-send-email-tim.gardner@canonical.com> <1326301242-5817-3-git-send-email-tim.gardner@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, tyler.hicks@canonical.com, linux-kernel@vger.kernel.org To: Tim Gardner Return-path: Content-Disposition: inline In-Reply-To: <1326301242-5817-3-git-send-email-tim.gardner@canonical.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Jan 11, 2012 at 06:00:42PM +0100, Tim Gardner wrote: > If a lower file system file is corrupted, then ecryptfs prints > a generic and mostly useless log message when attempting to > read metadata. Print the inode associated with the file > so that a user can do something about it, e.g., > > find -inum INODE_NUM > > Cc: linux-kernel@vger.kernel.org > Cc: stable@vger.kernel.org > Cc: Tyler Hicks > Signed-off-by: Tim Gardner Reviewed-by: Kees Cook -Kees -- Kees Cook