linux-kernel - Re: [PATCH 2/2] revoke: change revoke_table to fileset and revoke

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070503132253.7b6fe5fe.akpm@linux-foundation.org>
Date:	Thu, 3 May 2007 13:22:53 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Pekka J Enberg <penberg@...helsinki.fi>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] revoke: change revoke_table to fileset and
 revoke_details

On Thu, 3 May 2007 17:53:07 +0300 (EEST)
Pekka J Enberg <penberg@...helsinki.fi> wrote:

> From: Pekka Enberg <penberg@...helsinki.fi>
> 
> The revoke_table struct is overloaded because it serves two purposes:
> it manages the pre-allocated set of files and tracks the revoke
> operation so that we know where to start restore if the operation
> fails. This splits file set management to separate struct fileset and
> renames struct revoke_table to revoke_details.
> 
> Signed-off-by: Pekka Enberg <penberg@...helsinki.fi>
> ---
>  fs/revoke.c |  171 +++++++++++++++++++++++++++++++++++-------------------------
>  1 file changed, 101 insertions(+), 70 deletions(-)
> 
> Index: 26-mm/fs/revoke.c
> ===================================================================
> --- 26-mm.orig/fs/revoke.c	2007-05-03 17:10:56.000000000 +0300
> +++ 26-mm/fs/revoke.c	2007-05-03 17:14:49.000000000 +0300
> @@ -18,19 +18,71 @@  * Copyright (C) 2006-2007  Pekka Enberg
>  #include <linux/revoked_fs_i.h>
>  #include <linux/syscalls.h>
>  
> -/*
> - * This is used for pre-allocating an array of file pointers so that we don't
> - * have to do memory allocation under tasklist_lock.
> +/**
> + * fileset - an array of file pointers.
> + * @files:    the array of file pointers
> + * @nr:               number of elements in the array
> + * @end:      index to next unused file pointer
> + */
> +struct fileset {
> +	struct file	**files;
> +	unsigned long	nr;
> +	unsigned long	end;
> +};

What's the locking protocol for all this?

> +static void free_fset(struct fileset *fset)
> +{
> +      int i;
> +
> +      for (i = fset->end; i < fset->nr; i++)
> +              fput(fset->files[i]);
> +
> +      kfree(fset->files);
> +      kfree(fset);
> +}

Confused.  Shouldn't it be

	for (i = 0; i < fset->end; i++)

?

-
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/