From owner-freebsd-current@freebsd.org Sun May 3 16:04:15 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 AF2682E15EA for ; Sun, 3 May 2020 16:04:15 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from 44-233-67-66-mail.ore.mailhop.org (44-233-67-66-mail.ore.mailhop.org [44.233.67.66]) (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 49FW5C1g08z3N7y for ; Sun, 3 May 2020 16:04:15 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1588521848; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=h9vUdTbiYZ6iZGZR4b+dJkgCfl3R6G/A/VeKjgvXfgFxWyhy1XHiFV1ToNEdBh6cTj2ZFE+HXVD0N ghzyMaJgWVgyU6pG6bwNJ0xgOvYBe3Jcj2dAZjsJx2oGHEaRN3AL6uu2mYTg1ogYHES1yglyopvGqV bdL6VXyAiNjdPRFHt8Zy7Rlqtz/MDeivXhzSWmjBbrq2rc1cUmchTAxJAHMAKsCgsdY2H6ro93LzMO UzbA4iR3xJIa5rBtOTfOrKVGfXwZ3yN/EG5bK11b9sUNS8ry7mdvvaFFKMgb8fXxshb1aISyrlJNaK m4e6O4giY1CoHy01fL9UKz58qnPv70Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=wOQ+nFvnqrygpWHDC8wrLV1cmNPPobp0XkcOXNZUhv4=; b=jxEwGM5nw0y+zFetr4/xCsmWWg5xoFV8ZVHohQ5iUSjsLsN8X25ZX8dbfj9WLLKskz4Z7mo+INItN F/uyATznOiiGL1CFrk53MM4d945kWu2fBGg7UQuVEjHRO3TPc0VQlE027C9RRutxT1gapM1rkwfoNi 4v0CrMDLCEdcxhIupKztdbDurESK8F1PLcvTIQzouztBtrhmTz22AuVjaGVslF7goPLCtQPSzCQrrk 8Eosz6AcNCEMBw8nWpfeld/XMKFX2Y+lszyhJOM1IVRz9daceJmIcsmNbqmT0VBXaNhvVg/kaXhuGH MvdHXN1m5Jevre4be4oLnmVFs0rHl+A== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=wOQ+nFvnqrygpWHDC8wrLV1cmNPPobp0XkcOXNZUhv4=; b=w6wjIceXo4VhX07a/DxSNOr986dCNWug1H0PhsQOk81vLs4dcqO46gnI/V/J7RJxZ2k6pc5Gm/cuN z94o1C9N9LvMaBiG8SuWb7kjIfNHV2P8g1s6cqFHyqSkZYN376BHkd1WjNFdqVCp2vlBR6tOJznEjO v6gNTm3VepJivTPVv77Yplj4iSmd0vIwBVe4eHPbiZaeWJX0yOU0AMUfUQ64u+RU9VOFMQOvzMeVP0 o12Cs1NiEv1DdRCo7aKqZX7QrWAm5tRLYPJWEMbk8VezZ8NRHfXHpCORTV4++2PyLOWpBOYEllE/Mf n/Ps+oJMgQCuMitDRb5Mfga1jGo1ANA== X-MHO-RoutePath: aGlwcGll X-MHO-User: b694888b-8d57-11ea-b10c-b5956a7dd1a1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id b694888b-8d57-11ea-b10c-b5956a7dd1a1; Sun, 03 May 2020 16:04:07 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 043G44q0042973; Sun, 3 May 2020 10:04:04 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: lock order reversal and poudriere From: Ian Lepore To: Kurt Jaeger , Grzegorz Junka Cc: bzeeb+freebsd+lor@zabbadoz.net, freebsd-current@freebsd.org Date: Sun, 03 May 2020 10:04:04 -0600 In-Reply-To: <20200502183634.GA90255@fc.opsec.eu> References: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> <20200502095404.GN39563@home.opsec.eu> <20200502183634.GA90255@fc.opsec.eu> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49FW5C1g08z3N7y X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.94 / 15.00]; TAGGED_RCPT(0.00)[freebsd,lor]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.96)[-0.961,0]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US]; NEURAL_HAM_LONG(-0.98)[-0.980,0] 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 16:04:15 -0000 On Sat, 2020-05-02 at 20:36 +0200, 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. > That LOR site hasn't been updated in years. Many many years. The sad truth appears to be that nobody cares about LORs anymore. The same ones have been there for years. Nobody fixes them, nobody does anything to suppress reporting them. We just keep pointing new users to a dead website because that has always been the only response available. > > 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. > Segfaults and other problems with a program named "conftest" while building ports is normal. Autotools' configure script writes and runs programs named conftest to detect the presence or absence of features or bugs. That doesn't mean every failure of a program named conftest is normal and expected, but in general it's not a thing to worry about. -- Ian