tty: fix hang on tty device with no_room set
Subsystems (2)
PATCH v7 1/1 tty: fix hang on tty device with no_room set
From: Hui Li <[email protected]>
We have met a hang on pty device, the reader was blocking at epoll on master side, the writer was sleeping at wait_woken inside n_tty_write on slave side, and the write buffer on tty_port was full, we found that the reader and writer would never be woken again and blocked forever.
The problem was caused by a race between reader and kworker:n_tty_read(reader): n_tty_receive_buf_common(kworker):
copy_from_read_buf()|
|room = N_TTY_BUF_SIZE - (ldata->read_head - tail)
|room <= 0
n_tty_kick_worker() |
|ldata->no_room = trueAfter writing to slave device, writer wakes up kworker to flush data on tty_port to reader, and the kworker finds that reader has no room to store data so room <= 0 is met. At this moment, reader consumes all the data on reader buffer and calls n_tty_kick_worker to check ldata->no_room which is false and reader quits reading. Then kworker sets ldata->no_room=true and quits too.
If write buffer is not full, writer will wake kworker to flush data again after following writes, but if write buffer is full and writer goes to sleep, kworker will never be woken again and tty device is blocked.
This problem can be solved with a check for read buffer size inside n_tty_receive_buf_common, if read buffer is empty and ldata->no_room is true, a call to n_tty_kick_worker is necessary to keep flushing data to reader.
---
Patch changelogs between v1 and v2:
-add barrier inside n_tty_read and n_tty_receive_buf_common; -comment why barrier is needed; -access to ldata->no_room is changed with READ_ONCE and WRITE_ONCE; Patch changelogs between v2 and v3: -in function n_tty_receive_buf_common, add unlikely to check ldata->no_room, eg: if (unlikely(ldata->no_room)), and READ_ONCE is removed here to get locality; -change comment for barrier to show the race condition to make comment easier to understand;
Patch changelogs between v3 and v4:
-change subject from 'tty: fix a possible hang on tty device' to
'tty: fix hang on tty device with no_room set' to make subject more obvious;
Patch changelogs between v4 and v5:
-name is changed from cael to caelli, li is added as the family
name and caelli is the fullname.
Patch changelogs between v5 and v6:
-change from and Signed-off-by, from 'caelli <[email protected]>'
to 'caelli <[email protected]>', later one is my corporate address.
Patch changelogs between v6 and v7:
-change name from caelli to 'Hui Li', which is my name in chinese. -the comment for barrier is improved, and a Fixes and Reviewed-by
tags is added.
drivers/tty/n_tty.c | 41 +++++++++++++++++++++++++++++++++++++---- 1 file changed, 37 insertions(+), 4 deletions(-)
drivers/tty/n_tty.c +42 -4
@@ -204,8 +204,8 @@ static void n_tty_kick_worker(struct tty_struct *tty)struct n_tty_data *ldata = tty->disc_data;/* Did the input worker stop? Restart it */ -if (unlikely (ldata->no_room)) { - ldata->no_room =0 ; +if (unlikely (READ_ONCE (ldata->no_room))) { +WRITE_ONCE (ldata->no_room,0 );WARN_RATELIMIT (tty->port->itty ==NULL ,"scheduling with invalid itty\n" );
@@ -1698,7 +1698,7 @@ n_tty_receive_buf_common(struct tty_struct *tty, const unsigned char *cp,if (overflow && room <0 ) ldata->read_head--; room = overflow; - ldata->no_room = flow && !room; +WRITE_ONCE (ldata->no_room, flow && !room); }else overflow =0 ;
@@ -1729,6 +1729,27 @@ n_tty_receive_buf_common(struct tty_struct *tty, const unsigned char *cp, }else n_tty_check_throttle (tty); +if (unlikely (ldata->no_room)) { +/* +* Barrier here is to ensure to read the latest read_tail in +* chars_in_buffer() and to make sure that read_tail is not loaded +* before ldata->no_room is set, otherwise, following race may occur: +* n_tty_receive_buf_common() +* n_tty_read() +* if (!chars_in_buffer(tty))->false +* copy_from_read_buf() +* read_tail=commit_head +* n_tty_kick_worker() +* if (ldata->no_room)->false +* ldata->no_room = 1 +* Then both kworker and reader will fail to kick n_tty_kick_worker(), +* smp_mb is paired with smp_mb() in n_tty_read(). +*/ +smp_mb (); +if (!chars_in_buffer (tty)) +n_tty_kick_worker (tty); + } +up_read (&tty->termios_rwsem);return rcvd;
@@ -2282,8 +2303,25 @@ static ssize_t n_tty_read(struct tty_struct *tty, struct file *file,if (time) timeout = time; } -if (old_tail != ldata->read_tail) +if (old_tail != ldata->read_tail) { +/* +* Make sure no_room is not read in n_tty_kick_worker() +* before setting ldata->read_tail in copy_from_read_buf(), +* otherwise, following race may occur: +* n_tty_read() +* n_tty_receive_buf_common() +* n_tty_kick_worker() +* if(ldata->no_room)->false +* ldata->no_room = 1 +* if (!chars_in_buffer(tty))->false +* copy_from_read_buf() +* read_tail=commit_head +* Both reader and kworker will fail to kick tty_buffer_restart_work(), +* smp_mb is paired with smp_mb() in n_tty_receive_buf_common(). +*/ +smp_mb ();n_tty_kick_worker (tty); + }up_read (&tty->termios_rwsem);remove_wait_queue (&tty->read_wait, &wait);
Signature · 1 line
2.27.0
Quoted 5 lines · On Fri, Mar 17, 2023 at 10:24:07AM +0800, [email protected] wrote:
We have met a hang on pty device, the reader was blocking at epoll on master side, the writer was sleeping at
wait_wokeninsiden_tty_writeon slave side, and the write buffer ontty_portwas full, we found that the reader and writer would never be woken again and blocked forever.
Where do you find this hanging pty? Seems like the wording makes me confused. Maybe you mean "It is possible to hang pty device. In that case, ..."
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Quoted 11 lines · Bagas Sanjaya
Quoted 5 lines · On Fri, Mar 17, 2023 at 10:24:07AM +0800, [email protected] wrote:
We have met a hang on pty device, the reader was blocking at epoll on master side, the writer was sleeping at
wait_wokeninsiden_tty_writeon slave side, and the write buffer ontty_portwas full, we found that the reader and writer would never be woken again and blocked forever.Where do you find this hanging pty? Seems like the wording makes me confused. Maybe you mean "It is possible to hang pty device. In that case, ..."
Oops, I forgot to Cc: LKML.
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Quoted 3 lines
Where do you find this hanging pty? Seems like the wording makes me confused. Maybe you mean "It is possible to hang pty device. In that case, ..."
Thanks for your reply, I will correct messages like this:
"It is possible to hang pty devices in this case, the reader was blocking at epoll on master side, the writer was ..."
Quoted 19 lines · Bagas Sanjaya <[email protected]> 于2023年4月4日周二 10:55写道:
Quoted 11 lines · Bagas Sanjaya
Quoted 5 lines · On Fri, Mar 17, 2023 at 10:24:07AM +0800, [email protected] wrote:
We have met a hang on pty device, the reader was blocking at epoll on master side, the writer was sleeping at
wait_wokeninsiden_tty_writeon slave side, and the write buffer ontty_portwas full, we found that the reader and writer would never be woken again and blocked forever.Where do you find this hanging pty? Seems like the wording makes me confused. Maybe you mean "It is possible to hang pty device. In that case, ..."
Oops, I forgot to Cc: LKML.
--
An old man doll... just what I always wanted! - Clara