Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp6873318rwd; Tue, 6 Jun 2023 03:15:28 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4hc6Cv64Vc4YwwswksWvFJ2OGliCpX1Kw2d2XmN6xt/E3B5jIlj6KoHwmsALOQcw0MJF2K X-Received: by 2002:a05:6214:da2:b0:62b:437b:54c2 with SMTP id h2-20020a0562140da200b0062b437b54c2mr1480072qvh.19.1686046527844; Tue, 06 Jun 2023 03:15:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686046527; cv=none; d=google.com; s=arc-20160816; b=edRHGU2Waw+DV7x+TSejzEgsFPrLjPC5ToQHo4DfP7Nh81AhnCHPp+66i9pD8u64AZ WOUAcQ2wm5A/2GeryE+S7C9J8tTPFUjPmHVdTEPuOpENBI5kyCV1X1n2ywMY+QYgoODj HHNdki//P9HWEMaeogx9jTMAHcQKCbXDGsqZabChiDNKQYGG4X3UyxQgoNSXsdQGiFfq TPI6W3C7sdTRyuo2/1GhPqIzaEJSVtwl3a1OCwDhm/S2JchKBfLpUNQLu+wuS/gInF0x /ZANP7U4rdexu8CWwoHzmusBSaIT5yz5yJBr6AVH+OT1ZGLlWBFFKCJgq1abjF8bjDT0 J2+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature :dkim-signature:date; bh=KSa4OY9dsWXX7LG19K4ps06QwMPn/kJbzHoa0LvQ/dI=; b=osa1I/DsIAhDVqtdF+7ifw3oyy7t11HYmeuL0EdqvvUtR2xYIyI9uDELODG2g+67ny rNF9ULgReCZoNUduP1Jv54AJ32RwcP91D1I5hgZEmFNspILCGOSZaZEtHX85yiG+EHA2 KG177k9aUItFbz+9nTA7xfHLlGzuKAR/Hz/eov5KOeLTYIODb9rtaLlrnjYeYbzJLmWi xRIRbo3iidrx/myHkyGBZMLNiJMMARrhK/AlxTdpirg0LFhTf3EQEHL3UXUg17M1PNyv KaEqU7vJyDj2Rl/ucNESAl6NGYgnhGRv4eupocWBC85QnCmJlMjKPdFyls4SFFNbYF2n oe8g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=kD6EPcw8; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t7-20020ad45bc7000000b0061b60dc53fesi5948231qvt.606.2023.06.06.03.15.12; Tue, 06 Jun 2023 03:15:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=kD6EPcw8; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234915AbjFFJtR (ORCPT + 99 others); Tue, 6 Jun 2023 05:49:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237540AbjFFJtB (ORCPT ); Tue, 6 Jun 2023 05:49:01 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C4EA010C0; Tue, 6 Jun 2023 02:48:58 -0700 (PDT) Date: Tue, 6 Jun 2023 11:48:55 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1686044936; 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: in-reply-to:in-reply-to:references:references; bh=KSa4OY9dsWXX7LG19K4ps06QwMPn/kJbzHoa0LvQ/dI=; b=kD6EPcw8dfX8tpFG4VG8J3fP0j3U6yVTftzZul3WT4zmlELTbQOT5cnUQvQlKUhdLh8Hbg t2OO5xKtxJTTdTicNTD8UGPPkCzPzIQvZKnNI8YEii8e8jLBYMpAcQQV+n8ePSaC7/g5D2 trt7kdkXsSUDhsQjZt7B5In/yPv4E1/WFQQq53FoxYk+IhBPgegvZdsYLz1bXSNbS4TPeo gGWXdfdr+d/HxR0UacwZmwpBVqmk5tGfRLL22eTzC/T+ETyO6b8TMD1fUgtM5ELXmA6ahr bJ6XpGSE1SNRCHxt1iVHrY4297Kn3R/jdmvng2cLleiSojDUFJQtA4W8M5qvQw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1686044936; 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: in-reply-to:in-reply-to:references:references; bh=KSa4OY9dsWXX7LG19K4ps06QwMPn/kJbzHoa0LvQ/dI=; b=CAkW+0ZxzgX8EbTa5o4RZs12jtVQjzM2EIG7LLHwHbFe93r/jfHiMwkAhjXeMdJrnwnkyz r7nurGx2ELrFK0Ag== From: Sebastian Andrzej Siewior To: "Luis Claudio R. Goncalves" Cc: LKML , linux-rt-users , stable-rt , Steven Rostedt , Thomas Gleixner , Carsten Emde , Daniel Wagner , Tom Zanussi , Clark Williams , Mark Gross , Pavel Machek , Jeff Brady Subject: Re: [ANNOUNCE] 5.10.180-rt88 Message-ID: <20230606094855.v8zhk78I@linutronix.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023-05-30 16:46:28 [-0300], Luis Claudio R. Goncalves wrote: > Hello RT-list! Hi, > Support for deferred printing was removed in v5.10-rc1-rt1 by commit > 9153e3c5cb0c9 ("printk: remove deferred printing"). Sorry for not getting back to earlier, where you proposed the change. > diff --git a/include/linux/printk.h b/include/linux/printk.h > index 83c7734e98025..92e0656841128 100644 > --- a/include/linux/printk.h > +++ b/include/linux/printk.h > @@ -609,7 +609,7 @@ static inline void print_hex_dump_debug(const char *prefix_str, int prefix_type, > #define print_hex_dump_bytes(prefix_str, prefix_type, buf, len) \ > print_hex_dump_debug(prefix_str, prefix_type, 16, 1, buf, len, true) > > -#ifdef CONFIG_PRINTK > +#if defined(CONFIG_PRINTK) && !defined(CONFIG_PREEMPT_RT) > extern void __printk_safe_enter(void); > extern void __printk_safe_exit(void); This needs to go entirely. The "new" printk code does not need this safe functions also for !RT. > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index 5f1c50a6bebc5..7e65e3ef16e3a 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -6057,7 +6057,6 @@ static void __build_all_zonelists(void *data) > * tty_insert_flip_string_and_push_buffer() on other CPU might be > * calling kmalloc(GFP_ATOMIC | __GFP_NOWARN) with port->lock held. > */ > - printk_deferred_enter(); That is okay. However the commit, that introduced this a992c387b4118 ("mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock") also added a local_irq_safe a little higher up and it has to go, too. The code as-is should produce warnings once it enters this path. > write_seqlock(&zonelist_update_seq); > > #ifdef CONFIG_NUMA Sebastian