Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp3183891imm; Thu, 17 May 2018 04:55:23 -0700 (PDT) X-Google-Smtp-Source: AB8JxZry8Cdi8FWH/ZEzOfKSDV236ldVL0cSGMgceYehOdIW2Ke3iaMmO77pWAdnhQ5jNwYBoXVj X-Received: by 2002:a62:ea1a:: with SMTP id t26-v6mr4936695pfh.117.1526558123372; Thu, 17 May 2018 04:55:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526558123; cv=none; d=google.com; s=arc-20160816; b=p+iY2FsITpfv7cefR0r9XLv8tVerX6SH3vchgDdJ2QbRkDFSoViS8RCtvgcSacXDoA K764EOD8MBHRdIIPqFcfE94kh/RCS+eShQShLvkmZIcsaXuPnYFiKWATjSmuwdGMxAHv TecGLCrQwsl3wfBNBep4EKTir57gNUnezPdDRTFj1085474Q5HdPE8b7uozG8+97PIbN UdqAb+7tZ7bEoRyC+E4HiVWBmPkHzdbHrBxmx3HR9O/O4UdGurbcts9ZL7e1qfxw/fVh c8pI/QE9WES/SCAgF6oIU9Yy7SWpfyYmIc9oMZBJNK/Goj2gY5C84OSD7Uhd/BqmUm/w 9f9Q== 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:arc-authentication-results; bh=6JVtL6ycpvAl9Gv57P8BJEHB31WzI3TKkJdvx2tujTw=; b=Imd4fh1tnT63WJfW4J20oJyx0o9q4X+HC8XIjR9jLZzi4EdYRgnHDBwgRdPEspQH7/ ceO5Y9JR7FqcxjE6xRWlwdyBAfC/ztDrQlVbXLs/YfCJrhcXVf8WsRwbtivEOSg3uHyR 0pd7BfGbaqHcw5IswfYmjc4j8oDv3XuTCZZtBYl3iEevDacOoM/IhzGXrLJbskpBWJS0 k1WTqZKJKYVYLCM8EtfR8dkno8ApK6UFU464KWpLjEeR1jgXMtHfMz6RjIt9/9031vWt QKbHrBRrUWLmLLW4z84/tuV7sGOyIF9yChnumHgSigGdFk91EkFqSO9JRPEPEs4cg9pL txZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Zi5zg//n; 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 n6-v6si5073143plp.386.2018.05.17.04.55.08; Thu, 17 May 2018 04:55:23 -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=Zi5zg//n; 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 S1751907AbeEQLwy (ORCPT + 99 others); Thu, 17 May 2018 07:52:54 -0400 Received: from mail-pf0-f193.google.com ([209.85.192.193]:44162 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751839AbeEQLwx (ORCPT ); Thu, 17 May 2018 07:52:53 -0400 Received: by mail-pf0-f193.google.com with SMTP id q22-v6so1985188pff.11 for ; Thu, 17 May 2018 04:52:53 -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=6JVtL6ycpvAl9Gv57P8BJEHB31WzI3TKkJdvx2tujTw=; b=Zi5zg//nV4fQcYltWbAZ9+1OCq40cDU2O5GtjsqS/2Cn3sG+9pXlZccHLf1p3n/Lw4 V4vP7ehXjhT54G4iUY7vYq2gfs2lJzaQq/XCXpdLMZAav1sOaT2mi3dA3t5yItRW4l7B pxDFkpFVU8nr8hnZvtoWF4pNGjZaFPYvNentyhL5w2VDbkdXI8plZOTaGKrmdoIzg9x+ AqGMgAxNh9t4gdZIuY0H8c0GJ3oMg7p0Ksa0J2ht80azZWwOwilQAogG5qUpES5vynME Pw4d9aRM2QKSkXJizFP0SzbhHjkwAeCTPDeeMsX/aRGdLGf5XqlqVUokcz4i7dPI2cdX WMsA== 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=6JVtL6ycpvAl9Gv57P8BJEHB31WzI3TKkJdvx2tujTw=; b=Y9Wwt8tGSOGFTLcRUYIAJM55TOtpSZCikw+E3WoI84tvtfkGhyhg9MspllA7/nzvSf DBHg+kI0pSZl0eLiztvm6GLbIJnIHPJgLrMscCRCCI0WxXV6bV4SsqxmkA2u9ALTP13o 5JRZyjz+xYmt/2kIdxVz7IYjFQfZsLu4+1OpOUe8+cBvYI7l8xROy37Y8HB9iohNkti5 BHtn35LWlCz/+9NbGcn/edmUqEXx1IRwdiUM7k3A5IecQDCCGslgDWBdQaDW9SPa9yDe VCFEXpUGSY0LzMDmWff1n+q0TMchLDDk/518nd6SMu0M368WQcYN1++1HuH845PBYz4l 2DmA== X-Gm-Message-State: ALKqPweMBtxAC1+LqMb1/2Fld118ZyPRHSDGQQxBUwE9saainNqwqdTK ykaXiPTtfJZWujETlX+ZZM0= X-Received: by 2002:a62:c485:: with SMTP id h5-v6mr5016746pfk.86.1526557972736; Thu, 17 May 2018 04:52:52 -0700 (PDT) Received: from localhost ([175.223.26.113]) by smtp.gmail.com with ESMTPSA id z25-v6sm9988982pfi.171.2018.05.17.04.52.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 May 2018 04:52:51 -0700 (PDT) Date: Thu, 17 May 2018 20:52:48 +0900 From: Sergey Senozhatsky To: Sergey Senozhatsky Cc: Tetsuo Handa , dvyukov@google.com, pmladek@suse.com, sergey.senozhatsky@gmail.com, syzkaller@googlegroups.com, rostedt@goodmis.org, fengguang.wu@intel.com, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org Subject: Re: [PATCH] printk: inject caller information into the body of message Message-ID: <20180517115248.GA409@jagdpanzerIV> References: <20180511014515.GA895@jagdpanzerIV> <201805110238.w4B2cIGH079602@www262.sakura.ne.jp> <20180511062151.GA18160@jagdpanzerIV> <20180511095004.GA6575@jagdpanzerIV> <201805112058.AAB05258.HJQFFOMFOVtOSL@I-love.SAKURA.ne.jp> <20180517112135.GB20796@jagdpanzerIV> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180517112135.GB20796@jagdpanzerIV> User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (05/17/18 20:21), Sergey Senozhatsky wrote: > Dunno... > For instance, can we store context tracking info as a extended record > data? We have that dict/dict_len thing. So may we can store tracking > info there? Extended records will appear on the serial console /* if > console supports extended data */ or can be read in via devkmsg_read(). Those extended records are already there for exactly the same reason - people want to attach a special context to printk() entries. See dev_vprintk_emit() and create_syslog_header(). So we can add more key/value data to that context. Sounds kinda-sorta reasonable. So, for example, this output cat /dev/kmsg 6,577,3156036,-;snd_hda_codec_generic hdaudioC1D0: autoconfig for Generic: line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line SUBSYSTEM=hdaudio DEVICE=+hdaudio:hdaudioC1D 6,578,3156807,-;snd_hda_codec_generic hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) SUBSYSTEM=hdaudio DEVICE=+hdaudio:hdaudioC1D Becomes this: 6,566,3033752,-;snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 3/207: 0/0/0 SUBSYSTEM=hdaudio DEVICE=+hdaudio:hdaudioC0D 6,567,3033754,-;snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 3/207: 0/0/0 SUBSYSTEM=hdaudio DEVICE=+hdaudio:hdaudioC0D "3/207: 0/0/0" is smp_processor_id/task_pid_nr and then masked out bits of preempt count: hard irq, soft irq, nmi. We definitely can change the format, etc. This is just a very quick and dirty PoC. Something as follows? /* just to demonstrate the idea */ --- kernel/printk/printk.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index 2f4af216bd6e..4a82d52a343d 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -580,16 +580,33 @@ static u32 truncate_msg(u16 *text_len, u16 *trunc_msg_len, return msg_used_size(*text_len + *trunc_msg_len, 0, pad_len); } +static size_t add_log_origin(char *buf, size_t buf_len) +{ + return snprintf(buf, + buf_len, + "%d/%d: %lu/%lu/%lu", + raw_smp_processor_id(), + task_pid_nr(current), + preempt_count() & HARDIRQ_MASK, + preempt_count() & SOFTIRQ_MASK, + preempt_count() & NMI_MASK); +} + /* insert record into the buffer, discard old ones, update heads */ static int log_store(int facility, int level, enum log_flags flags, u64 ts_nsec, const char *dict, u16 dict_len, const char *text, u16 text_len) { + static char log_origin[64]; + static size_t log_origin_len; struct printk_log *msg; u32 size, pad_len; u16 trunc_msg_len = 0; + log_origin_len = add_log_origin(log_origin, sizeof(log_origin)); + dict_len += log_origin_len; + /* number of '\0' padding bytes to next message */ size = msg_used_size(text_len, dict_len, &pad_len); @@ -620,7 +637,10 @@ static int log_store(int facility, int level, memcpy(log_text(msg) + text_len, trunc_msg, trunc_msg_len); msg->text_len += trunc_msg_len; } - memcpy(log_dict(msg), dict, dict_len); + memcpy(log_dict(msg), log_origin, log_origin_len); + memcpy(log_dict(msg) + log_origin_len + 1, + dict, + dict_len - log_origin_len); msg->dict_len = dict_len; msg->facility = facility; msg->level = level & 7;