Return-Path: Message-ID: <1537280357.21380.7.camel@arista.com> Subject: Re: [PATCHv5 3/7] tty: Hold tty_ldisc_lock() during tty_reopen() From: Dmitry Safonov To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>, Daniel Axtens , Dmitry Vyukov , Mark Rutland , Michael Neuling , Mikulas Patocka , Nathan March , Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= , Peter Hurley , Peter Zijlstra , "Rong, Chen" , Sergey Senozhatsky , Tan Xiaojun , Tetsuo Handa , Jiri Slaby , syzbot+3aa9784721dfb90e984d@syzkaller.appspotmail.com, stable@vger.kernel.org, Jiri Slaby Date: Tue, 18 Sep 2018 15:19:17 +0100 In-Reply-To: <20180918134734.GE23431@kroah.com> References: <20180917235258.5719-1-dima@arista.com> <20180917235258.5719-4-dima@arista.com> <20180918134734.GE23431@kroah.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Tue, 2018-09-18 at 15:47 +0200, Greg Kroah-Hartman wrote: > On Tue, Sep 18, 2018 at 12:52:54AM +0100, Dmitry Safonov wrote: > > tty_ldisc_reinit() doesn't race with neither tty_ldisc_hangup() > > nor set_ldisc() nor tty_ldisc_release() as they use tty lock. > > But it races with anyone who expects line discipline to be the same > > after hoding read semaphore in tty_ldisc_ref(). > > > > We've seen the following crash on v4.9.108 stable: > > > > BUG: unable to handle kernel paging request at 0000000000002260 > > IP: [..] n_tty_receive_buf_common+0x5f/0x86d > > Workqueue: events_unbound flush_to_ldisc > > Call Trace: > > [..] n_tty_receive_buf2 > > [..] tty_ldisc_receive_buf > > [..] flush_to_ldisc > > [..] process_one_work > > [..] worker_thread > > [..] kthread > > [..] ret_from_fork > > > > tty_ldisc_reinit() should be called with ldisc_sem hold for > > writing, > > which will protect any reader against line discipline changes. > > > > Backport-first: b027e2298bd5 ("tty: fix data race between > > tty_init_dev > > and flush of buf") > > What does this mean? > > Does this require that patch for a stable patch? If so, just do: > Cc: stable@vger.kernel.org # b027e2298bd5 ("tty: fix data race > between tty_init_dev and flush of buf") > in the signed-off-by area. The stable documentation should describe > this pretty well. If not, we can modify it to make it more obvious. > > can you fix this up for the next resend of this series? Sure, sorry about that non-obvious tag. -- Thanks, Dmitry