public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Serge E. Hallyn" <serge@hallyn.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] linux ttyname and ttyname_r: return link if appropriate
Date: Wed, 10 Aug 2016 23:24:00 -0000	[thread overview]
Message-ID: <20160810232430.GB20138@mail.hallyn.com> (raw)
In-Reply-To: <20160809232608.GC3835@altlinux.org>

Quoting Dmitry V. Levin (ldv@altlinux.org):
> 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 ?

Hm, yeah that's right.

> 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?

So you mean

	if (is_pty (&st)) {
		if (strlen (procname) < buflen) {
			strcpy (buf, procname);
			return 0;
		}
		return -ERANGE;
	}

?

  reply	other threads:[~2016-08-10 23:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 15:29 [PATCH 1/1] linux ttyname: " Serge Hallyn
2016-04-15 16:27 ` Florian Weimer
2016-04-15 16:47   ` Serge Hallyn
2016-04-15 17:06     ` Florian Weimer
2016-04-15 17:43       ` Serge Hallyn
2016-04-15 18:48         ` Serge Hallyn
2016-04-15 19:59           ` Mike Frysinger
2016-04-18 19:53             ` Serge Hallyn
2016-04-18 19:53             ` [PATCH 1/2] " Serge Hallyn
2016-04-18 20:02               ` Mike Frysinger
2016-04-18 20:23                 ` Serge Hallyn
2016-04-20  2:10                   ` [PATCH] linux ttyname and ttyname_r: " Serge Hallyn
2016-04-20  2:28                     ` Mike Frysinger
2016-04-20 18:51                       ` Serge Hallyn
2016-07-27 13:43                         ` Serge E. Hallyn
2016-07-27 17:28                         ` Dmitry V. Levin
2016-08-06  2:09                           ` Serge E. Hallyn
2016-08-06  8:46                             ` Mike Frysinger
2016-08-06 15:00                               ` Serge E. Hallyn
2016-08-09 20:41                                 ` Serge E. Hallyn
2016-08-09 21:18                                 ` Dmitry V. Levin
2016-08-09 21:39                                   ` Serge E. Hallyn
2016-08-09 23:26                                     ` Dmitry V. Levin
2016-08-10 23:24                                       ` Serge E. Hallyn [this message]
2016-08-10 23:48                                         ` Dmitry V. Levin
2016-08-10  6:38                                     ` Florian Weimer
2016-08-10 23:03                                       ` Serge E. Hallyn
2016-08-10 23:18                                         ` Dmitry V. Levin
2016-08-10 23:26                                           ` Serge E. Hallyn
2016-10-03  6:16                                           ` Serge E. Hallyn
2016-10-03  7:29                                             ` Andreas Schwab
2016-10-03 14:05                                               ` [PATCH 1/1] linux ttyname and ttyname_r: do not return wrong results Serge E. Hallyn
2016-10-04  9:53                                             ` [PATCH] linux ttyname and ttyname_r: return link if appropriate Florian Weimer
2016-10-04 12:47                                               ` Serge E. Hallyn
2016-04-18 19:54             ` [PATCH 2/2] linux " Serge Hallyn
2016-04-18 20:03               ` Mike Frysinger

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=20160810232430.GB20138@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=libc-alpha@sourceware.org \
    /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).