Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp834104imm; Fri, 22 Jun 2018 06:09:00 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIUAfpSNtv6+AN4brl0EYz6VBZ+aUfy9aQ3vNTWJnUtQebzOrT6LXtG/34SsmpWX22osSC8 X-Received: by 2002:a62:a8e:: with SMTP id 14-v6mr1682671pfk.57.1529672940567; Fri, 22 Jun 2018 06:09:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529672940; cv=none; d=google.com; s=arc-20160816; b=DtxnQm6KhFVu/BMoC0l+jhMJyM/QlMU65Kd+dlrJMM4xh3xoBDmMu6VuSWBo8W7BD7 NM7pOGqyxFSU03flWWZcROlsY6v7WSYgH11ye5I0ffKQc8OfTUF1DA7vTraVmI56ihMH ctNkdK1LBPDHhZ/Rn71+WDDZbky8VNC+lj5nwB6Ngmyu6KjS3E11xVbcJfz+wsA6YvDI tngbLf3FnlrBctxKtsI6bsb6XNtx3W26NEdq/85XlV3lM1HAxkaprSp5PChvvqaj8L+q fKy60xC2HZPgO1SY4ev4qcmiWm1FKqMgwYwXl/6gEx5I5oqMErzdqPcBXyzqjTGxSYLu Hocg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=8Da98fJBy2ZDpxzcO6Wyf/XOer97lDnQhoa8qfcwJ/I=; b=dUdP+QG7vx3gH3gqRtZFXTrpTIdb9R86D2zIPt56/bveIKk5J/23966c4RocXZJZcd 9eH0GXPFvmcoLXGZixWNxA2Za47JiSsyWcJajbOCxKkMh+1BZrpqVZ/OnRH2qikkTYEs yNhpWAR9YdKdn66/w+qlA9JBxsAVYc8okIBu55JEw2QQ6t9g8oBvIWLOzx8z8d0bDkxn TOoW0HFT0bsUUK8xDp5IZBC2+2dY3WNNJTufS5IwxPz7hOnNKApdyXMU572Z+gOXv+w8 Ky4Kev+ncgeyBkwK3cKakpTk9TnqmtfI5SpNJvtJ9UfVxQYMcL7v53OT5aas4OUmvAIJ nOsw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w8-v6si5989843pgs.145.2018.06.22.06.08.46; Fri, 22 Jun 2018 06:09:00 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754129AbeFVNGy (ORCPT + 99 others); Fri, 22 Jun 2018 09:06:54 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:55713 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750853AbeFVNGx (ORCPT ); Fri, 22 Jun 2018 09:06:53 -0400 Received: from fsav404.sakura.ne.jp (fsav404.sakura.ne.jp [133.242.250.103]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id w5MD6p7s081828; Fri, 22 Jun 2018 22:06:51 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav404.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav404.sakura.ne.jp); Fri, 22 Jun 2018 22:06:51 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav404.sakura.ne.jp) Received: from [192.168.1.8] (softbank126074194044.bbtec.net [126.74.194.44]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id w5MD6kQC081787 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jun 2018 22:06:51 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH] printk: inject caller information into the body of message To: Sergey Senozhatsky , Dmitry Vyukov , Fengguang Wu Cc: Sergey Senozhatsky , Petr Mladek , syzkaller , Steven Rostedt , LKML , Linus Torvalds , Andrew Morton References: <20180524021451.GA23443@jagdpanzerIV> <20180620083126.GA477@jagdpanzerIV> <20180620090413.GA444@jagdpanzerIV> <20180620091541.GB444@jagdpanzerIV> <20180620110759.GD444@jagdpanzerIV> <20180620130628.GA1000@tigerII.localdomain> From: Tetsuo Handa Message-ID: <197be25e-c841-bf3c-7081-61f0a9653c8c@i-love.sakura.ne.jp> Date: Fri, 22 Jun 2018 22:06:45 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180620130628.GA1000@tigerII.localdomain> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018/06/20 22:06, Sergey Senozhatsky wrote: > On (06/20/18 13:32), Dmitry Vyukov wrote: >>> So, if we could get rid of pr_cont() from the most important parts >>> (instruction dumps, etc) then I would just vote to leave pr_cont() >>> alone and avoid any handling of it in printk context tracking. Simply >>> because we wouldn't care about pr_cont(). This also could simplify >>> Tetsuo's patch significantly. >> >> Sounds good to me. > > Awesome. If you and Fengguang can combine forces and lead the > whole thing towards "we couldn't care of pr_cont() less", it > would be really huuuuuge. Go for it! Can't we have seq_printf()-like one which flushes automatically upon seeing '\n' or buffer full? Printing memory information is using a lot of pr_cont(), even in function names (e.g. http://lkml.kernel.org/r/20180622083949.GR10465@dhcp22.suse.cz ). Since OOM killer code is serialized by oom_lock, we can use static buffer for OOM killer messages.