mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: Some questions
Date: Tue, 1 May 2018 12:34:13 +1000	[thread overview]
Message-ID: <CAEg67GmbDfovHHUUXzvZL6CLZOZBssZox4fD9+wQLdiEzHW5_w@mail.gmail.com> (raw)
In-Reply-To: <20180430153112.GL1392@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

On Tue, May 1, 2018 at 1:31 AM, Rich Felker <dalias@libc.org> wrote:
> On Mon, Apr 30, 2018 at 03:29:39PM +1000, Patrick Oppenlander wrote:
>> Actually, my biggest issue with getcwd is that it allocates a PATH_MAX
>> sized buffer on the stack. That's painful on deeply embedded stuff.
>
> That's unrelated, and could/should be fixed by the attached patch I
> think.

Unfortunately that fails to build on arm with:

src/unistd/getcwd.c: In function 'getcwd':
src/unistd/getcwd.c:25:1: error: r7 cannot be used in asm here

I was also having a go at resolving the stack & the buffer size issue
and came up with the attached (untested) patch.

Patrick

[-- Attachment #2: getcwd2.diff --]
[-- Type: text/x-patch, Size: 1208 bytes --]

diff --git a/src/unistd/getcwd.c b/src/unistd/getcwd.c
index 103fbbb5..306dbc4f 100644
--- a/src/unistd/getcwd.c
+++ b/src/unistd/getcwd.c
@@ -3,17 +3,10 @@
 #include <limits.h>
 #include <string.h>
 #include "syscall.h"
+#include "libc.h"
 
-char *getcwd(char *buf, size_t size)
+static char *do_getcwd(char *buf, size_t size)
 {
-	char tmp[PATH_MAX];
-	if (!buf) {
-		buf = tmp;
-		size = PATH_MAX;
-	} else if (!size) {
-		errno = EINVAL;
-		return 0;
-	}
 	long ret = syscall(SYS_getcwd, buf, size);
 	if (ret < 0)
 		return 0;
@@ -21,5 +14,37 @@ char *getcwd(char *buf, size_t size)
 		errno = ENOENT;
 		return 0;
 	}
-	return buf == tmp ? strdup(buf) : buf;
+	return buf;
+}
+
+static char *getcwd_glibc(size_t size)
+{
+	char tmp[PATH_MAX];
+	if (!do_getcwd(tmp, sizeof tmp))
+		return 0;
+	size_t len = strlen(tmp) + 1;
+	if (!size)
+		size = len;
+	else if (size < len) {
+		errno = ERANGE;
+		return 0;
+	}
+	char *buf = malloc(size);
+	if (!buf) {
+		errno = ENOMEM;
+		return 0;
+	}
+	memcpy(buf, tmp, len);
+	return buf;
+}
+
+char *getcwd(char *buf, size_t size)
+{
+	if (!buf)
+		return getcwd_glibc(size);
+	if (!size) {
+		errno = EINVAL;
+		return 0;
+	}
+	return do_getcwd(buf, size);
 }

  reply	other threads:[~2018-05-01  2:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30  2:52 Patrick Oppenlander
2018-04-30  3:16 ` Rich Felker
2018-04-30  3:55   ` Patrick Oppenlander
2018-04-30 15:35     ` Rich Felker
2018-05-01  2:35       ` Patrick Oppenlander
2018-05-01 21:03         ` Rich Felker
2018-05-01 22:14           ` Patrick Oppenlander
2018-04-30  5:17   ` Patrick Oppenlander
2018-04-30 15:29     ` Rich Felker
2018-05-01  2:32       ` Patrick Oppenlander
2018-04-30  5:29   ` Patrick Oppenlander
2018-04-30 15:31     ` Rich Felker
2018-05-01  2:34       ` Patrick Oppenlander [this message]
2018-05-01 15:52         ` Rich Felker
2018-05-01 17:35           ` Rich Felker
2018-05-01 21:49             ` Andre McCurdy
2018-05-01 22:14               ` Szabolcs Nagy
2018-05-02 13:42                 ` Rich Felker
2018-05-01  0:10   ` Patrick Oppenlander
2018-05-01 14:19     ` Szabolcs Nagy
2018-05-01 21:05     ` Rich Felker

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=CAEg67GmbDfovHHUUXzvZL6CLZOZBssZox4fD9+wQLdiEzHW5_w@mail.gmail.com \
    --to=patrick.oppenlander@gmail.com \
    --cc=musl@lists.openwall.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://git.vuxu.org/mirror/musl/

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).