From: Aristeu Rozanski <aris@redhat.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH] n_tty_read: check for hanging tty while waiting for input
Date: Wed, 18 Feb 2015 09:58:06 -0500 [thread overview]
Message-ID: <20150218145805.GD13666@redhat.com> (raw)
In-Reply-To: <54E3C21E.3000301@hurleysoftware.com>
Hi Peter,
On Tue, Feb 17, 2015 at 05:35:10PM -0500, Peter Hurley wrote:
> I realize that. But hanging up the tty that is /dev/console only affects
> open descriptors that are not /dev/console.
>
> So readers using the /dev/ttyS0 file descriptor will see a hungup fops,
> but readers using /dev/console will not, and /dev/ttyS0 will _not_
> be closed or released because of the still-open descriptor on /dev/console.
I see.
> Ok, so the process sleeping on /dev/console read() should have received
> SIGHUP, which would wake the process and cause it to exit the
> n_tty_read() loop, thus dropping the ldisc reference it holds.
> Did it ignore the signal or perhaps the signal is masked?
Not masked on the test case (attached). Sent sighup manually and it did
receive it.
--
Aristeu
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <termios.h>
#include <errno.h>
#include <signal.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/wait.h>
#include <fcntl.h>
#include <sys/ioctl.h>
static char *default_console = "/dev/console";
static char *default_tty = "/dev/ttyS0";
struct data {
char *console;
char *tty;
};
static void *reader(void *d)
{
struct data *data = (struct data *)d;
struct termios old_termio;
char buff[512];
int fd = -1, rc;
while (1) {
if (fd == -1) {
fd = open(data->console, O_RDWR);
if (fd < 0)
exit(1);
if (tcgetattr(fd, &old_termio) == -1)
exit(1);
old_termio.c_lflag = ICANON;
if (tcsetattr(fd, 0, &old_termio) == -1)
exit(1);
}
rc = read(fd, buff, sizeof(buff));
if (rc < 0 && errno == EAGAIN)
continue;
close(fd);
fd = -1;
}
}
void launch(void *(*fn)(void *), struct data *data)
{
if (fork() == 0)
fn(data);
}
int main(int argc, char *argv[])
{
struct data data;
int fd;
fd = open("/dev/ttyS0", O_RDWR);
close(0);
close(1);
close(2);
ioctl(fd, TIOCSCTTY, 1);
data.console = default_console;
data.tty = default_tty;
launch(reader, &data);
waitpid(-1, NULL, 0);
return 0;
}
next prev parent reply other threads:[~2015-02-18 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 21:06 Aristeu Rozanski
2015-02-17 21:28 ` Peter Hurley
2015-02-17 21:50 ` Aristeu Rozanski
2015-02-17 22:35 ` Peter Hurley
2015-02-18 14:58 ` Aristeu Rozanski [this message]
2015-02-18 15:40 ` Peter Hurley
2015-02-18 15:56 ` Aristeu Rozanski
2015-02-18 16:38 ` Peter Hurley
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=20150218145805.GD13666@redhat.com \
--to=aris@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.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
Powered by JetHome