From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Mladek Subject: Re: [PATCHv3] panic: avoid deadlocks in re-entrant console drivers Date: Thu, 1 Nov 2018 09:08:08 +0100 Message-ID: <20181101080808.n73lrlnjd65nk4qf@pathway.suse.cz> References: <20181016050428.17966-2-sergey.senozhatsky@gmail.com> <20181025101036.6823-1-sergey.senozhatsky@gmail.com> <20181031122736.epbxu424l3xagge5@pathway.suse.cz> <20181101014821.GB502@jagdpanzerIV> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20181101014821.GB502@jagdpanzerIV> Sender: linux-kernel-owner@vger.kernel.org To: Sergey Senozhatsky Cc: linux-kernel@vger.kernel.org, Steven Rostedt , Daniel Wang , Peter Zijlstra , Andrew Morton , Linus Torvalds , Greg Kroah-Hartman , Alan Cox , Jiri Slaby , Peter Feiner , linux-serial@vger.kernel.org, Sergey Senozhatsky List-Id: linux-serial@vger.kernel.org On Thu 2018-11-01 10:48:21, Sergey Senozhatsky wrote: > On (10/31/18 13:27), Petr Mladek wrote: > > > > > > Signed-off-by: Sergey Senozhatsky > > > > The patch makes sense to me. The locks should stay busted also for > > console_flush_on_panic(). > > > > With the added #include : > > > > Reviewed-by: Petr Mladek > > Thanks! > > Since there are no objections - how shall we route it? Via printk tree? Good question. OK, I am going to put it into printk.git unless I hear complains withing next couple of days. > I'd also prefer this patch to be in -stable, it fixes a real issue after > all. It makes sense. Best Regards, Petr