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=-10.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 99928C48BDF for ; Thu, 24 Jun 2021 12:55:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7D3BF613F3 for ; Thu, 24 Jun 2021 12:55:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231765AbhFXM6H (ORCPT ); Thu, 24 Jun 2021 08:58:07 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:60536 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230236AbhFXM6G (ORCPT ); Thu, 24 Jun 2021 08:58:06 -0400 Received: from relay1.suse.de (relay1.suse.de [149.44.160.133]) by smtp-out1.suse.de (Postfix) with ESMTP id 92BE421986; Thu, 24 Jun 2021 12:55:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1624539346; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dLLHFzfm50RSkiAjN/HrgY4nObJsrbvcWNrlMkDYW74=; b=mG7SQoudASw5dBgrwS/TBK1WY4Bj6UX2q4Ha6iipzhvRZIJD7gzd/pUbIG6NA5mlUTnGUB 3OFlMSdOKjSnj83aAyuyISUNPa+jmkMQ++cO0K7+4mn5DpFnbqTBnVf8596uhV4jLR5YLx mteyO7Ay3U2gdMa+d2Z3OUwDF9oNcc8= Received: from suse.cz (unknown [10.100.224.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay1.suse.de (Postfix) with ESMTPS id 6713B25CCD; Thu, 24 Jun 2021 12:55:46 +0000 (UTC) Date: Thu, 24 Jun 2021 14:55:45 +0200 From: Petr Mladek To: John Ogness Cc: Sergey Senozhatsky , Steven Rostedt , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH printk v3 2/6] printk: track/limit recursion Message-ID: References: <20210624111148.5190-1-john.ogness@linutronix.de> <20210624111148.5190-3-john.ogness@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210624111148.5190-3-john.ogness@linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2021-06-24 13:17:44, John Ogness wrote: > Currently the printk safe buffers provide a form of recursion > protection by redirecting to the safe buffers whenever printk() is > recursively called. > > In preparation for removal of the safe buffers, provide an alternate > explicit recursion protection. Recursion is limited to 3 levels > per-CPU and per-context. > > Signed-off-by: John Ogness It looks pretty straightforward. Reviewed-by: Petr Mladek Best Regards, Petr