[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071222162516.df6fe557.akpm@linux-foundation.org>
Date: Sat, 22 Dec 2007 16:25:16 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Eric Sandeen <sandeen@...hat.com>
Cc: linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
Michael Halcrow <mhalcrow@...ibm.com>, mike@...crow.us,
Jeff Moyer <jmoyer@...hat.com>
Subject: Re: [PATCH] (UPDATED) ecryptfs: check for existing key_tfm at mount
time
On Sat, 22 Dec 2007 11:42:37 -0600 Eric Sandeen <sandeen@...hat.com> wrote:
> Andrew Morton wrote:
>
> > It would all look a lot more solid if this locking was retained and both
> > ecryptfs_tfm_exists() and ecryptfs_add_new_key_tfm() were designed to be
> > called under key_tfm_list_mutex.
>
> Hmm good point, sorry for missing that. How's this look?
key_tfm_list_mutex gets used in fs/ecryptfs/main.c but it is static in
fs/ecryptfs/crypto.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists