Fix IXANY and restart after signal (e.g. ctrl-C) in n_tty line discipline
PATCH 1/1 Fix IXANY and restart after signal (e.g. ctrl-C) in n_tty line discipline
Here is a patch that fixes a couple of issues with ttys in the stopped state. See patch below for more details.
Note that this patch assumes that my previous patch from last month (called "tty-enable-the-echoing-of-c-in-the-n_tty-discipline.patch" in the -mm tree) has been applied, since part of this patch is adjacent to that code.
Happy holidays! Joe
Fix two N_TTY line discipline issues related to resuming a stopped TTY (typically done with ctrl-S):
1) Fix handling of character that resumes a stopped TTY (with IXANY)
With "stty ixany", the TTY line discipline would lose the first character after the stop, so typing, for example, "hi^Sthere" resulted in "hihere" (the 't' would cause the resume after ^S, but it would then be thrown away rather than processed as an input character). This was inconsistent with the behavior of other Unix systems.
2) Fix interrupt signal (e.g. ctrl-C) behavior in stopped TTYs
With "stty -ixany" (often the default), interrupt signals were ignored in a stopped TTY until the TTY was resumed with the start char (typically ctrl-Q), which was inconsistent with the behavior of other Unix systems.
---
drivers/char/n_tty.c renamed from drivers/char/n_tty.c~tty-fix-ixany-and-restart-after-signal-in-the-n_tty-discipline +3 -4
@@ -695,11 +695,8 @@ static inline void n_tty_receive_char(streturn ; } -if (tty->stopped && !tty->flow_stopped && -I_IXON (tty) &&I_IXANY (tty)) { +if (tty->stopped && !tty->flow_stopped &&I_IXON (tty) &&I_IXANY (tty))start_tty (tty); -return ; - }if (I_ISTRIP (tty)) c &=0x7f ;
@@ -769,6 +766,8 @@ static inline void n_tty_receive_char(st signal =SIGTSTP ;if (c ==SUSP_CHAR (tty)) { send_signal: +if (tty->stopped && !tty->flow_stopped &&I_IXON (tty)) +start_tty (tty);/* * Echo character, and then send the signal. * Note that we do not use isig() here because we want
PATCH 1/1 (*revised*) Fix IXANY and restart after signal (e.g. ctrl-C) in n_tty line discipline
Here is a revised version of my patch, currently in the -mm kernel as "fix-ixany-and-restart-after-signal-eg-ctrl-c-in-n_tty-line-discipline". It fixes a couple of issues with ttys in the stopped state. See patch below for more details.
This patch should *replace* the old version of the patch. It is cleaner, and its behavior better matches that of other Unix platforms. It also avoids needless/redundant calls to start_tty() when ctrl-S or ctrl-Q are hit.
-Joe
Fix two N_TTY line discipline issues related to resuming a stopped TTY (typically done with ctrl-S):
1) Fix handling of character that resumes a stopped TTY (with IXANY)
With "stty ixany", the TTY line discipline would lose the first character after the stop, so typing, for example, "hi^Sthere" resulted in "hihere" (the 't' would cause the resume after ^S, but it would then be thrown away rather than processed as an input character). This was inconsistent with the behavior of other Unix systems.
2) Fix interrupt signal (e.g. ctrl-C) behavior in stopped TTYs
With "stty -ixany" (often the default), interrupt signals were ignored in a stopped TTY until the TTY was resumed with the start char (typically ctrl-Q), which was inconsistent with the behavior of other Unix systems.
---
drivers/char/n_tty.c renamed from drivers/char/n_tty.c~fix-ixany-and-restart-after-signal-eg-ctrl-c-in-n_tty-line-discipline +5 -6
@@ -695,17 +695,16 @@return ; } -if (tty->stopped && !tty->flow_stopped && -I_IXON (tty) &&I_IXANY (tty)) { -start_tty (tty); -return ; - } -if (I_ISTRIP (tty)) c &=0x7f ;if (I_IUCLC (tty) &&L_IEXTEN (tty)) c=tolower (c); +if (tty->stopped && !tty->flow_stopped &&I_IXON (tty) && + ((I_IXANY (tty) && c !=START_CHAR (tty) && c !=STOP_CHAR (tty)) || + c ==INTR_CHAR (tty) || c ==QUIT_CHAR (tty))) +start_tty (tty); +if (tty->closing) {if (I_IXON (tty)) {if (c ==START_CHAR (tty))
Re: [PATCH] (*revised*) Fix IXANY and restart after signal (e.g. ctrl-C) in n_tty line discipline
Quoted 4 lines · On Thu, 17 Jan 2008 16:44:33 -0700 Joe Peterson <[email protected]> wrote:
Here is a revised version of my patch, currently in the -mm kernel as "fix-ixany-and-restart-after-signal-eg-ctrl-c-in-n_tty-line-discipline". It fixes a couple of issues with ttys in the stopped state. See patch below for more details.
What were the "couple of issues"?
Quoted 1 line
This patch should *replace* the old version of the patch.
I don't like replacements a lot. It forces one to re-review the whole thing from scratch. Which is why I almost always turn the replacement into an incremental patch, as below.
Quoted 5 lines
It is
cleaner, and its behavior better matches that of other Unix platforms. It also avoids needless/redundant calls tostart_tty()when ctrl-S or ctrl-Q are hit.
drivers/char/n_tty.c renamed from drivers/char/n_tty.c~fix-ixany-and-restart-after-signal-eg-ctrl-c-in-n_tty-line-discipline-update +5 -5
@@ -695,14 +695,16 @@ static inline void n_tty_receive_char(streturn ; } -if (tty->stopped && !tty->flow_stopped &&I_IXON (tty) &&I_IXANY (tty)) -start_tty (tty); -if (I_ISTRIP (tty)) c &=0x7f ;if (I_IUCLC (tty) &&L_IEXTEN (tty)) c=tolower (c); +if (tty->stopped && !tty->flow_stopped &&I_IXON (tty) && + ((I_IXANY (tty) && c !=START_CHAR (tty) && c !=STOP_CHAR (tty)) || + c ==INTR_CHAR (tty) || c ==QUIT_CHAR (tty))) +start_tty (tty); +if (tty->closing) {if (I_IXON (tty)) {if (c ==START_CHAR (tty))
@@ -766,8 +768,6 @@ static inline void n_tty_receive_char(st signal =SIGTSTP ;if (c ==SUSP_CHAR (tty)) { send_signal: -if (tty->stopped && !tty->flow_stopped &&I_IXON (tty)) -start_tty (tty);/* * Echo character, and then send the signal. * Note that we do not use isig() here because we want
_
Re: [PATCH] (*revised*) Fix IXANY and restart after signal (e.g. ctrl-C) in n_tty line discipline
Quoted 1 line · Andrew Morton
What were the "couple of issues"?
They are the same 2 issues described in the original version of the patch and included in the text of this one too (i.e. the text at the start of this latest patch version is the same as before).
Quoted 5 lines
Quoted 1 line
This patch should *replace* the old version of the patch.
I don't like replacements a lot. It forces one to re-review the whole thing from scratch. Which is why I almost always turn the replacement into an incremental patch, as below.
I see your point. Cool, thanks for making the update patch, and I'll submit them like that in the future.
-Thanks, Joe