From owner-freebsd-hackers@freebsd.org Wed Mar 28 19:47:46 2018 Return-Path: Delivered-To: freebsd-hackers@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 48C69F7167A for ; Wed, 28 Mar 2018 19:47:46 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::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 BA5197F9DE for ; Wed, 28 Mar 2018 19:47:45 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id v13so4917259iob.6 for ; Wed, 28 Mar 2018 12:47:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=QaWZrmiIzwE1oXNgm1kgw3jNfFoZLz01IciqR/Xm5nQ=; b=i4tE9+IRHiaSdSNIUcLf5Lfl9xfZEH0tuOsIiL4T+5Y04QgAPa5KsF+/hMV0nkzpO0 1JuOHvMwwc/mNYj4sTNjDXiJ/s46ovI8ZzLu2l4r2sFmKFUkUp0QtXwYmnwAHOP+qsbn qjJKeJVfDPDiXg+yCSZLXIkW83wilIaix3Y+5ABNmovJs6wuVFi9Dc2W+Z/lFX6eUPJS ynbHsk28XdBNnH3Ow/UmR6D9mrDqfJChRv7ZPzgiDnnl5BDWFzGQf/M9urhSWVzXrbqp 0NADFGOQRsp6YKa/IKRXC1nkiqg27I807uerTqFzPMJO/jsXjwyWW6QPX4DKNbaOIKis wdZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QaWZrmiIzwE1oXNgm1kgw3jNfFoZLz01IciqR/Xm5nQ=; b=Y0HQSrMMphbFwUkSGOdWkeyUnUYx4SUzJFFil75eLpros1QLAC2ud8PDWPpurtxjmE 1+4UV5nxhInt6vsOFsa3iADFJN99WLJlsJH50xzoTbPTPk4mzo+HZc9Phgobjrcam1S+ SMwOZQUZdyx8EGh1A2qigNijl8aicZXOs6+fhg6a6irPZzxECnKUaXTE/EoXr6708bGe Ft1J5GgjA/nRdzy/k0GDTt1OndiLs8dqVc4XdyL0wTJKFLSGgvV+g+kuLo5W2D7Foor+ BMQy9oV3deC4kj93JtyRvv80KryogWNuFDdUtTIBYGpXIh5Ltm9uwQCSoSf5QI45JRoZ l0PA== X-Gm-Message-State: AElRT7E0U6Ujuh/Axr6ZpNBBSkpsuU1epANsu6Fb2+SYahhScRMy/xwK 2ZkyCkXLz01+OKixstwKVOS2CPfWQXKB0jLtH/A= X-Google-Smtp-Source: AIpwx48k0rPeF8IzQz9TAKWdYi5to03FzZWPzagmrtmvcyF0XHaLoYlOSLVY/P9sGAJrJ/vduuNzr5OGyeo07xzPVR4= X-Received: by 10.107.146.136 with SMTP id u130mr13343982iod.96.1522266465234; Wed, 28 Mar 2018 12:47:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.192.242.196 with HTTP; Wed, 28 Mar 2018 12:47:44 -0700 (PDT) From: Dieter BSD Date: Wed, 28 Mar 2018 11:47:44 -0800 Message-ID: Subject: Re: GSoC Idea: per-process filesystem namespaces for FreeBSD To: theron.tarigo@gmail.com, freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2018 19:47:46 -0000 Someone typed: > A kind of related task; FreeBSD could benefit from : Fixing and > improving unionfs / nullfs. There are some weird issues with the current > unionfs ... > try to unmount it in the wrong order or thrash a unionfs with > lots of writes on top of a tmpfs and things break Suggestion: fix the unionfs so that it works. 1) Code review. Read the code looking for problems. 2) Hunt down whatever filesystem tests exist. Run them. Do they pass? 3) Are the tests complete? Assuming that they are not: Complete the test suite: A) Functional tests (A filesystem should be able to do x, y, and z. Test that it can. Include various stress tests, and things like a kernel panic, disconnecting a disk's data cable, various types of raid, with/without encryption, various newfs options, labels, ...) B) Code tests (Write test cases to exercise every line of code, and verify that you get the expected result.) 4) Check for open PRs against the filesystem. Can your expanded test suite duplicate the problem? 5) Fix any problems found. 6) Don't forget the filesystem support tools, like newfs, fsck, dump/restore, ... 7) Is the documentation complete, and does it match the code? Remember that the test suite needs documentation too. This should be a good first step towards the Plan 9 functionality.