git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] entry.c: use dir-iterator to avoid explicit dir traversal

From
Ootalpster <otalpster@gmail.com>
Date
Dec 16, 2019, 16:12 UTC
Message-ID
<CAEKpa1QqrxyS1jeAUoSEAM2bC5h+trPJc_Mm1M18NVA73sCWKQ@mail.gmail.com>
In-Reply-To
<CAHd-oW5tVNP=yNZqPANkk4JLWKJyPkb4g4AeUerrd1O=xdLKXQ@mail.gmail.com>

On Tue, Dec 10, 2019 at 6:38 AM Matheus Tavares Bernardino <matheus.bernardino@usp.br> wrote:

Show 45 quoted lines
>
> On Mon, Dec 9, 2019 at 6:18 PM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:
> >
> > >> The changes pass the test suite t/ and Travis CI.
> > >> Please point out any mistakes.
> > >> ...
> > >> -               strbuf_addch(path, '/');
> > >> -               strbuf_addstr(path, de->d_name);
> > >> -               if (lstat(path->buf, &st))
> > >> -                       die_errno("cannot lstat '%s'", path->buf);
> > >> -               if (S_ISDIR(st.st_mode))
> > >> -                       remove_subtree(path);
> > >> -               else if (unlink(path->buf))
> > >> -                       die_errno("cannot unlink '%s'", path->buf);
> > >> -               strbuf_setlen(path, origlen);
> > >> +               if (unlink(iter->path.buf)) {
> > >
> > > unlink()-ing a directory in Linux will return a EISDIR error. So I
> > > think you still need to use S_ISDIR() to check if iter->path.buf is a
> > > directory and call rmdir(), in this case.
> > >
> > > However, note that the dir-iterator API gives entries in pre-order.
> > > I.e. a directory appears before its subentries. In the use case of
> > > remove_subtree(), though, we need to traverse in post-order, since we
> > > have to remove the subentries before removing the directory where they
> > > reside. My suggestion is that you add a preliminary patch,
> > > implementing a new DIR_ITERATOR_POST_ORDER flag to dir-iterator.h, and
> > > then use it in this patch.
> >
> > Thanks for a review and a few hints to nudge a new contributor in
> > the right direction.  Very much appreciated.
> >
> > I wonder why the bugs in this patch weren't caught by self test we
> > already have, by the way.  We need a bit better test coverage,
> > perhaps?
>
> I think there is no current test that covers remove_subtree() being
> called with nested directories. But we could use the test proposed by
> Daniel[1], which does fail when this current patch is applied. So,
> maybe, Plato could also include this test in v2, before performing the
> dir-iterator convertion.
>
> [1]: https://public-inbox.org/git/1493226219-33423-3-git-send-email-bnmvco@gmail.com/

Hello! Thanks for the warm welcome and sorry for the late reply. Your review and hints you provided were very helpful and appreciated.

Yes, I can work and include the test in v2, as well as performing the dir-iterator conversion. The required process and the necessary changes I need to make were very clear.

This week I'm very busy. I'll work on this in great detail from next week.

Thanks, Plato

Previous: Matheus Tavares Bernardino
Message 6 of 6 in “entry.c: use dir-iterator to avoid explicit dir traversal”
  1. entry.c: use dir-iterator to avoid explicit dir traversalotalpster@gmail.com, Dec 8, 2019
  2. Derrick StoleeDec 9, 2019
  3. Matheus Tavares BernardinoDec 9, 2019
  4. Junio C HamanoDec 9, 2019
  5. Matheus Tavares BernardinoDec 10, 2019
  6. otalpsterDec 16, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.