Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp1297565pxa; Sat, 15 Aug 2020 14:53:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx2Z/VPaAEK+e9ckIRyEVl9i2SCSCeIGoYyemjd4a8o94T+gZi0kqc/TAlYH1fNC4T1VDVM X-Received: by 2002:a50:ba8c:: with SMTP id x12mr8656187ede.319.1597528384419; Sat, 15 Aug 2020 14:53:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597528384; cv=none; d=google.com; s=arc-20160816; b=MwNQsDh3CDlUTksE4XmEd+PQfv4RgpHniVKfZDO4qcfYaDGECTWuvfn2ote0/8DyBA 903s3m66B2bdJe15mjAwcTQx17gRWpgAp7uyZzT9PKVSQm/aPhrW45rUPAd+3fMC2OBN y4v4J6g0a26jsCdfSf1abQ5HqT1kbRZdQCbM00IpDAajHZnGU5NcIQ7W2HtW1dFmF2eA dB+Ho5sj19b0IVBXwW8lLWdfRWaxOM7YxlJJZKszIcHKzTy8W+8/G+qJw3yLPnQqWH0C k5DFAosFx6Kq7mb4TW4qNBchcgOavd5NfAfBCA4/6x+82DKs1oGG1F6Hg1j+4bijHWve 1Wnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=srq9xR0jTgO+mDmp3efyhBKbSnbNofpfpXcr4LilIjQ=; b=EMI4lq/vR6v3y0QBbgc22OmEEc1JlMnPixeqywjYXu61lgltmIuB+JylXFdMKYQAzh AyRAUQ6ljUQjJGgQPtGA4WjyYBq8O/DB8YJYGiBSFOCxbMd+wGEzGRfpZQne2si5oSDC dt0q+bejLXzBThtCwQUBeLYI0WcuKBfH+RaiqXLnMxP9Xyv6O7p5aatGTTi9qEynzsao JJnu0O/z/DbM5YVtjqP8y+7jsU01qSE1Ge33CE26xBjfiSKd8wVPiuypjAMGtpvyarsx 1Qf2jm1CdMJTYV7u0Trq/Xj+6SXi30Uryly6Bk1sEXG3gOwYLhgaKlOTmZMbiWTwvFye Vl4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nQE9ecdj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id n11si8586742ejg.69.2020.08.15.14.52.41; Sat, 15 Aug 2020 14:53:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nQE9ecdj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1728861AbgHOVvh (ORCPT + 99 others); Sat, 15 Aug 2020 17:51:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728699AbgHOVvW (ORCPT ); Sat, 15 Aug 2020 17:51:22 -0400 Received: from mail-pj1-x1041.google.com (mail-pj1-x1041.google.com [IPv6:2607:f8b0:4864:20::1041]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0D259C061233 for ; Fri, 14 Aug 2020 22:41:46 -0700 (PDT) Received: by mail-pj1-x1041.google.com with SMTP id e4so5367725pjd.0 for ; Fri, 14 Aug 2020 22:41:46 -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; bh=srq9xR0jTgO+mDmp3efyhBKbSnbNofpfpXcr4LilIjQ=; b=nQE9ecdjegmgyaV/9aIBzopGQ2bnLLI9akMcx4qO/xGiJshCq+dHj++WehnY4Pe9fS ME8Ogdd2M00zA6WGyvTCT1Y9KRwRtJsflWfM8+gNtcGzqPX0TyibVZ/TdpkVhMn1gUyo 6Q0frCzlGBU4Xz/D4R4KhEVHAZv809XSwaZvo06Fxk3Ln+VXEXNkCi/PINwVy9XeZ/j+ UzdHaGrXxegyEqXhEjMBtixhwIO1OrRK5c1HUFMLhw7qcP/k9vVdhaQe9BjzHpm35ySO Y4B0GdSaWkiPrDV5yG7wRLcm/8LvExOu6h3ibIVbtpDHwSvM3KIyv3duRrFmst/b1AIU yoQA== 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; bh=srq9xR0jTgO+mDmp3efyhBKbSnbNofpfpXcr4LilIjQ=; b=D/5oKQC6BFzUinl0Hj18I6XmLkHpDl4/Wlavv91KpLFRfeco7DQAqMx1Kok09RbT+m c7RlxF8uCXNpg9dGbFwgU+G1kuethX7SwmBFUmLNfCJTBLWyA7Fs1+1GXqF+KkNDqKai W6VJ7/nCaJZm93VJgMbhKMVRONuqgSi+jfeezS3mHgyzqoKr8AjVL0QKx+wnDGrmTCla G4k/n1b0NcHTQS2SVn0TjpEQDVWZuH7rc5HVPJzk9+0cR2qYMZdetk3FdVDWHwyZLx6Q YkJ8Yy8wEVZ5mGuVbOduFdWULfplHCHx/OfylYYbz/x818evjIpdYfN9OZqSI93PQlkJ auHg== X-Gm-Message-State: AOAM5317muzUV65M13gw8Y9VVUCVR0pPF1P5cq+C1sJCSxb51YQHlUrG ntvJfXqpVGtWVSEOu2QY2s8= X-Received: by 2002:a17:90a:70c9:: with SMTP id a9mr4519032pjm.167.1597470106338; Fri, 14 Aug 2020 22:41:46 -0700 (PDT) Received: from localhost ([2409:10:2e40:5100:6e29:95ff:fe2d:8f34]) by smtp.gmail.com with ESMTPSA id q7sm8704580pfu.133.2020.08.14.22.41.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 14 Aug 2020 22:41:45 -0700 (PDT) Date: Sat, 15 Aug 2020 14:41:43 +0900 From: Sergey Senozhatsky To: Linus Torvalds Cc: Sergey Senozhatsky , Petr Mladek , John Ogness , Sergey Senozhatsky , Steven Rostedt , Greg Kroah-Hartman , Peter Zijlstra , Thomas Gleixner , kexec@lists.infradead.org, Linux Kernel Mailing List Subject: Re: POC: Alternative solution: Re: [PATCH 0/4] printk: reimplement LOG_CONT handling Message-ID: <20200815054143.GD582@jagdpanzerIV.localdomain> References: <87blkcanps.fsf@jogness.linutronix.de> <20200811160551.GC12903@alley> <20200812163908.GH12903@alley> <87v9hn2y1p.fsf@jogness.linutronix.de> <20200813051853.GA510@jagdpanzerIV.localdomain> <875z9nvvl2.fsf@jogness.linutronix.de> <20200813084136.GK12903@alley> <20200813115435.GB483@jagdpanzerIV.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (20/08/14 15:46), Linus Torvalds wrote: > On Thu, Aug 13, 2020 at 4:54 AM Sergey Senozhatsky > wrote: > > > > I think what Linus said a long time ago was that the initial purpose of > > pr_cont was > > > > pr_info("Initialize feature foo..."); > > if (init_feature_foo() == 0) > > pr_cont("ok\n"); > > else > > pr_cont("not ok\n"); > > > > And if init_feature_foo() crashes the kernel then the first printk() > > form panic() will flush the cont buffer. > > Right. > > This is why I think any discussion that says "people should buffer > their lines themselves and we should get rid if pr_cont()" is > fundamentally broken. I think what we've been talking about so far was "how do we buffer cont lines now", what are the problems of current buffering and what can we do to make that buffering SMP safe (preserving the context of broken cont buffer, etc. etc.). I don't think that anyone concluded to just "s/pr_cont/printk/g", I don't see this. -ss