From: "J. Bruce Fields" <bfields@fieldses.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
stable@kernel.org
Subject: Re: [PATCH] fs: fix lock initialization
Date: Wed, 6 Jul 2011 14:21:54 -0400 [thread overview]
Message-ID: <20110706182154.GB31214@fieldses.org> (raw)
In-Reply-To: <87iprf3dgs.fsf@tucsk.pomaz.szeredi.hu>
On Wed, Jul 06, 2011 at 12:33:55PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> locks_alloc_lock() assumed that the allocated struct file_lock is
> already initialized to zero members. This is only true for the first
> allocation of the structure, after reuse some of the members will have
> random values.
>
> This will for example result in passing random fl_start values to
> userspace in fuse for FL_FLOCK locks, which is an information leak at
> best.
>
> Fix by reinitializing those members which may be non-zero after freeing.
Could you also just get rid of init_once() while you're at it?
--b.
>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> CC: stable@kernel.org
> ---
> fs/locks.c | 30 ++++++++++++++++++++----------
> 1 file changed, 20 insertions(+), 10 deletions(-)
>
> Index: linux-2.6/fs/locks.c
> ===================================================================
> --- linux-2.6.orig/fs/locks.c 2011-07-04 17:06:01.000000000 +0200
> +++ linux-2.6/fs/locks.c 2011-07-04 17:06:04.000000000 +0200
> @@ -160,10 +160,28 @@ EXPORT_SYMBOL_GPL(unlock_flocks);
>
> static struct kmem_cache *filelock_cache __read_mostly;
>
> +static void locks_init_lock_always(struct file_lock *fl)
> +{
> + fl->fl_next = NULL;
> + fl->fl_fasync = NULL;
> + fl->fl_owner = NULL;
> + fl->fl_pid = 0;
> + fl->fl_nspid = NULL;
> + fl->fl_file = NULL;
> + fl->fl_flags = 0;
> + fl->fl_type = 0;
> + fl->fl_start = fl->fl_end = 0;
> +}
> +
> /* Allocate an empty lock structure. */
> struct file_lock *locks_alloc_lock(void)
> {
> - return kmem_cache_alloc(filelock_cache, GFP_KERNEL);
> + struct file_lock *fl = kmem_cache_alloc(filelock_cache, GFP_KERNEL);
> +
> + if (fl)
> + locks_init_lock_always(fl);
> +
> + return fl;
> }
> EXPORT_SYMBOL_GPL(locks_alloc_lock);
>
> @@ -200,17 +218,9 @@ void locks_init_lock(struct file_lock *f
> INIT_LIST_HEAD(&fl->fl_link);
> INIT_LIST_HEAD(&fl->fl_block);
> init_waitqueue_head(&fl->fl_wait);
> - fl->fl_next = NULL;
> - fl->fl_fasync = NULL;
> - fl->fl_owner = NULL;
> - fl->fl_pid = 0;
> - fl->fl_nspid = NULL;
> - fl->fl_file = NULL;
> - fl->fl_flags = 0;
> - fl->fl_type = 0;
> - fl->fl_start = fl->fl_end = 0;
> fl->fl_ops = NULL;
> fl->fl_lmops = NULL;
> + locks_init_lock_always(fl);
> }
>
> EXPORT_SYMBOL(locks_init_lock);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-06 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 10:33 Miklos Szeredi
2011-07-06 17:40 ` Linus Torvalds
2011-07-06 21:12 ` Matthew Wilcox
2011-07-06 18:21 ` J. Bruce Fields [this message]
2011-07-07 10:19 ` Miklos Szeredi
2011-07-07 11:06 ` Miklos Szeredi
2011-07-09 20:40 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110706182154.GB31214@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®