Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751453AbdH3UP5 (ORCPT ); Wed, 30 Aug 2017 16:15:57 -0400 Received: from emh03.mail.saunalahti.fi ([62.142.5.109]:37757 "EHLO emh03.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750761AbdH3UPw (ORCPT ); Wed, 30 Aug 2017 16:15:52 -0400 X-Greylist: delayed 333 seconds by postgrey-1.27 at vger.kernel.org; Wed, 30 Aug 2017 16:15:52 EDT Date: Wed, 30 Aug 2017 23:10:14 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Mikulas Patocka Cc: Michael Neuling , Dmitry Vyukov , Stephen Rothwell , Peter Hurley , Greg Kroah-Hartman , Nathan March , centos-virt@centos.org, linux-kernel@vger.kernel.org Subject: Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes Message-ID: <20170830201014.GO4090@reaktio.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1345 Lines: 27 Hello everyone, Recently Nathan March reported on centos-virt list he's getting frequent Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch "tty: Fix ldisc crash on reopened tty". The patch was already merged upstream here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05 but then reverted here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=896d81fefe5d1919537db2c2150ab6384e4a6610 Nathan confirmed if he applies the patch from 71472fa9c52b1da27663c275d416d8654b905f05 to his Linux 4.9 LTS kernel the bug/problem goes away, so the patch (or similar fix) is still needed, at least for 4.9 LTS kernel. Mikulas reported he's able to trigger the same crash on Linux 4.10: https://www.spinics.net/lists/kernel/msg2440637.html https://lists.gt.net/linux/kernel/2664604?search_string=ldisc%20reopened;#2664604 Michael Neuling reported he's able to trigger the bug on PowerPC: https://lkml.org/lkml/2017/3/10/1582 So now the question is.. is anyone currently working on getting this patch fixed and applied upstream? I think one of the problems earlier was being able to reliable reproduce the crash.. Nathan says he's able to reproduce it many times per week on his environment on x86_64. Thanks a lot, -- Pasi