From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: Re: [RFC PATCH v1 19/25] printk: introduce emergency messages Date: Tue, 12 Mar 2019 11:58:47 +0900 Message-ID: <20190312025847.GD4146@jagdpanzerIV> References: <20190212143003.48446-1-john.ogness@linutronix.de> <20190212143003.48446-20-john.ogness@linutronix.de> <20190307073029.GA489@jagdpanzerIV> <20190308103127.txsgv3d6lqlf6pad@pathway.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190308103127.txsgv3d6lqlf6pad@pathway.suse.cz> Sender: linux-kernel-owner@vger.kernel.org To: Petr Mladek Cc: Sergey Senozhatsky , John Ogness , linux-kernel@vger.kernel.org, Peter Zijlstra , Steven Rostedt , Daniel Wang , 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 (03/08/19 11:31), Petr Mladek wrote: > Great catch! > > I think that it is doable to guard the list using RCU. I think console_sem is more than just list lock. E.g. fb_flashcursor() - console_sem protects framebuffer from concurrent modifications. And many other examples. I think the last time we talked about it (two+ years ago) we counted 5 or 7 (don't remember exactly) different things which console_sem does. -ss