From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alex Riesen <raa.lkml@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Fix set_work_tree on cygwin
Date: Thu, 2 Aug 2007 22:36:37 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708022230070.14781@racer.site> (raw)
In-Reply-To: <7vwswdtz98.fsf@assigned-by-dhcp.cox.net>
Hi,
On Thu, 2 Aug 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Hi,
> >
> > On Thu, 2 Aug 2007, Alex Riesen wrote:
> >
> >> Johannes Schindelin, Thu, Aug 02, 2007 17:38:37 +0200:
> >>
> >> > On Thu, 2 Aug 2007, Alex Riesen wrote:
> >> >
> >> > >@@ -209,7 +209,8 @@ const char *set_work_tree(const char *dir)
> >> > > len = strlen(dir);
> >> > > if (len > postfix_len && !strcmp(dir + len - postfix_len,
> >> > > "/" DEFAULT_GIT_DIR_ENVIRONMENT)) {
> >> > >- strncpy(dir_buffer, dir, len - postfix_len);
> >> > >+ strncpy(dir_buffer, dir, len - postfix_len);
> >> > >+ dir_buffer[len - postfix_len] = '\0';
> >> > >
> >> > > /* are we inside the default work tree? */
> >> > > rel = get_relative_cwd(buffer, sizeof(buffer), dir_buffer);
> >> >
> >> > Darn, darn, darn. strncpy does _not_ NUL terminate. I keep forgetting
> >> > that.
> >> >
> >> > Better use strlcpy()?
> >>
> >> Of course, but it just should not be needed at all: static supposed to
> >> be zeroed.
> >
> > Certainly. But reality outweighs theory, and so I Ack either your patch
> > or replacing it by strlcpy().
>
> Static is supposed to be zeroed and also is supposed to retain
> the value from the previous call. I am guessing from the change
> to make "rel" to non-static that this function is called twice
> perhaps?
Apparently (but I would feel safer with strlcpy() anyway). git-read-tree
is the first and only offender which comes up in the test suite:
-- snipsnap --
[PATCH] read-tree: remove unnecessary call to setup_git_directory()
read-tree is already marked with RUN_SETUP in git.c, so there is
no need to call setup_git_directory() a second time.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
builtin-read-tree.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/builtin-read-tree.c b/builtin-read-tree.c
index 41f8110..a3b17a3 100644
--- a/builtin-read-tree.c
+++ b/builtin-read-tree.c
@@ -97,7 +97,6 @@ int cmd_read_tree(int argc, const char **argv, const char *unused_prefix)
memset(&opts, 0, sizeof(opts));
opts.head_idx = -1;
- setup_git_directory();
git_config(git_default_config);
newfd = hold_locked_index(&lock_file, 1);
--
1.5.3.rc3.121.g7f37
next prev parent reply other threads:[~2007-08-02 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 15:25 [PATCH] Fix set_work_tree on cygwin Alex Riesen
2007-08-02 15:38 ` Johannes Schindelin
2007-08-02 20:49 ` Alex Riesen
2007-08-02 21:04 ` Johannes Schindelin
2007-08-02 21:14 ` Junio C Hamano
2007-08-02 21:36 ` Johannes Schindelin [this message]
2007-08-02 21:43 ` Junio C Hamano
2007-08-02 22:04 ` [PATCH] Allow setup_work_tree() to be called several times Johannes Schindelin
2007-08-02 22:02 ` [PATCH] Fix unterminated string copy in set_work_tree Alex Riesen
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=Pine.LNX.4.64.0708022230070.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=raa.lkml@gmail.com \
/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).