From: Jiri Slaby <jslaby@suse.cz>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
gregkh@linuxfoundation.org, alan@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/10] TTY: switch tty_schedule_flip
Date: Fri, 01 Feb 2013 16:06:17 +0100 [thread overview]
Message-ID: <510BD9E9.9000400@suse.cz> (raw)
In-Reply-To: <1359722247.3381.16.camel@thor.lan>
On 02/01/2013 01:37 PM, Peter Hurley wrote:
> On Thu, 2013-01-03 at 15:53 +0100, Jiri Slaby wrote:
>> Now, we start converting tty buffer functions to actually use
>> tty_port. This will allow us to get rid of the need of tty in many
>> call sites. Only tty_port will needed and hence no more
>> tty_port_tty_get in those paths.
>>
>> This is the last one: tty_schedule_flip
>
> [snip]
>
>> diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c
>> index 5aace4d..a9af1b9a 100644
>> --- a/drivers/tty/vt/keyboard.c
>> +++ b/drivers/tty/vt/keyboard.c
>> @@ -307,26 +307,17 @@ int kbd_rate(struct kbd_repeat *rep)
>> */
>> static void put_queue(struct vc_data *vc, int ch)
>> {
>> - struct tty_struct *tty = vc->port.tty;
>> -
>> tty_insert_flip_char(&vc->port, ch, 0);
>> - if (tty) {
>> - tty_schedule_flip(tty);
>> - }
>> + tty_schedule_flip(&vc->port);
>> }
>>
>> static void puts_queue(struct vc_data *vc, char *cp)
>> {
>> - struct tty_struct *tty = vc->port.tty;
>> -
>> - if (!tty)
>> - return;
>> -
>> while (*cp) {
>> tty_insert_flip_char(&vc->port, *cp, 0);
>> cp++;
>> }
>> - tty_schedule_flip(tty);
>> + tty_schedule_flip(&vc->port);
>> }
>
> Umm. So even though the vt driver knows the tty has been shutdown,
> keystrokes will still be buffered? And then fed to whichever tty happens
> to next get installed on the same port?
Unless I completely missed something, they should be flushed. If that's
not the case, that's a bug. I will check next week.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2013-02-01 15:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 14:53 [PATCH 00/10] TTY: switch flipping functions to tty_port Jiri Slaby
2013-01-03 14:53 ` [PATCH 01/10] TTY: switch tty_buffer_request_room " Jiri Slaby
2013-01-03 14:53 ` [PATCH 02/10] TTY: convert more flipping functions Jiri Slaby
2013-01-03 14:53 ` [PATCH 03/10] TTY: switch tty_insert_flip_char Jiri Slaby
2013-01-03 14:53 ` [PATCH 04/10] TTY: switch tty_insert_flip_string Jiri Slaby
2013-01-03 14:53 ` [PATCH 05/10] TTY: move low_latency to tty_port Jiri Slaby
2013-01-03 14:53 ` [PATCH 06/10] TTY: switch tty_flip_buffer_push Jiri Slaby
2013-01-03 14:53 ` [PATCH 07/10] TTY: switch tty_schedule_flip Jiri Slaby
2013-02-01 12:37 ` Peter Hurley
2013-02-01 15:06 ` Jiri Slaby [this message]
2013-02-01 20:39 ` Peter Hurley
2013-02-05 11:40 ` Jiri Slaby
2013-02-05 14:06 ` Peter Hurley
2013-01-03 14:53 ` [PATCH 08/10] cyclades: push down tty_port_tty_get Jiri Slaby
2013-01-03 14:53 ` [PATCH 09/10] TTY: synclink, remove unneeded tests Jiri Slaby
2013-01-03 14:53 ` [PATCH 10/10] TTY: nozomi, remove dead code Jiri Slaby
2013-01-16 6:47 ` [PATCH 00/10] TTY: switch flipping functions to tty_port Greg KH
2013-01-16 13:37 ` Jiri Slaby
2013-01-16 15:39 ` Greg KH
2013-01-16 15:48 ` Steven Rostedt
2013-01-16 15:44 ` Steven Rostedt
2013-01-16 15:59 ` Jiri Slaby
2013-01-16 16:23 ` Steven Rostedt
2013-01-16 16:42 ` Alan Cox
2013-01-16 16:49 ` Steven Rostedt
2013-01-19 4:52 ` Steven Rostedt
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=510BD9E9.9000400@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--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