This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Tue, Aug 09, 2016 at 04:39:37PM -0500, Serge E. Hallyn wrote:
[...]
> --- a/sysdeps/unix/sysv/linux/ttyname.c
> +++ b/sysdeps/unix/sysv/linux/ttyname.c
[...]
> + /* If the link doesn't exist, then it points to a device in another
> + namespace. If it is a UNIX98 pty, then return the /proc/self
> + fd, as it points to a name unreachable in our namespace. */
> + if (is_pty (&st) && strlen (procname) < buflen - 1)
> + return strcpy (ttyname_buf, procname);
With buflen == 4095 and sizeof(procname) == 30, this buflen check looks
redundant. To keep the safe side, I'd rather add a static assert instead,
e.g.
#define TTYNAME_BUFLEN 4095
...
buflen = TTYNAME_BUFLEN;
...
_Static_assert (sizeof (procname) < TTYNAME_BUFLEN, "buflen too small");
[...]
> --- a/sysdeps/unix/sysv/linux/ttyname_r.c
> +++ b/sysdeps/unix/sysv/linux/ttyname_r.c
[...]
> + /* If the link doesn't exist, then it points to a device in another
> + namespace. If it is a UNIX98 pty, then return the /proc/self
> + fd, as it points to a name unreachable in our namespace. */
> + if (is_pty (&st) && strlen (procname) < buflen - 1)
> + {
> + strcpy (buf, procname);
> + return 0;
> + }
Unlike ttyname.c, here buflen might be quite small, and this code skips
strlen (procname) == buflen - 1. Shouldn't it rather be
strlen (procname) < buflen ?
If is_pty(&st) is true but buflen is too small for procname, is there any
chance of finding the device using getttyname_r? Shouldn't ttyname_r fail
with ERANGE instead?
--
ldv
Attachment:
pgprNvuWx8awV.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |