Re: [PATCH -next 0/9] tty: Fix buffer work access-after-free

From: Ilya Zykov
Date: Mon Dec 10 2012 - 14:00:34 EST


On 04.12.2012 11:07, Peter Hurley wrote:
>
> The most common cause stems from the n_tty_close() path spuriously
> scheduling buffer work, when the ldisc has already been halted.
> This is fixed in 'tty: Don't reschedule buffer work while closing'

Thank you,
very useful.
Fix this:

WARNING: at drivers/tty/tty_buffer.c:429 flush_to_ldisc+0x52/0x192()
Hardware name: P5K Premium
tty is NULL
...
Pid: 1394, comm: kworker/0:2 Tainted: P W O 3.7.0-rc8-next-20121210-debtty.1+ #4
Call Trace:
[<ffffffff8102d2f8>] warn_slowpath_common+0x80/0x98
[<ffffffff8102d3a4>] warn_slowpath_fmt+0x41/0x43
[<ffffffff8119c53a>] flush_to_ldisc+0x52/0x192
[<ffffffff812594bd>] ? __schedule+0x5dd/0x60c
[<ffffffff8103f146>] process_one_work+0x1c1/0x279
[<ffffffff8119c4e8>] ? tty_buffer_free_all+0x4d/0x4d
[<ffffffff8104104b>] worker_thread+0x154/0x24e
[<ffffffff81040ef7>] ? manage_workers+0x26c/0x26c
[<ffffffff810446ef>] kthread+0xb0/0xb8
[<ffffffff8104463f>] ? kthread_parkme+0x1f/0x1f
[<ffffffff8125f7ec>] ret_from_fork+0x7c/0xb0
[<ffffffff8104463f>] ? kthread_parkme+0x1f/0x1f

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/