bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: bug-gnulib@gnu.org
Subject: Re: [patch] glob: resolve DT_UNKNOWN via is_dir
Date: Wed, 17 Nov 2021 12:12:20 +0100	[thread overview]
Message-ID: <87y25n6nor.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <xnsfvv30on.fsf@greed.delorie.com> (DJ Delorie's message of "Tue,  16 Nov 2021 22:45:12 -0500")

* DJ Delorie:

> diff --git a/lib/glob.c b/lib/glob.c
> index 22c459574..d0521bb4a 100644
> --- a/lib/glob.c
> +++ b/lib/glob.c
> @@ -1381,7 +1381,26 @@ glob_in_dir (const char *pattern, const char *directory, int flags,
>                if (flags & GLOB_ONLYDIR)
>                  switch (readdir_result_type (d))
>                    {
> -                  case DT_DIR: case DT_LNK: case DT_UNKNOWN: break;
> +                  case DT_DIR: case DT_LNK: break;
> +		  case DT_UNKNOWN:
> +		    {
> +		      /* The filesystem was too lazy to give us a hint,
> +			 so we have to do it the hard way.  */
> +		      char *fullpath, *p;
> +		      bool isdir;
> +		      fullpath = malloc (strlen (directory) + strlen (d.name) + 2);
> +		      if (fullpath == NULL)
> +			/* This matches old behavior wrt DT_UNKNOWN.  */
> +			break;

Shouldn't this report memory allocation failure to the caller?

Thanks,
Florian



  reply	other threads:[~2021-11-17 11:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  3:45 [patch] glob: resolve DT_UNKNOWN via is_dir DJ Delorie
2021-11-17 11:12 ` Florian Weimer [this message]
2021-11-17 21:59   ` DJ Delorie
2021-11-17 22:14     ` Florian Weimer
2021-11-17 22:38       ` DJ Delorie
2022-03-11 21:43 ` [patch v2] " DJ Delorie
2022-03-12  0:37   ` Paul Eggert
2022-03-23  4:34     ` DJ Delorie
2022-03-23 17:35       ` Paul Eggert
2022-03-25 19:18         ` DJ Delorie
2022-05-14 20:34         ` Bruno Haible

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: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y25n6nor.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=bug-gnulib@gnu.org \
    --cc=dj@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).