From: Richard Weinberger <richard@nod.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jslaby@suse.cz, user-mode-linux-devel@lists.sourceforge.net,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, alan@linux.intel.com, kzak@redhat.com
Subject: Re: um: TTY fixes (?)
Date: Tue, 05 Jun 2012 01:14:41 +0200 [thread overview]
Message-ID: <4FCD4161.7060409@nod.at> (raw)
In-Reply-To: <20120604221731.5e378fc2@pyramind.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Am 04.06.2012 23:17, schrieb Alan Cox:
>> On all other ttys login works but bash dies because of of -EIO.
>> After vhangup() the tty returns -EIO upon read()/write().
>
> You can't re-open the tty because a process is holding on to it, not
> closing it and not killable. Fedora shouldn't be holding these devices
> open this way. The behaviour we have of refusing to reopen them why this
> is the case is both a) what the spec seems to say b) good security.
Hmm, there seems to be a bug in util-linux's login.
login-utils/login.c::init_tty() does:
...
/* Kill processes left on this tty */
tcsetattr(0, TCSAFLUSH, &ttt);
signal(SIGHUP, SIG_IGN); /* so vhangup() wont kill us */
vhangup();
signal(SIGHUP, SIG_DFL);
/* open stdin,stdout,stderr to the tty */
open_tty(cxt->tty_path);
/* restore tty modes */
tcsetattr(0, TCSAFLUSH, &tt);
...
By calling vhangup() it kills all other programs on the current tty.
open_tty() opens the tty again but it's still open because stdin, stdout and stderr
belongs to it.
If I add:
fclose(stdin);
fclose(stdout);
fclose(stderr);
before the call to vhangup() login works like charm. :-)
Karel, what do you think?
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-06-04 23:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 20:27 um: TTY fixes (?) Richard Weinberger
2012-06-04 20:27 ` [PATCH 1/6] TTY: um/line, add tty_port Richard Weinberger
2012-06-04 20:27 ` [PATCH 2/6] TTY: um/line, use tty from tty_port Richard Weinberger
2012-06-04 20:27 ` [PATCH 3/6] um: remove line_ioctl() Richard Weinberger
2012-06-04 20:27 ` [PATCH 4/6] um: Remove dead code Richard Weinberger
2012-06-04 20:27 ` [PATCH 5/6] um: fully use tty_port Richard Weinberger
2012-06-04 20:47 ` Jiri Slaby
2012-06-04 20:27 ` [PATCH 6/6] um: remove count_lock Richard Weinberger
2012-06-04 21:17 ` um: TTY fixes (?) Alan Cox
2012-06-04 23:14 ` Richard Weinberger [this message]
2012-06-05 10:41 ` Karel Zak
2012-06-05 11:15 ` Alan Cox
2012-06-05 12:20 ` Richard Weinberger
2012-06-05 15:17 ` Karel Zak
2012-07-12 14:49 ` Karel Zak
2012-07-12 15:01 ` Richard Weinberger
2012-06-06 23:17 ` Richard Weinberger
2012-06-07 9:19 ` Alan Cox
2012-06-07 9:06 ` Richard Weinberger
2012-06-06 14:20 ` [uml-devel] " Boaz Harrosh
2012-06-07 7:35 ` Boaz Harrosh
2012-06-07 7:43 ` Boaz Harrosh
2012-06-07 8:45 ` Richard Weinberger
2012-06-07 9:22 ` Alan Cox
2012-06-07 10:14 ` Boaz Harrosh
2012-06-07 10:19 ` Richard Weinberger
2012-06-07 10:35 ` Boaz Harrosh
2012-06-07 10:52 ` Alan Cox
2012-06-07 13:41 ` Boaz Harrosh
2012-06-07 15:18 ` Richard Weinberger
2012-06-07 16:37 ` Alan Cox
2012-06-07 16:32 ` Richard Weinberger
2012-06-07 16:50 ` Alan Cox
2012-06-07 16:41 ` Richard Weinberger
2012-06-07 17:26 ` Alan Cox
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=4FCD4161.7060409@nod.at \
--to=richard@nod.at \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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