From owner-freebsd-x11@freebsd.org Thu Sep 26 01:20:02 2019 Return-Path: Delivered-To: freebsd-x11@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 DCF20F0223 for ; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46dxtV5YZTz4nl8 for ; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BEB9BF0222; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) Delivered-To: x11@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 BE876F0221 for ; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46dxtV4bRdz4nl7 for ; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 745B0F12E for ; Thu, 26 Sep 2019 01:20:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f178.google.com with SMTP id q203so446644qke.1 for ; Wed, 25 Sep 2019 18:20:02 -0700 (PDT) X-Gm-Message-State: APjAAAUgHMoCVzdD+XOvO4Xi1Y0kW7BpecPoOvoeKoIMRHDIxQw39cTb eil+5oeZHWym+0tLdUlyKw4co0KdPiYNOl70bso= X-Google-Smtp-Source: APXvYqxXnNsAtdN9t6lPWC1Zbnr9cFT/QFZUVkw4j+1h3fyfWFUQK0BsZuFJ3So+X0BQnrwK0P+sbu6W0sYBi+oFjAA= X-Received: by 2002:ae9:e88a:: with SMTP id a132mr952116qkg.120.1569460801887; Wed, 25 Sep 2019 18:20:01 -0700 (PDT) MIME-Version: 1.0 From: Kyle Evans Date: Wed, 25 Sep 2019 20:19:51 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: HEADS UP: memfd_create landed in head To: x11@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Sep 2019 01:20:02 -0000 Hi, Just a heads up- memfd_create(3) landed in head today (__FreeBSD_version 1300048); at least graphics/mesa-dri has relevant patches, and I seem to recall others. My test builds didn't seem to raise any problems, and the patches are all to !HAVE_MEMFD_CREATE blocks. autoconf should be doing the right thing here and picking up that it exists now. We don't support MFD_HUGETLB, but I didn't see any usage in mesa-dri or any other ports that used memfd_create. Please send any/all memfd_create related breakage my direction... this should be an improvement in some ways, as we can now properly support some of the cases that wanted !CLOEXEC but weren't getting it with how we emulated memfd_create, though I suspect there's no practical impact. Thanks, Kyle Evans