From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2756C43387 for ; Tue, 18 Dec 2018 15:24:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9962121871 for ; Tue, 18 Dec 2018 15:24:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="Qwq4jMS9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726740AbeLRPYU (ORCPT ); Tue, 18 Dec 2018 10:24:20 -0500 Received: from mail.skyhub.de ([5.9.137.197]:48200 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726379AbeLRPYU (ORCPT ); Tue, 18 Dec 2018 10:24:20 -0500 Received: from zn.tnic (p200300EC2BD17800C11009BD73D4094D.dip0.t-ipconnect.de [IPv6:2003:ec:2bd1:7800:c110:9bd:73d4:94d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 285281EC0629; Tue, 18 Dec 2018 16:24:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1545146659; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=WiI6Cwb5uZxuV1PBAluk7NuN00HlrCKbo6BN3NUAdeA=; b=Qwq4jMS9Pt+LQxCRIdJaV5zQR1mRF9L2GHQppAcimZtUvzXnTKJBqb2QwfAL7fPvGVEQpP jyRXRaqDhQP0T+HV4xEP8CtCszwm4jQcjpnr/SZyliieYRGeEvC2SwVUyo95v8z6xKz1jB +8zaHJXQ37EXThh533WAwf7OsZ1SvyM= Date: Tue, 18 Dec 2018 16:24:13 +0100 From: Borislav Petkov To: Sergey Senozhatsky Cc: Sergey Senozhatsky , Peter Zijlstra , Petr Mladek , Steven Rostedt , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] printk: increase devkmsg write() ratelimit Message-ID: <20181218152413.GJ7485@zn.tnic> References: <20181218091842.4996-1-sergey.senozhatsky@gmail.com> <20181218104812.GC15430@hirez.programming.kicks-ass.net> <20181218111701.GA32522@jagdpanzerIV> <20181218114709.GF7485@zn.tnic> <20181218130750.GA665@tigerII.localdomain> <20181218142623.GH7485@zn.tnic> <20181218145558.GD665@tigerII.localdomain> <20181218150313.GI7485@zn.tnic> <20181218151455.GE665@tigerII.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20181218151455.GE665@tigerII.localdomain> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 19, 2018 at 12:14:55AM +0900, Sergey Senozhatsky wrote: > Right, but unlike log_buf_len, devkmsg is a bit close to a "binary" knob: > either all messages or none; ... which is perfectly fine for a debugging session. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.