Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6384982ybe; Wed, 18 Sep 2019 02:34:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrxN/Pt2pkNRcvhuPK7GRaQUzNGeA0x3rjtcZJxIhY6KuvObF8PsVpp3JdrWpYqCWiQddE X-Received: by 2002:a50:9a05:: with SMTP id o5mr9354794edb.44.1568799285672; Wed, 18 Sep 2019 02:34:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568799285; cv=none; d=google.com; s=arc-20160816; b=bh51wuZVn5XroazQ81hq0uc87YkpzHRhDzqlhOKfkVM8HCN/96a9KuLv1GkTUdmt4L YBhNA0Yl1Fx8Z2xWOCk8/wq7q+KSXlgB4DcODSJIEB2TFHIkWdAjvmFi48A7KUpISQjy pxiOxxh04yRhWvKs5XfvULUbmCw/MIfVl66p/7cBPgWFthBrsOFTYSXLkxIi8pXpcXAL U+LHQPcdZy6dXztwskQxiK/KMXroROqdB1Wmxsx8QGoCjIS2GghvCP3OzXaU6GwIDqBm sKArG+iD+ijFsDfg23A/rD7/er7uiZCOlOjOOXVI32Bju6IMgp0fYzGD54Ez36wT9h2X gVaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=RQbdsmmWxLAMHmcxjS1VEkYRC7qh/5LglHiRmX1QRKk=; b=qDRToRV8AnljV0TNA0fkLvW/k4G/13SHYuLhozz95gweGeCyzHBlxPDc7LqN5MXFOS zI9VwcEk0OtWORq8hyDEaCvKVeZ2uGwHQUXu/KLzOL+lvmsfewdg/okWxrKikFc1Ve3R PA6wef9EVfE4Y+/pkzkOjaxXoksl/wX1SNM2O40SpFJDLJCE/bUBdNskE/n3dVCxlE7r MX8KDPG8Kqcbg42IwTE0I92Hhb1tgfCq3ELNrnECbZKquGfaSpH7dYLFg76M7BDk3K4v +YjS73aiThoPpYNr50SkJWhIrQmYgOFFG31P7X4XhAXqWOXmNEoUAiSFK8afdtRkK6eV OV1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=TjtPWLGX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id qh28si2503597ejb.210.2019.09.18.02.34.22; Wed, 18 Sep 2019 02:34:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=TjtPWLGX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729820AbfIRIIi (ORCPT + 99 others); Wed, 18 Sep 2019 04:08:38 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:35618 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726824AbfIRIIh (ORCPT ); Wed, 18 Sep 2019 04:08:37 -0400 Received: by mail-pg1-f195.google.com with SMTP id a24so3564041pgj.2 for ; Wed, 18 Sep 2019 01:08:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=RQbdsmmWxLAMHmcxjS1VEkYRC7qh/5LglHiRmX1QRKk=; b=TjtPWLGXOaEKW8ssJzgvSB2n4aJtzX0cjdAOZJcnLI8qci4h1dTkisnVfA4BCjaRev 48XZfPTGz7NkZZemSYpSm/y491n2jhpolVE4TnhgAHJytfh+rdzXX44pnuenMyWFOMkS ig5myx4Uy5ltGzh8hxi10KysoEvbrD+Jk1C6PLEVCX7nnJcmFYcyfhbD58+EEMUGzinJ fZ2gU8CZkICUXELUNE+yfedq+rQrfbiA+zK2iFdNYvTd53gOmIfwKi7ZbpIkS6jCQE3V ZRbw3DfdyWUxXDJ4HgFhkXqpqcWBrBBhTUn6CrACnoG2CEIkquXPY5DJygjYFu5GOrz8 +jdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RQbdsmmWxLAMHmcxjS1VEkYRC7qh/5LglHiRmX1QRKk=; b=bZFoZae1XuTZ6O7pq/sJZsakEq9WPaMYvLP+u499YfI+OIcwSXkunCzRTcW53HEJCA 3Vraju+y57N/6T5fS8Mtaq5bNxGqv6O0OgG9ayPk4IEDXBfJBNKLllKFXdXelJALujaw y1M8kGdb4cQHWsIlcB1xpw5UptI27q6nxHbyovmhicU1bnN2jEkbI038l7gxuYxFb2zZ Uxr1iPHEqDuKmhjV871Tb1Grbtt2pnTIJJl9ng1Lz1UGBXIZ6tSGR1Z9ng0gF9sAFbOZ RiW6O3ZkBNlUJc46kuRIEdna99T4qAcSEQ2vXUnNtPffd5RHDGakVD+2pPt3QYNJAezF xjdg== X-Gm-Message-State: APjAAAWlIs4eMyT6wVbtrdkET29+0vnL/XlpZPiRnM9yaqV5VIJxmKq2 1tDpVXi6sPqO85W8d+TeXKM= X-Received: by 2002:a17:90a:ae04:: with SMTP id t4mr2424248pjq.52.1568794116915; Wed, 18 Sep 2019 01:08:36 -0700 (PDT) Received: from localhost ([175.223.34.14]) by smtp.gmail.com with ESMTPSA id y28sm8616881pfq.48.2019.09.18.01.08.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Sep 2019 01:08:36 -0700 (PDT) Date: Wed, 18 Sep 2019 17:08:32 +0900 From: Sergey Senozhatsky To: John Ogness Cc: Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Thomas Gleixner , Peter Zijlstra , Petr Mladek , Andrea Parri , Sergey Senozhatsky , Brendan Higgins , Greg Kroah-Hartman , LKML , Theodore Ts'o , Paul Turner , Daniel Vetter , Prarit Bhargava Subject: Re: printk meeting at LPC Message-ID: <20190918080832.GA37041@jagdpanzerIV> References: <20190905130513.4fru6yvjx73pjx7p@pathway.suse.cz> <20190905143118.GP2349@hirez.programming.kicks-ass.net> <20190905121101.60c78422@oasis.local.home> <87k1acz5rx.fsf@linutronix.de> <20190918012546.GA12090@jagdpanzerIV> <20190917220849.17a1226a@oasis.local.home> <20190918023654.GB15380@jagdpanzerIV> <87lfumnjo2.fsf@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lfumnjo2.fsf@linutronix.de> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (09/18/19 09:33), John Ogness wrote: > > I expect sysrq to be the only valid use of "synchronous state" other > than oops/panic. Although I suppose PeterZ would like a boot argument to > always run the consoles in this state. Yes, there might be more cases when we need sync printk(). Like lockdep splats, KASAN warnings, PM debugging, etc. Those things sometimes come right before "truly bad stuff". > > For instance, tty/sysrq must be able to switch printk emergency > > on/off. > > The switch/flush _will_ be visible. But not the state. So, for example, > it won't be possible for some random driver to determine if we are in an > emergency state. (Well, I don't know if oops_in_progress will really > disappear. But at least the printk/console stuff will no longer rely on > it.) [..] > Thanks for bringing up that RFC thread again. I haven't looked at it in > over a year. I will go through it again to see if there is anything I've > overlooked. Particularly the suspend stuff. That thread most likely is incomplet and incorrekt in some parts; shouldn't be taken too seriously, I guess. -ss