From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jean-Noël AVILA" <avila.jn@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] attr: fix off-by-one directory component length calculation
Date: Wed, 16 Jan 2013 08:08:03 +0700 [thread overview]
Message-ID: <CACsJy8Bn4GKJzi4n5cMPp+26dovT795nUqcXGNLgapf+r_PFCw@mail.gmail.com> (raw)
In-Reply-To: <7vwqve2qk3.fsf@alter.siamese.dyndns.org>
On Wed, Jan 16, 2013 at 2:29 AM, Junio C Hamano <gitster@pobox.com> wrote:
> "Jean-Noël AVILA" <avila.jn@gmail.com> writes:
>
>> Thank you for the explanation.
>>
>> I did not monitor the system calls when writing that patch.
>> Where is the perf framework?
>>
>> As the mistake is located in the "find_basename" function, I would propose a
>> fix directly into it so that the output fits what the other functions expect.
>
> Isn't that a crazy semantics for the function, though? I would
> expect find_basename("/a/path/to/file") to return "file", not
Actually I'd like to remove that function. The function is called twice:
- collect_all_attrs
+ prepare_attr_stack
* find_basename
+ find_basename
which could be reordered to
- collect_all_attrs
+ find_basename
+ prepare_attr_stack (modified to take dirlen from caller)
and because that'll be the only place find_basename is used, we could
just inline the code there.
--
Duy
next prev parent reply other threads:[~2013-01-16 1:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 13:35 [PATCH] attr: fix off-by-one directory component length calculation Nguyễn Thái Ngọc Duy
2013-01-15 16:17 ` Junio C Hamano
2013-01-15 19:14 ` Jean-Noël AVILA
2013-01-15 19:29 ` Junio C Hamano
2013-01-15 19:53 ` Jean-Noël AVILA
2013-01-15 20:49 ` Junio C Hamano
2013-01-15 23:24 ` Jeff King
2013-01-16 6:15 ` t9902 fails (Was: [PATCH] attr: fix off-by-one directory component length calculation) Torsten Bögershausen
2013-01-17 22:47 ` Jean-Noël AVILA
2013-01-18 0:04 ` Jonathan Nieder
2013-01-18 0:12 ` t9902 fails Junio C Hamano
2013-01-18 5:20 ` t9902 fails (Was: [PATCH] attr: fix off-by-one directory component length calculation) Torsten Bögershausen
2013-01-18 16:49 ` t9902 fails Junio C Hamano
2013-01-18 20:15 ` Junio C Hamano
2013-01-18 22:23 ` Jean-Noël AVILA
2013-01-18 22:37 ` Junio C Hamano
2013-01-18 22:57 ` Junio C Hamano
2013-01-19 5:38 ` Torsten Bögershausen
2013-01-19 7:52 ` Re* " Junio C Hamano
2013-01-19 8:00 ` [PATCH 1/2] help: include <common-cmds.h> only in one file Junio C Hamano
2013-01-19 8:02 ` [PATCH 2/2] help --standard: list standard commands Junio C Hamano
2013-01-19 10:32 ` Jean-Noël AVILA
2013-01-19 13:43 ` Re* t9902 fails Jean-Noël AVILA
2013-01-19 10:23 ` Jean-Noël AVILA
2013-01-16 1:08 ` Duy Nguyen [this message]
2013-01-16 2:09 ` [PATCH] attr: fix off-by-one directory component length calculation Duy Nguyen
2013-01-16 2:33 ` Junio C Hamano
2013-01-16 3:12 ` Duy Nguyen
2013-01-16 5:35 ` Junio C Hamano
2013-01-16 6:02 ` Duy Nguyen
2013-01-16 19:07 ` Junio C Hamano
2013-01-16 1:03 ` Duy Nguyen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8Bn4GKJzi4n5cMPp+26dovT795nUqcXGNLgapf+r_PFCw@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=avila.jn@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).