Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp187319imm; Tue, 19 Jun 2018 18:56:23 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIZRx51DDAIBEX+aUgF+f8dkXDj6Ol5JG541yLZG+xh25FnKr5oEBk/L72b/hiN8WO+3bpt X-Received: by 2002:a17:902:a9ca:: with SMTP id b10-v6mr5231310plr.275.1529459783073; Tue, 19 Jun 2018 18:56:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529459783; cv=none; d=google.com; s=arc-20160816; b=kCKBfObYeyMPWmcl7783JnkT7+ye2CWcUIdN+YDpDLFs/GhYuQHvgofFqS8p/CMoTI hVC3bX3odFhKBpxlDzeIOzUNdw+qnvQ85KmLBiIPjFnEm9ijIvPGsqEZVW4Y4H0iLpcb /cvHloiytd0gDsQWs8LireTyLrESp/RhbUrykFKnP3IBXH1xltPzbXAQ1gI7v3i2gdo5 hrBQlI6fVmM+RN9WF7sLu+pF/fLR3XQmTYWn9jrWt7bm4QkqGH4wU0dHg518PS0nFun4 /CYDqOspNpULenc4ui/hI6RBgP6UCczUxGj8IFaglP/6OIJ7vtE0BGHaEiRu9ZQbgzkg W03Q== 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=OuvBfndeGk2bUFzhKctxXhezMsreB0RrB+0AYNF8mso=; b=khvyjALDQxIh2B1u6rYAUmGJLOY2TBEFUHtHZmqOZmjLaxL+fpUda/oXShIondFjtk nnRKecJWOM5V2ozJIBxF7atHz8+nK9yF9gqRtGnesWgB4KXEiq2EXQsMBFxWQElrdJUy bxqZ1aC7Qi5shw2kF6Euk66wt+mrF4sFC8rvK+Pp4uc6TzSJ/HszJrOcH01jj/3rNCtr lZb8st63n12bxA8QZj+iqATQ/k5j8IImyKzjFCz3aibGtyPXLfCy7FPoRmFdjqh0to1B xeP/iRPqWt4HCNH5cT/YRYO6+Ku3Q6mfEZeEQ0EPF+Q89f6N+D8H7HlcTtJ0MThPTDg5 6lHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=A5jw3mAa; 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 z4-v6si1166095pfl.31.2018.06.19.18.56.09; Tue, 19 Jun 2018 18:56: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=A5jw3mAa; 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 S1753741AbeFTBzc (ORCPT + 99 others); Tue, 19 Jun 2018 21:55:32 -0400 Received: from mail-pg0-f65.google.com ([74.125.83.65]:46549 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752784AbeFTBza (ORCPT ); Tue, 19 Jun 2018 21:55:30 -0400 Received: by mail-pg0-f65.google.com with SMTP id d2-v6so695543pga.13 for ; Tue, 19 Jun 2018 18:55:30 -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=OuvBfndeGk2bUFzhKctxXhezMsreB0RrB+0AYNF8mso=; b=A5jw3mAaa321Uk/Bf9oVEFtBE1HeG98Ub7RzaN7kX54ioZp3HZ/j+39iQT/vYOXX3c 2UNc5lv+isufmuViZPDfScMLpjfucFgZIq1ny3OhXiuDUVo6Ao4imBnQTzDbjoiFY0DZ XIXxNKMcYW495g68iqPZFobEAwY32Kbb3+uxuGrDh307ra2XKtqsxBcYY4cp3LpB719e +Gg41cXY1xte67tdNjBwnUuEjx+/r6NjrJEcZrLrax95F/DZyeg1wjPhhn7PVOOwRQTr o/92edwrwz0qxynseqe1JsI0hykWXa959t6KsuhVxu5cA+s0bYYol5UmiTlX/I3x/WKv fBmA== 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=OuvBfndeGk2bUFzhKctxXhezMsreB0RrB+0AYNF8mso=; b=eZWWso7bIZf3QU1X44s3WAA1YJlgpZI9yxymAn2GidvMp0wCrM8cgK+xj7yPxt4qSw NOyTh3nJClIU7IbHJ/QDnY8FGKAh262TI222Com22OXqNxLkmC679iZQG/Sdy1fiuOix iLXiOy+caiRUhFzgtJ8ArBynFBz3AkQFLd7j+TbLe95pB/kURb0u5udN7YslyPG/jmw9 rNVtKgQMCitT+jmTYmv9THubZZHoSuslS0RInE9WGfeLk6AYxlLuxdHhN6o9PussDiqu 5bz7HeP28bLJKwQrFamxciQInvMZJACsPd++nWj/qqiSPR+7zyhprLwxISS+6JU/NEKD lRnQ== X-Gm-Message-State: APt69E0sXomZxxg+MZPIp8v7Br3A99YCpsleR0G9zn4xOGkMfL84Kcpb BtapMb5HRGavdXK0mxEPoSM= X-Received: by 2002:a63:7255:: with SMTP id c21-v6mr16397559pgn.99.1529459730269; Tue, 19 Jun 2018 18:55:30 -0700 (PDT) Received: from localhost ([110.70.59.159]) by smtp.gmail.com with ESMTPSA id m11-v6sm1278291pfk.42.2018.06.19.18.55.27 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Jun 2018 18:55:28 -0700 (PDT) Date: Wed, 20 Jun 2018 10:55:25 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Sergey Senozhatsky , Maninder Singh , sergey.senozhatsky@gmail.com, rostedt@goodmis.org, linux-kernel@vger.kernel.org, a.sahrawat@samsung.com, pankaj.m@samsung.com, v.narang@samsung.com Subject: Re: [PATCH v2] printk: make sure to print log on console. Message-ID: <20180620015525.GC650@jagdpanzerIV> References: <20180601090029epcas5p3cc93d4bfbebb3199f0a2684058da7e26~z-a_jkmrI2993329933epcas5p3q@epcas5p3.samsung.com> <20180618061550.GA27996@jagdpanzerIV> <20180618062306.GA29683@jagdpanzerIV> <20180619093244.ehj34uhpnpv6447f@pathway.suse.cz> <20180619094953.GB2631@jagdpanzerIV> <20180619105213.uzf6ba3oo3475icz@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180619105213.uzf6ba3oo3475icz@pathway.suse.cz> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (06/19/18 12:52), Petr Mladek wrote: > > But when I set /sys/module/printk/parameters/ignore_loglevel I naturally > > expect it to take an immediate action. Without waiting for the consoles > > to catch up and to discard N messages [if the consoles were behind the > > logbuf head]. > > Yeah, I understand this view. I thought about it as well. But did you > ever needed this behavior in the real life? > > I personally changed ignore_loglevel only before I wanted to reproduce a > bug. Then it would be perfectly fine to handle it only in > vprintk_emit(). In fact, it would be even better because it would > affect only messages that happened after I triggered the bug. I thought that additionally to sysfs knob we had a console_foo() function that simply set ignore_loglevel. But it appears to be sysfs or boot-time configurable only. I confused CONSOLE_LOGLEVEL_MOTORMOUTH and ignore_loglevel and thought that a console_verbose() call would basically set ignore_loglevel to true. It's a bit misleading that we have multiple and independent ways of achieving the same result. So maybe the patch can stand the way it is, after all. JFI, still haven't seen those "helps in real life a lot" examples, tho. > schizophrenic logic. OUCH! Seriously, what the... Knock it off! -ss