git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 2/7] move setting of object->type to alloc_* functions
Date: Sat, 12 Jul 2014 15:44:06 +0100	[thread overview]
Message-ID: <53C149B6.7010705@ramsay1.demon.co.uk> (raw)
In-Reply-To: <20140711084611.GB5625@sigill.intra.peff.net>

On 11/07/14 09:46, Jeff King wrote:
> The "struct object" type implements basic object
> polymorphism.  Individual instances are allocated as
> concrete types (or as a union type that can store any
> object), and a "struct object *" can be cast into its real
> type after examining its "type" enum.  This means it is
> dangerous to have a type field that does not match the
> allocation (e.g., setting the type field of a "struct blob"
> to "OBJ_COMMIT" would mean that a reader might read past the
> allocated memory).
> 
> In most of the current code this is not a problem; the first
> thing we do after allocating an object is usually to set its
> type field by passing it to create_object. However, the
> virtual commits we create in merge-recursive.c do not ever
> get their type set. This does not seem to have caused
> problems in practice, though (presumably because we always
> pass around a "struct commit" pointer and never even look at
> the type).
> 
> We can fix this oversight and also make it harder for future
> code to get it wrong by setting the type directly in the
> object allocation functions.
> 
> This will also make it easier to fix problems with commit
> index allocation, as we know that any object allocated by
> alloc_commit_node will meet the invariant that an object
> with an OBJ_COMMIT type field will have a unique index
> number.
> 
> Signed-off-by: Jeff King <peff@peff.net>
> ---
>  alloc.c         | 18 ++++++++++--------
>  blob.c          |  2 +-
>  builtin/blame.c |  1 -
>  commit.c        |  2 +-
>  object.c        |  5 ++---
>  object.h        |  2 +-
>  tag.c           |  2 +-
>  tree.c          |  2 +-
>  8 files changed, 17 insertions(+), 17 deletions(-)
> 
> diff --git a/alloc.c b/alloc.c
> index d7c3605..fd5fcb7 100644
> --- a/alloc.c
> +++ b/alloc.c
> @@ -18,11 +18,11 @@
>  
>  #define BLOCKING 1024
>  
> -#define DEFINE_ALLOCATOR(name, type)				\
> +#define DEFINE_ALLOCATOR(name, flag, type)			\
>  static struct alloc_state name##_state;				\
>  void *alloc_##name##_node(void)					\
>  {								\
> -	return alloc_node(&name##_state, sizeof(type));		\
> +	return alloc_node(&name##_state, flag, sizeof(type));	\
>  }

I don't particularly like 'flag' here. (not a massive dislike, mind you:)

Perhaps: flag->object_type, type->node_type?
Or, if that's too verbose, maybe just: flag->type, type->node?

ATB,
Ramsay Jones

  reply	other threads:[~2014-07-12 14:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 23:59 [PATCH v3 2/2] alloc.c: remove the redundant commit_count variable Ramsay Jones
2014-07-11  0:30 ` Jeff King
2014-07-11  0:59   ` Ramsay Jones
2014-07-11  8:32     ` Jeff King
2014-07-11  9:41       ` Ramsay Jones
2014-07-11  8:41   ` [PATCH 0/7] ensure index is set for all OBJ_COMMIT objects variable Jeff King
2014-07-11  8:42     ` [PATCH 1/7] alloc.c: remove the alloc_raw_commit_node() function Jeff King
2014-07-11  8:46     ` [PATCH 2/7] move setting of object->type to alloc_* functions Jeff King
2014-07-12 14:44       ` Ramsay Jones [this message]
2014-07-12 18:05         ` Jeff King
2014-07-13  6:41           ` Jeff King
2014-07-13  6:41             ` [PATCH v2 1/8] alloc.c: remove the alloc_raw_commit_node() function Jeff King
2014-07-15 20:06               ` Junio C Hamano
2014-07-13  6:41             ` [PATCH v2 2/8] alloc: write out allocator definitions Jeff King
2014-07-15 20:11               ` Junio C Hamano
2014-07-13  6:41             ` [PATCH v2 3/8] move setting of object->type to alloc_* functions Jeff King
2014-07-15 20:12               ` Junio C Hamano
2014-07-13  6:42             ` [PATCH v2 4/8] parse_object_buffer: do not set object type Jeff King
2014-07-13  6:42             ` [PATCH v2 5/8] add object_as_type helper for casting objects Jeff King
2014-07-13  6:42             ` [PATCH v2 6/8] alloc: factor out commit index Jeff King
2014-07-13  6:42             ` [PATCH v2 7/8] object_as_type: set " Jeff King
2014-07-13  6:42             ` [PATCH v2 8/8] diff-tree: avoid lookup_unknown_object Jeff King
2014-07-13 19:27             ` [PATCH 2/7] move setting of object->type to alloc_* functions Ramsay Jones
2014-07-14  5:57               ` Jeff King
2014-07-14 11:03                 ` Ramsay Jones
2014-07-12 14:55       ` Ramsay Jones
2014-07-12 18:07         ` Jeff King
2014-07-11  8:46     ` [PATCH 3/7] parse_object_buffer: do not set object type Jeff King
2014-07-11  8:48     ` [PATCH 4/7] add object_as_type helper for casting objects Jeff King
2014-07-11 10:45       ` Ramsay Jones
2014-07-11 16:59         ` Jeff King
2014-07-11  8:48     ` [PATCH 5/7] alloc: factor out commit index Jeff King
2014-07-11  8:49     ` [PATCH 6/7] object_as_type: set " Jeff King
2014-07-11  8:50     ` [PATCH 7/7] diff-tree: avoid lookup_unknown_object Jeff King
2014-07-11 10:31     ` [PATCH 0/7] ensure index is set for all OBJ_COMMIT objects variable Ramsay Jones

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=53C149B6.7010705@ramsay1.demon.co.uk \
    --to=ramsay@ramsay1.demon.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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;
as well as URLs for NNTP newsgroup(s).