From owner-freebsd-arch@freebsd.org Mon Mar 26 09:52:57 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBA6AF5A57F for ; Mon, 26 Mar 2018 09:52:57 +0000 (UTC) (envelope-from ahmadvip077@icloud.com) Received: from st42p59im-ztdg12250501.me.com (st42p59im-ztdg12250501.me.com [17.36.65.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 896BD75508 for ; Mon, 26 Mar 2018 09:52:57 +0000 (UTC) (envelope-from ahmadvip077@icloud.com) Received: from process-dkim-sign-daemon.st42p59im-ztdg12250501.me.com by st42p59im-ztdg12250501.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P6600900WJD3N00@st42p59im-ztdg12250501.me.com> for freebsd-arch@FreeBSD.org; Mon, 26 Mar 2018 08:52:51 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1522054371; bh=Ksiyrmq5gx7NUq+DVNwm3jH9cVGyFPnVqRc7SOGuU8s=; h=Content-type:From:MIME-version:Date:Subject:Message-id:To; b=nWWcg3tyuX3bX2XTty7ClDHEmWGTueCADzSpCs5Ki+AF5V51zZFLdHtmTFfgFX21d SMOl01x9mnyog73mFHofgG0MjNgLQJuqFbJhWdErdTtKDtAV+OpFTyYd8qFdjeRW/N 1D9etIZa/cD+lSOXF+Y7SIrNNzmpEyVmg2/xkKjyWFfl7vcjque1hFhHnMswAgYM0O LAu5P4bZbtppFgm+zawTwioP7Pj/2Z3wK1v2Rnz0vHJoWK3cmbeySmrcEYHBw0RJ9a p/UlyyFx0jkoUTygzPxcQsLuulXoYn73sV4VaY8Wr/CVLw3I3Le4m5DpKlRVQ2PsQ/ hWUZEx+j63S+A== Received: from icloud.com ([127.0.0.1]) by st42p59im-ztdg12250501.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P660096YWNY1K00@st42p59im-ztdg12250501.me.com> for freebsd-arch@FreeBSD.org; Mon, 26 Mar 2018 08:52:51 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-26_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1803260098 From: Ahmad Vip MIME-version: 1.0 (1.0) Date: Mon, 26 Mar 2018 11:52:45 +0300 Subject: A Message-id: <1A009201-C291-40B7-A5B4-F080985E419F@icloud.com> To: freebsd-arch@FreeBSD.org X-Mailer: iPhone Mail (15C202) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 09:52:58 -0000 DQoNCuKAj+KAq9mF2YYg2KfZhNmAIGlQaG9uZSDYp9mE2K7Yp9i1INio2YrigKw= From owner-freebsd-arch@freebsd.org Mon Mar 26 15:18:56 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2851F4CAC8 for ; Mon, 26 Mar 2018 15:18:55 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 875838247F for ; Mon, 26 Mar 2018 15:18:55 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 44091F4CAC6; Mon, 26 Mar 2018 15:18:55 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31C05F4CAC5 for ; Mon, 26 Mar 2018 15:18:55 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (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 C722F8247D; Mon, 26 Mar 2018 15:18:53 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id 1DC7737604F4; Mon, 26 Mar 2018 17:09:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 110A937603B9; Mon, 26 Mar 2018 17:09:16 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id U91PFkAYLHh4; Mon, 26 Mar 2018 17:09:16 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id F2D673760393; Mon, 26 Mar 2018 17:09:15 +0200 (CEST) Date: Mon, 26 Mar 2018 17:09:15 +0200 (CEST) From: Emeric POUPON To: John Baldwin Cc: arch@freebsd.org Message-ID: <411722908.3896403.1522076955839.JavaMail.zimbra@stormshield.eu> In-Reply-To: <3790717.UIxaijsHl3@ralph.baldwin.cx> References: <3790717.UIxaijsHl3@ralph.baldwin.cx> Subject: Re: Ranting about OCF / crypto(9) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Thread-Topic: Ranting about OCF / crypto(9) Thread-Index: lsICCUX7Ybc1rzKmA1kjPsh55wjdOA== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 15:18:56 -0000 > - We need to not treat accelerated software (e.g. AES-NI) as a > hardware interface. Right now OCF's model of priorities when > trying to choose a backend driver for a session only has two > "levels" software vs hardware and aesni(4) (and the ARMv8 variant) > are lumped into the hardware bucket so that they have precedence > over the "dumb" software implementation. However, the accelerated > software algorithms do need some of the same support features of > the "dumb" software implementation (such as being scheduled on a > thread pool to use CPU cycles) that are not needed by other "hardware" > engines. OCF needs to understand this distinction. Hello, As you already mentioned before, we cannot benefit from aesni(4) with IPSec on Intel platforms, except when using AEAD algorithms like GCM. Maybe we should not expose accelerated software (e.g. AESNI) as crypto drivers. Plugging them directly into cryptosoft brings some benefits: - no duplicate code about crypto session handling, - partially accelerated crypto (e.g. aesni for AES-CBC, soft for SHA256. Useful for IPSec), - possible use of the 'async' mode to process crypto jobs using a thread pool. Actually that's something we already did using straightforward, internal patches. Now I would like to know what you think about this idea and what you would suggest to achieve this? (using a new framework?) Regards, Emeric From owner-freebsd-arch@freebsd.org Mon Mar 26 19:54:03 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADB2CF65DE4 for ; Mon, 26 Mar 2018 19:54:03 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 31E8F7042F; Mon, 26 Mar 2018 19:54:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id 0YBjf6n1sU5pn0YBmfwVwS; Mon, 26 Mar 2018 13:53:55 -0600 X-Authority-Analysis: v=2.3 cv=Tai4SyYh c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=v2DPQv5-lfwA:10 a=xfDLHkLGAAAA:8 a=VwQbUJbxAAAA:8 a=20KFwNOVAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=0WsirsSEdtL0j8BrKcMA:9 a=CjuIK1q_8ugA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=AjGcO6oz07-iQ99wixmX:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id D6A2E986; Mon, 26 Mar 2018 12:53:50 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w2QJrYZc028257; Mon, 26 Mar 2018 12:53:34 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w2QJrYQm028227; Mon, 26 Mar 2018 12:53:34 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201803261953.w2QJrYQm028227@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: cem@freebsd.org cc: "Luis R. Rodriguez" , "Darrick J. Wong" , Carlos Maiolino , "freebsd-arch@freebsd.org" Subject: Re: FreeBSD and xfsprogs ? In-Reply-To: Message from Conrad Meyer of "Fri, 23 Mar 2018 12:28:07 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Mar 2018 12:53:33 -0700 X-CMAE-Envelope: MS4wfOQ+uhYQVnlr+/6z3/BB9JpqTT8Rf136sJfdbsYEDKhxBH+oc1rJfuGupdfpIB3ozaeOzx7UjZDNmZlQ4kQt/eYW1uwE73IZUc8UjMc+hH+mL8tqbQ3G fmqfwk2FlbJnqWhaeTyYe8lFGMo/ogOytxI+7SoRaWqNmpdEeV03IIY4F5e4qcgTnx+vwMKlY63aTjwfH6E/kIT4CQZD9W252Mjx+k0WRQnNbNjSiM+SjRJF HqnxV0pnqdkdwYEPy5mIRW5UT3miKc7GIuqxXzwp1t3qjYJGDLHgCYzZETfk/pPWBHV2AqfmI7vOa1CU+HP8Wg== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 19:54:03 -0000 In message , Conrad Meyer writes: > On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote > : > > On the Linux xfs development list there is an RFC to remove IRIX, > > Darwin, and FreeBSD support from xfsprogs, the userspace program used > > to create/interact with XFS filesystems. Just wanted to poke and check > > to ensure that FreeBSD is not interested in XFS, if this is incorrect > > now would be the good time to chime into the list and discussion. > > > > [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys. > redhat.com > > Hi Luis, > > FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port > incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate > xfsprogs retaining FreeBSD support at least for creating or modifying > offline XFS filesystems, if it isn't too painful for you. fusefs-lkl is flagged broken as of r465272. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-arch@freebsd.org Mon Mar 26 20:04:05 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AF3EF663D3 for ; Mon, 26 Mar 2018 19:59:27 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EE1D7066B for ; Mon, 26 Mar 2018 19:58:07 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f174.google.com with SMTP id d7so9370808ioc.11 for ; Mon, 26 Mar 2018 12:58:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=RcIPfMlJfdKZuYGTk7O4ajr9zpJofb/jEsXG4zGKFXw=; b=taelt9ejNFVlqgAjqwLAVvmBIiWH0yGfYJfmwekTfv5HMUBXZ4jhn8YeSjCES0LWvu 1eAp32+uXz8m4YosWDTZ0CHxSo+thA2qbCpBLG7xoE5TxQ8EZrCVRZf9RcsUYyuIwheo eSEg15QNvIGpiZAjfyNYX/CL207RRlOj/RBwBs5guM0vW022m5zhn9rFtJWlo0mJgGHZ p/ePiQ2x5/Th4+JP8Lhhn0gN9mrIOnkxJGy4eJ4XPcUn0BpXUL3txnQCOwQEywfJ6ugI hk1bIyKovUfb7ukCa5YBfeofVuJe5qh0HuptngpKOheRXs+7T3eMNtcv4ih3gAEq6yge mvLQ== X-Gm-Message-State: AElRT7HtH7UtMVukmskjBt2kMZeCC69Gro+EtB8smXiPGm3hInpp+MMr FGJC17BOWN3PS4t1OHD5txdUVRHw X-Google-Smtp-Source: AG47ELu1qM3ArPQGtE4ieqQAwAUK43d5nzrihJxFgtyHZJZkPmdFKiw7PcovRW367xnFx1EGqfPnfQ== X-Received: by 10.107.4.196 with SMTP id 187mr41180322ioe.146.1522094276724; Mon, 26 Mar 2018 12:57:56 -0700 (PDT) Received: from mail-it0-f45.google.com (mail-it0-f45.google.com. [209.85.214.45]) by smtp.gmail.com with ESMTPSA id u96sm9849150iou.58.2018.03.26.12.57.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Mar 2018 12:57:56 -0700 (PDT) Received: by mail-it0-f45.google.com with SMTP id d13-v6so12271428itf.0 for ; Mon, 26 Mar 2018 12:57:56 -0700 (PDT) X-Received: by 2002:a24:2f8d:: with SMTP id j135-v6mr24695303itj.53.1522094276047; Mon, 26 Mar 2018 12:57:56 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.62.19 with HTTP; Mon, 26 Mar 2018 12:57:55 -0700 (PDT) In-Reply-To: <201803261953.w2QJrYQm028227@slippy.cwsent.com> References: <201803261953.w2QJrYQm028227@slippy.cwsent.com> From: Conrad Meyer Date: Mon, 26 Mar 2018 12:57:55 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD and xfsprogs ? To: Cy Schubert Cc: "Luis R. Rodriguez" , "Darrick J. Wong" , Carlos Maiolino , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 20:04:05 -0000 Yeah, someone broke the build recently via a base toolchain change or a ports framework/compiler change. I don't think that changes anything. On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert wrote: > In message il.com> > , Conrad Meyer writes: >> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote >> : >> > On the Linux xfs development list there is an RFC to remove IRIX, >> > Darwin, and FreeBSD support from xfsprogs, the userspace program used >> > to create/interact with XFS filesystems. Just wanted to poke and check >> > to ensure that FreeBSD is not interested in XFS, if this is incorrect >> > now would be the good time to chime into the list and discussion. >> > >> > [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys. >> redhat.com >> >> Hi Luis, >> >> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port >> incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate >> xfsprogs retaining FreeBSD support at least for creating or modifying >> offline XFS filesystems, if it isn't too painful for you. > > fusefs-lkl is flagged broken as of r465272. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > From owner-freebsd-arch@freebsd.org Tue Mar 27 14:09:17 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAC0DF57189; Tue, 27 Mar 2018 14:09:16 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50C4487365; Tue, 27 Mar 2018 14:09:16 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f51.google.com with SMTP id e5-v6so33553827lfb.7; Tue, 27 Mar 2018 07:09:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pm5W21szaK9mjKeKernvK6J9t5H35csrSsNI0hje+mY=; b=c7ZC6mkZpFqT5BjX5OAG3nJz9Vaxg4EjyjU7DtGoJs/BlZmglJi8tgiOdr+JdzRQ7A eGZaYOZntaXRAgHNh1yNwTgdpif1nbEHWgg7Q2fOZJazbaN7orDFOvKi6DpD8lrMcqHC BNLFBBwI6svqFEvHtHn8bsDdWKcfTC6PvL9OfvhlusCKNpGZqnh57Oelg2UI6fN6N5as 2D7dfG1rLED3spGSZmLnJHzsDg07YGY1h8hgcPs0BJ6V54MmXHeBjHQXB37G/Cs2Qx6i E+LkpxiiUXEPopmT/WGMW6HUCSujG8GNjPbDqPGMPCZw5eicSeHDshRurwsb3/K9WmH3 G/oA== X-Gm-Message-State: AElRT7FIxQ7z6VvrK13qOsyUW18U/f2j49SJn1+JsSBEcK2fsjukKDLj QdNJ9EJA8llooTN8tvMAnLIUL8Uv X-Google-Smtp-Source: AG47ELsTQXhTzxUEHjT3u31wvMJkYtTVlTkmjrDTw9n+4VrARG9IzUPtn8e/ovX88ewT/jNKT4/o8Q== X-Received: by 10.46.4.149 with SMTP id a21mr30870864ljf.138.1522159749011; Tue, 27 Mar 2018 07:09:09 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id 1sm238322lje.38.2018.03.27.07.09.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Mar 2018 07:09:07 -0700 (PDT) Subject: Re: geom->access problem and workaround To: Warner Losh Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , freebsd-geom@freebsd.org References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> From: Andriy Gapon Message-ID: <356b875d-baee-c60b-fa76-531d3de22676@FreeBSD.org> Date: Tue, 27 Mar 2018 17:09:06 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 14:09:17 -0000 On 23/03/2018 15:31, Warner Losh wrote: > > > On Fri, Mar 23, 2018 at 4:38 AM, Andriy Gapon > wrote: > > On 12/03/2018 20:07, Poul-Henning Kamp wrote: > > If we want to have an architectural sound way to do slow operations > > before any "user-I/O" is initiated, the right way to do so is to > > define new BIO_OPEN and BIO_CLOSE  operation, and insist via asserts > > than all BIO_{READ|WRITE|DELETE} are wrapped in these. > > > In support of this proposal I want to add another example. > The problem is not only with doing I/O in access, but also with doing blocking > I/O in the normal I/O path. > The following happened when a userland program tried to read from a CD-ROM while > its tray was open: > > panic: sleepq_add: td 0xfffff80008e1c000 to sleep on wchan 0xfffff801e58b8048 > with sleeping prohibited > > > cdstrategy shouldn't be sleeping. It can start I/O, but it can't wait for it to > finish. strategy has been a no-sleep-zone since at least v6. The fact it's > waiting for prevent is the bug here. I guess that what you suggest is that cdstrategy should place the incoming request on a queue and then start a state machine for issuing management commands and handling their completions. After the state machine goes back to the normal state only then the driver would start processing queued I/O requests. Something like that? -- Andriy Gapon From owner-freebsd-arch@freebsd.org Tue Mar 27 16:17:29 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51710F66946 for ; Tue, 27 Mar 2018 16:17:29 +0000 (UTC) (envelope-from darrick.wong@oracle.com) Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "aserp2130.oracle.com", Issuer "Symantec Class 3 Secure Server CA - G4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C40816F402; Tue, 27 Mar 2018 16:17:28 +0000 (UTC) (envelope-from darrick.wong@oracle.com) Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2RG4xkM083240; Tue, 27 Mar 2018 16:17:19 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=corp-2017-10-26; bh=m2PW0w6o2wrSeHoeMGsYsbLs0d1gaEI8GlFRgym3z7g=; b=HhmAY8MioDbvEuowY0DWAPS9IJ3pB1Ta2IP8aXEg8giNbrgxLei3HhXv3+Cb29GFzSEg 0A4qyiemmuP1I2Zb6af6stR8/ykM0hIe8p+TGrzrUbSNwx/IXosWNMNLFHMZgN1mVVLN zU6opARL92nOQi6C27qLssY+YrovLj87LGuVQ7PqkV7GZR2F3Fn5yHOdDZRu44UupuFr p9er/nMH0nTjcWUvJApKoboPSWiDMCZiz/EJBDQviiyJRcIt/5xmKGY6/NEERIGXM1ff HR7uvD3YmPJcpl6RTOCCnq+5tcgh+5mgx85nFAg3wT0XHrd2rlBLLaFflOXYm4oZoRbB 0w== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp2130.oracle.com with ESMTP id 2gys2p04t4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Mar 2018 16:17:19 +0000 Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w2RG7HSo015439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Mar 2018 16:07:17 GMT Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2RG7GS0017258; Tue, 27 Mar 2018 16:07:16 GMT Received: from localhost (/67.169.218.210) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 27 Mar 2018 09:07:16 -0700 Date: Tue, 27 Mar 2018 09:07:14 -0700 From: "Darrick J. Wong" To: Conrad Meyer Cc: Cy Schubert , "Luis R. Rodriguez" , Carlos Maiolino , "freebsd-arch@freebsd.org" , Eric Sandeen , xfs Subject: Re: FreeBSD and xfsprogs ? Message-ID: <20180327160714.GB4818@magnolia> References: <201803261953.w2QJrYQm028227@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8844 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803270161 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 16:17:29 -0000 [cc the xfsprogs maintainer] [cc xfs list] On Mon, Mar 26, 2018 at 12:57:55PM -0700, Conrad Meyer wrote: > Yeah, someone broke the build recently via a base toolchain change or > a ports framework/compiler change. I don't think that changes > anything. > > On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert wrote: > > In message > il.com> > > , Conrad Meyer writes: > >> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote > >> : > >> > On the Linux xfs development list there is an RFC to remove IRIX, > >> > Darwin, and FreeBSD support from xfsprogs, the userspace program used > >> > to create/interact with XFS filesystems. Just wanted to poke and check > >> > to ensure that FreeBSD is not interested in XFS, if this is incorrect > >> > now would be the good time to chime into the list and discussion. > >> > > >> > [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys. > >> redhat.com > >> > >> Hi Luis, > >> > >> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port > >> incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate Yikes. I'm curious, how many people use fusefs-lkl? Eric will have more to say about this, but is your xfsprogs port still on 3.2.4 because ./configure can't find libblkid? --D > >> xfsprogs retaining FreeBSD support at least for creating or modifying > >> offline XFS filesystems, if it isn't too painful for you. > > fusefs-lkl is flagged broken as of r465272. > > > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > > The need of the many outweighs the greed of the few. > > > > From owner-freebsd-arch@freebsd.org Tue Mar 27 16:48:35 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21D78F69A17 for ; Tue, 27 Mar 2018 16:48:35 +0000 (UTC) (envelope-from sandeen@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 B933D712A6; Tue, 27 Mar 2018 16:48:34 +0000 (UTC) (envelope-from sandeen@redhat.com) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BD0FE2F30C2; Tue, 27 Mar 2018 16:48:33 +0000 (UTC) Received: from [IPv6:::1] (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B7DBA5E1A5; Tue, 27 Mar 2018 16:48:29 +0000 (UTC) Subject: Re: FreeBSD and xfsprogs ? To: "Darrick J. Wong" , Conrad Meyer Cc: Cy Schubert , "Luis R. Rodriguez" , Carlos Maiolino , "freebsd-arch@freebsd.org" , xfs References: <201803261953.w2QJrYQm028227@slippy.cwsent.com> <20180327160714.GB4818@magnolia> From: Eric Sandeen Message-ID: <8396fd92-3a64-a84f-b110-7edc6f0844b0@redhat.com> Date: Tue, 27 Mar 2018 11:48:29 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180327160714.GB4818@magnolia> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Tue, 27 Mar 2018 16:48:33 +0000 (UTC) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 16:48:35 -0000 On 3/27/18 11:07 AM, Darrick J. Wong wrote: > [cc the xfsprogs maintainer] > [cc xfs list] Yes, thanks. > On Mon, Mar 26, 2018 at 12:57:55PM -0700, Conrad Meyer wrote: >> Yeah, someone broke the build recently via a base toolchain change or >> a ports framework/compiler change. I don't think that changes >> anything. >> >> On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert wrote: >>> In message >> il.com> >>> , Conrad Meyer writes: >>>> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote >>>> : >>>>> On the Linux xfs development list there is an RFC to remove IRIX, >>>>> Darwin, and FreeBSD support from xfsprogs, the userspace program used >>>>> to create/interact with XFS filesystems. Just wanted to poke and check >>>>> to ensure that FreeBSD is not interested in XFS, if this is incorrect >>>>> now would be the good time to chime into the list and discussion. >>>>> >>>>> [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys. >>>> redhat.com >>>> >>>> Hi Luis, >>>> >>>> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port >>>> incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate > Yikes. I'm curious, how many people use fusefs-lkl? > > Eric will have more to say about this, but is your xfsprogs port still > on 3.2.4 because ./configure can't find libblkid? So: At this point, it seems like if you're still on a 4 year old xfsprogs release with custom patches due to build problems we've never heard about, there doesn't seem to be a very strong effort to keep XFS on FreeBSD thriving. And, given that you're stuck on 3.2.4, removing support from 4.16.0 won't change your situation anyway. Are people using this? Is anyone dedicated to maintaining it, or is it just kind of floating along at this point? I'd rather not keep non-building freebsd code around just in case; I'd like to either see someone take ownership to get freebsd properly building upstream, or just drop it and let FreeBSD keep patching on the side as you've been doing for a few years anyway. Thoughts? Thanks, -Eric From owner-freebsd-arch@freebsd.org Tue Mar 27 17:17:12 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE646F6C8AA for ; Tue, 27 Mar 2018 17:17:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE2FD72F54 for ; Tue, 27 Mar 2018 17:17:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22d.google.com with SMTP id j137-v6so184069ita.1 for ; Tue, 27 Mar 2018 10:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=htZ3c5ckamE/9tMtANru4YOOM7xskRKeMlvbPUe0XpY=; b=eyDILg3DpxHQm4iTai1KVMlcrkzWJATnKxEN6lud8AujfCWuj+1AlV1K6Fs7qqZj/2 mM7+asGOVKjnRlF/yG0ivwhNVSA5UvmOvV3tdwackVJb8S8b/8bLhyXeabiAQBFkHOFI zYLLC659TRn7Bn59ex1zp0GgpmK52v3jDSDl1FYUWYvqG3ZVtv5PMCqGQxf5wpoGG+5c AsnFmBgS4amKrGjnUoqfdQKoVRFYD10pR2vpscKQKYQWZ6zbvQRu5gliA2rwa1x+kKiI qOgTcJ2z1Wg8V8OsBYZLeBGYOsP1/91cc9ZOKhNgwWB3yiMoVx1d7oSbzAyBPgUnPx1Q XZ/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=htZ3c5ckamE/9tMtANru4YOOM7xskRKeMlvbPUe0XpY=; b=Xyywcdk0PpDxdxzpXiKRkUzq77EMPUqXWouRykGMbYrfz5C/YYaZILHlzKir0Dn1XY 2ZXNNZ6TBil+xWKW6SIOLaT07K1IKEDC7ep1v6zEF4idIDemLYh4lJOisTFVuP+UoE+y NEPHtGCkvg6o9/3bWmo+8IfmaMJzrpgI9J1f9cXeDntqoy5iIkHC63izI0WxZP01ZKk0 rt4DaJLU9CqDNcnRfYkvJlnv7PD4h73o2Veo6vIPhIiN3SG6VKXGjrbwIpFo9bQNP6Cn FeKt9fuTFy8cJDtSxPWQ5Don/Ltih6Zk2mEqnvJjCXQdkYp5YCECso4sVZN3rwyop+YU CEgQ== X-Gm-Message-State: AElRT7GUT0ZgTC7BUnVsi21MvrGhERozlIZwKfSdNGpcV3/aIQmOsw3F srftPTx1RIADAQOdvA5lorYyo9IV5iwpKJAQeP1joQ== X-Google-Smtp-Source: AIpwx4+fNJxtgPXf2Apn7l9gOT6WtjBCjfKJyT8go0iEQeZH71GSt7N5VXfbIErH6k/bK7AFyAd0ZiF848+8BXGzNms= X-Received: by 2002:a24:b649:: with SMTP id d9-v6mr117608itj.51.1522171029929; Tue, 27 Mar 2018 10:17:09 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Tue, 27 Mar 2018 10:17:08 -0700 (PDT) X-Originating-IP: [192.173.67.1] Received: by 10.79.203.196 with HTTP; Tue, 27 Mar 2018 10:17:08 -0700 (PDT) In-Reply-To: <356b875d-baee-c60b-fa76-531d3de22676@FreeBSD.org> References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> <356b875d-baee-c60b-fa76-531d3de22676@FreeBSD.org> From: Warner Losh Date: Tue, 27 Mar 2018 10:17:08 -0700 X-Google-Sender-Auth: 5AzV3bO-RwvZyu47HZQ9x6j32yw Message-ID: Subject: Re: geom->access problem and workaround To: Andriy Gapon Cc: Poul-Henning Kamp , freebsd-arch@freebsd.org, freebsd-geom@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 17:17:12 -0000 On Mar 27, 2018 7:09 AM, "Andriy Gapon" wrote: On 23/03/2018 15:31, Warner Losh wrote: > > > On Fri, Mar 23, 2018 at 4:38 AM, Andriy Gapon > wrote: > > On 12/03/2018 20:07, Poul-Henning Kamp wrote: > > If we want to have an architectural sound way to do slow operations > > before any "user-I/O" is initiated, the right way to do so is to > > define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts > > than all BIO_{READ|WRITE|DELETE} are wrapped in these. > > > In support of this proposal I want to add another example. > The problem is not only with doing I/O in access, but also with doing blocking > I/O in the normal I/O path. > The following happened when a userland program tried to read from a CD-ROM while > its tray was open: > > panic: sleepq_add: td 0xfffff80008e1c000 to sleep on wchan 0xfffff801e58b8048 > with sleeping prohibited > > > cdstrategy shouldn't be sleeping. It can start I/O, but it can't wait for it to > finish. strategy has been a no-sleep-zone since at least v6. The fact it's > waiting for prevent is the bug here. I guess that what you suggest is that cdstrategy should place the incoming request on a queue and then start a state machine for issuing management commands and handling their completions. After the state machine goes back to the normal state only then the driver would start processing queued I/O requests. Something like that? Yes. Something like that. If we have to restart the discovery state machine, that has to freeze the queues until that is done. Warner From owner-freebsd-arch@freebsd.org Tue Mar 27 22:32:30 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23177F6593E for ; Tue, 27 Mar 2018 22:32:30 +0000 (UTC) (envelope-from david@fromorbit.com) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 16D5F86C45; Tue, 27 Mar 2018 22:32:28 +0000 (UTC) (envelope-from david@fromorbit.com) Received: from ppp59-167-129-252.static.internode.on.net (HELO dastard) ([59.167.129.252]) by ipmail06.adl6.internode.on.net with ESMTP; 28 Mar 2018 09:02:02 +1030 Received: from dave by dastard with local (Exim 4.80) (envelope-from ) id 1f0x8L-0004RV-40; Wed, 28 Mar 2018 09:32:01 +1100 Date: Wed, 28 Mar 2018 09:32:01 +1100 From: Dave Chinner To: Eric Sandeen Cc: "Darrick J. Wong" , Conrad Meyer , Cy Schubert , "Luis R. Rodriguez" , Carlos Maiolino , "freebsd-arch@freebsd.org" , xfs Subject: Re: FreeBSD and xfsprogs ? Message-ID: <20180327223201.GR18129@dastard> References: <201803261953.w2QJrYQm028227@slippy.cwsent.com> <20180327160714.GB4818@magnolia> <8396fd92-3a64-a84f-b110-7edc6f0844b0@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8396fd92-3a64-a84f-b110-7edc6f0844b0@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 22:32:30 -0000 On Tue, Mar 27, 2018 at 11:48:29AM -0500, Eric Sandeen wrote: > On 3/27/18 11:07 AM, Darrick J. Wong wrote: > > [cc the xfsprogs maintainer] > > [cc xfs list] > > Yes, thanks. > > > On Mon, Mar 26, 2018 at 12:57:55PM -0700, Conrad Meyer wrote: > >> Yeah, someone broke the build recently via a base toolchain change or > >> a ports framework/compiler change. I don't think that changes > >> anything. > >> > >> On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert wrote: > >>> In message >>> il.com> > >>> , Conrad Meyer writes: > >>>> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote > >>>> : > >>>>> On the Linux xfs development list there is an RFC to remove IRIX, > >>>>> Darwin, and FreeBSD support from xfsprogs, the userspace program used > >>>>> to create/interact with XFS filesystems. Just wanted to poke and check > >>>>> to ensure that FreeBSD is not interested in XFS, if this is incorrect > >>>>> now would be the good time to chime into the list and discussion. > >>>>> > >>>>> [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys. > >>>> redhat.com > >>>> > >>>> Hi Luis, > >>>> > >>>> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port > >>>> incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate > > Yikes. I'm curious, how many people use fusefs-lkl? > > > > Eric will have more to say about this, but is your xfsprogs port still > > on 3.2.4 because ./configure can't find libblkid? > > So: At this point, it seems like if you're still on a 4 year old xfsprogs > release with custom patches due to build problems we've never heard about, > there doesn't seem to be a very strong effort to keep XFS on FreeBSD thriving. > > And, given that you're stuck on 3.2.4, removing support from 4.16.0 won't > change your situation anyway. > > Are people using this? Is anyone dedicated to maintaining it, or is it > just kind of floating along at this point? > > I'd rather not keep non-building freebsd code around just in case; I'd like > to either see someone take ownership to get freebsd properly building upstream, > or just drop it and let FreeBSD keep patching on the side as you've been doing > for a few years anyway. > > Thoughts? We don't support fuse-lkl XFS filesystems on Linux, so I'm not sure that using it on some other platform compels us to maintain a current userspace tool port to those platforms... Cheers, Dave. -- Dave Chinner david@fromorbit.com From owner-freebsd-arch@freebsd.org Wed Mar 28 12:02:14 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABE34F53E4B for ; Wed, 28 Mar 2018 12:02:14 +0000 (UTC) (envelope-from BATV+21eba84c15e1805462fd+5330+infradead.org+hch@bombadil.srs.infradead.org) Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) (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 44280857F9; Wed, 28 Mar 2018 12:02:14 +0000 (UTC) (envelope-from BATV+21eba84c15e1805462fd+5330+infradead.org+hch@bombadil.srs.infradead.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=cezh3DYw97ykeqppP7daPIuSk8iex1Ns2xCEkm9pt58=; b=EtcyJfiFQyDNmRVRQ/iRoewfF BVgXUriMpM5ghQoMkX4NMEDzke29mZLz0AS3cpZVxHEPftlY+MEGmzqc1fwgPFoKUn+aB3sM0e1ZV 9qdDHfcEOeJqWfrKvYi0vqt6qRFxahkVlB9FKSI+mQTeugHR0DgLwNHwIo4MRrnjNR4mtoIqYl2Jf g1BzR64QhSoBu7W3Cso4L52XSg2le77Jh4rqgJ4cdRLDBaqpbzjEmaV7Bl8behuEoB+65XFP2F9aQ BLz8GRDvy4AGeMjomkzgTPvWDC3yYv03LD3i0VdSvOmCpXtsrr8xWKMtos7prmYv0KQmUJtT5bW56 Jqih33elQ==; Received: from hch by bombadil.infradead.org with local (Exim 4.90_1 #2 (Red Hat Linux)) id 1f19mO-0002m4-7i; Wed, 28 Mar 2018 12:02:12 +0000 Date: Wed, 28 Mar 2018 05:02:12 -0700 From: Christoph Hellwig To: Dave Chinner Cc: Eric Sandeen , Carlos Maiolino , Conrad Meyer , "Darrick J. Wong" , xfs , "Luis R. Rodriguez" , "freebsd-arch@freebsd.org" Subject: Re: FreeBSD and xfsprogs ? Message-ID: <20180328120212.GA1838@infradead.org> References: <201803261953.w2QJrYQm028227@slippy.cwsent.com> <20180327160714.GB4818@magnolia> <8396fd92-3a64-a84f-b110-7edc6f0844b0@redhat.com> <20180327223201.GR18129@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180327223201.GR18129@dastard> User-Agent: Mutt/1.9.2 (2017-12-15) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2018 12:02:14 -0000 On Wed, Mar 28, 2018 at 09:32:01AM +1100, Dave Chinner wrote: > We don't support fuse-lkl XFS filesystems on Linux, so I'm not sure > that using it on some other platform compels us to maintain a > current userspace tool port to those platforms... IFF we have someone signing up to maintain the FreeBSD port it seems like a whortwhile exercise. But that is a big IFF. For now I'd say give it a grace period of another release or two to see if someone is going to maintain it properly and if not drop it. From owner-freebsd-arch@freebsd.org Fri Mar 30 20:45:24 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48BF1F678B3 for ; Fri, 30 Mar 2018 20:45:24 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 1D3107EF44 for ; Fri, 30 Mar 2018 20:45:23 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 2266D5A9F16; Fri, 30 Mar 2018 20:45:23 +0000 (UTC) Date: Fri, 30 Mar 2018 20:45:23 +0000 From: Brooks Davis To: freebsd-arch@freebsd.org Cc: Tal Garfinkel , Ali Mashtizadeh Subject: adding pointer annotations to syscalls.master Message-ID: <20180330204523.GO88362@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 20:45:24 -0000 I plan to commit https://reviews.freebsd.org/D14285 early next week. It adds SAL 2.0 annotations to syscalls in syscalls.master and code makesyscalls.sh to strip them out in generated files. This is based on work I started in CheriBSD and use to validate fat pointers at the syscall boundary. Tal Garfinkel reviewed the changes, added annotations to COMPAT* syscalls and is using them in a record and playback framework. One can envision other uses such as a WITNESS-like validator for copyin/out as speculated on in the review. As this time we are only annotating sys/kern/syscalls.master as that is sufficient for userspace work. If kernel use cases materialize, we can annotate other syscalls.master as needed. -- Brooks