From owner-freebsd-current@freebsd.org Sun May 3 14:00:58 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 ED2C82DE46C for ; Sun, 3 May 2020 14:00:58 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49FSLx2NHsz3F47; Sun, 3 May 2020 14:00:56 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 49FSLk6wpRz3mGw; Sun, 3 May 2020 14:00:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1588514445; bh=rB8J2tl5FrI6SoF5u21QXbjI x4PC7WUvSa/MNGkrw8E=; b=WcbzUOPVqL2XfIpypaFH6dJwGxHSep9kFAy0G4qz QQPj95SM4L+fSAML7WzhDlfS41xLr7v6ZfV3saH9W04lHNPE9GAOE1RuYddfMIPZ dtaRI5BQPkE11aS3Szh7cWR81BDluCP4Vwlm002tK8nL8gckg6hbayikkXucTmUx zR8= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id zEWhmXciQ24N; Sun, 3 May 2020 14:00:45 +0000 (UTC) Received: from vivi.daemonic.se (vivi.daemonic.se [IPv6:2001:470:dca9:2::4]) by mail.daemonic.se (Postfix) with ESMTPSA id 49FSLh6xQ1z3lb5; Sun, 3 May 2020 14:00:44 +0000 (UTC) Subject: Re: lock order reversal and poudriere To: Kurt Jaeger , Grzegorz Junka Cc: bzeeb+freebsd+lor@zabbadoz.net, freebsd-current@freebsd.org References: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> <20200502095404.GN39563@home.opsec.eu> <20200502183634.GA90255@fc.opsec.eu> From: Niclas Zeising Message-ID: Date: Sun, 3 May 2020 16:00:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200502183634.GA90255@fc.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49FSLx2NHsz3F47 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=daemonic.se header.s=20151023 header.b=WcbzUOPV; dmarc=pass (policy=none) header.from=daemonic.se; spf=pass (mx1.freebsd.org: domain of zeising@daemonic.se designates 2607:f740:d:20::25 as permitted sender) smtp.mailfrom=zeising@daemonic.se X-Spamd-Result: default: False [-6.69 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[daemonic.se:s=20151023]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd,lor]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[daemonic.se:+]; DMARC_POLICY_ALLOW(-0.50)[daemonic.se,none]; IP_SCORE(-3.69)[ip: (-9.72), ipnet: 2607:f740:d::/48(-4.86), asn: 36236(-3.80), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[] 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: Sun, 03 May 2020 14:00:59 -0000 On 2020-05-02 20:36, Kurt Jaeger wrote: > 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. > >> Thanks Kurt. I can't find those two specific LORs in the list on that >> page. The page also says to report them using a link, which leads to 404 >> :-), or on this mailing list, which I did. I am not sure what else should >> I do. > > I don't know, either 8-} bz@ is in Cc:, so he'll probably know what > to do. > >> How do I know if I have got a backtrace? >> >> Are those errors: >> >> pid 43297 (conftest), jid 5, uid 0: exited on signal 11 >> >> related or it's a different issue? > > I think that's a different issue. > conftest is when configure scripts do things. Configure works a lot by compiling (and sometimes running) small snippets of code to figure out what's going on. Sometimes those snippets core dump. It's all normal. Regards -- Niclas