From owner-freebsd-current@freebsd.org Sat May 2 09:54:14 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1BF2C2CA51E for ; Sat, 2 May 2020 09:54:14 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Dkwj3XBlz40jR for ; Sat, 2 May 2020 09:54:13 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD)) (envelope-from ) id 1jUoqS-000Cbs-34; Sat, 02 May 2020 11:54:04 +0200 Date: Sat, 2 May 2020 11:54:04 +0200 From: Kurt Jaeger To: Grzegorz Junka Cc: freebsd-current@freebsd.org Subject: Re: lock order reversal and poudriere Message-ID: <20200502095404.GN39563@home.opsec.eu> References: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> X-Rspamd-Queue-Id: 49Dkwj3XBlz40jR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.69 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.83)[-0.828,0]; NEURAL_HAM_LONG(-0.87)[-0.866,0]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2020 09:54:14 -0000 Hi! > I am compiling some packages with poudriere on 13-current kernel. I > noticed some strange messages printed into the terminal and dmesg: > > lock order reversal: [...] > Are those the debug messages that aren't visible on non-current kernel > and should they be reported? Yes, they should be checked and reported. For more details see: http://sources.zabbadoz.net/freebsd/lor.html There's a webpage with a list of all known LORs and a way to report new LORs. -- pi@opsec.eu +49 171 3101372 Now what ?