[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181122131202.nkcurdt5k6jrhowa@pathway.suse.cz>
Date: Thu, 22 Nov 2018 14:12:02 +0100
From: Petr Mladek <pmladek@...e.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
Daniel Wang <wonderfly@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Jiri Slaby <jslaby@...e.com>,
Peter Feiner <pfeiner@...gle.com>,
linux-serial@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [PATCHv3] panic: avoid deadlocks in re-entrant console drivers
On Thu 2018-11-01 09:08:08, Petr Mladek wrote:
> 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 <sergey.senozhatsky@...il.com>
> > >
> > > The patch makes sense to me. The locks should stay busted also for
> > > console_flush_on_panic().
> > >
> > > With the added #include <linux/vt_kern.h>:
> > >
> > > Reviewed-by: Petr Mladek <pmladek@...e.com>
> >
> > 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 have pushed this into printk.git, branch for-4.21.
Best Regards,
Petr
Powered by blists - more mailing lists