Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Dec 2013 17:28:50 +0100
From:      krichy@cflinux.hu
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Re: zfs deadlock
Message-ID:  <9d532168bb6eafa52fecef5e1bb833d7@cflinux.hu>
In-Reply-To: <b36ec81192f2d8fa11db5f2433b71456@cflinux.hu>
References:  <ce83a25c57a1d62abce7a002e8da2949@cflinux.hu> <DF23B67C7A294429B5D47D7186156BEC@multiplay.co.uk> <3b3b22b13d8f1cce460da46c0dd71753@cflinux.hu> <b36ec81192f2d8fa11db5f2433b71456@cflinux.hu>

next in thread | previous in thread | raw e-mail | index | archive | help
Dear Steven,

using the previously provided scripts, the bug still appears. And I got 
the attaches traces when the deadlock occured.

It seems that one process is in zfs_mount(), while the other is in 
zfs_unmount_snap(). Look for the 'zfs' and 'ls' commands.

Hope it helps.

Regards,
2013-12-06 16:59 időpontban krichy@cflinux.hu ezt írta:
> So maybe the force flag is too strict. Under linux the snapshots
> remains mounted after a send.
> 
> 2013-12-06 16:54 időpontban krichy@cflinux.hu ezt írta:
>> Dear Steven,
>> 
>> Of course. But I got further now. You mentioned that is normal that
>> zfs send umounts snapshots. I dont know, but this indeed causes a
>> problem:
>> 
>> It is also reproducible without zfs send.
>> 1. Have a large directory structure (just to make sure find runs long
>> enough), make a snapshot of it.
>> # cd /mnt/pool/set/.zfs/snapshot/snap
>> # find .
>> 
>> meanwhile, on another console
>> # umount -f /mnt/pool/set/.zfs/snapshot/snap
>> 
>> will cause a panic, or such.
>> 
>> So effectively a regular user on a system can cause a crash.
>> 
>> Regards,
>> 
>> 2013-12-06 16:50 időpontban Steven Hartland ezt írta:
>>> kernel compiled, installed and rebooted?
>>> ----- Original Message ----- From: <krichy@cflinux.hu>
>>> To: <smh@FreeBSD.org>
>>> Sent: Friday, December 06, 2013 12:17 PM
>>> Subject: Fwd: Re: zfs deadlock
>>> 
>>> 
>>>> Dear shm,
>>>> 
>>>> I've applied r258294 on top fo releng/9.2, but my test seems to 
>>>> trigger
>>>> the deadlock again.
>>>> 
>>>> Regards,
>>>> 
>>>> -------- Eredeti üzenet --------
>>>> Tárgy: Re: zfs deadlock
>>>> Dátum: 2013-12-06 13:17
>>>> Feladó: krichy@cflinux.hu
>>>> Címzett: freebsd-fs@freebsd.org
>>>> 
>>>> I've applied r258294 on top of releng/9.2, and using the attached
>>>> scripts parallel, the system got into a deadlock again.
>>>> 
>>>> 2013-12-06 11:35 időpontban Steven Hartland ezt írta:
>>>>> Thats correct it unmounts the mounted snapshot.
>>>>> 
>>>>>    Regards
>>>>>    Steve
>>>>> 
>>>>> ----- Original Message ----- From: <krichy@cflinux.hu>
>>>>> To: "Steven Hartland" <killing@multiplay.co.uk>
>>>>> Cc: <freebsd-fs@freebsd.org>
>>>>> Sent: Friday, December 06, 2013 8:50 AM
>>>>> Subject: Re: zfs deadlock
>>>>> 
>>>>> 
>>>>>> What is strange also, when a zfs send finishes, the paralell 
>>>>>> running
>>>>>> find command issues errors:
>>>>>> 
>>>>>> find: ./e/Chuje: No such file or directory
>>>>>> find: ./e/singe: No such file or directory
>>>>>> find: ./e/joree: No such file or directory
>>>>>> find: ./e/fore: No such file or directory
>>>>>> find: fts_read: No such file or directory
>>>>>> Fri Dec  6 09:46:04 CET 2013 2
>>>>>> 
>>>>>> Seems if the filesystem got unmounted meanwhile. But the script is
>>>>>> changed its working directory to the snapshot dir.
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> 2013-12-06 09:03 időpontban krichy@cflinux.hu ezt írta:
>>>>>>> Dear Steven,
>>>>>>> 
>>>>>>> While I was playig with zfs, trying to reproduce the previous 
>>>>>>> bug,
>>>>>>> accidentaly hit another one, which caused a trace I attached.
>>>>>>> 
>>>>>>> The snapshot contains directories in 2 depth, which contain 
>>>>>>> files. It
>>>>>>> was to simulate a vmail setup, with domain/user hierarchy.
>>>>>>> 
>>>>>>> I hope it is useful for someone.
>>>>>>> 
>>>>>>> I used the attached two scripts to reproduce the ZFS bug.
>>>>>>> 
>>>>>>> It definetly crashes the system, in the last 10 minutes it is the 
>>>>>>> 3rd
>>>>>>> time.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> 2013-12-05 20:26 időpontban krichy@cflinux.hu ezt írta:
>>>>>>>> Dear Steven,
>>>>>>>> 
>>>>>>>> Thanks for your reply. Do you know how to reproduce the bug? 
>>>>>>>> Because
>>>>>>>> simply sending a snapshot which is mounted does not 
>>>>>>>> automatically
>>>>>>>> trigger the deadlock. Some special cases needed, or what?
>>>>>>>> How to prove that the patch fixes this?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> 2013-12-05 19:39 időpontban Steven Hartland ezt írta:
>>>>>>>>> Known issue you want:
>>>>>>>>> http://svnweb.freebsd.org/changeset/base/258595
>>>>>>>>> 
>>>>>>>>>    Regards
>>>>>>>>>    Steve
>>>>>>>>> 
>>>>>>>>> ----- Original Message ----- From: "Richard Kojedzinszky"
>>>>>>>>> <krichy@cflinux.hu>
>>>>>>>>> To: <freebsd-fs@freebsd.org>
>>>>>>>>> Sent: Thursday, December 05, 2013 2:56 PM
>>>>>>>>> Subject: zfs deadlock
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Dear fs devs,
>>>>>>>>>> 
>>>>>>>>>> We have a freenas server, which is basicaly a freebsd. I was
>>>>>>>>>> trying to look at snapshots using ls .zfs/snapshot/.
>>>>>>>>>> 
>>>>>>>>>> When I issued it, the system entered a deadlock. An NFSD was
>>>>>>>>>> running, a zfs send was running when I issued the command.
>>>>>>>>>> 
>>>>>>>>>> I attached to command outputs while the system was in a 
>>>>>>>>>> deadlock
>>>>>>>>>> state. I tried to issue
>>>>>>>>>> # reboot -q
>>>>>>>>>> But that did not restart the system. After a while (5-10 
>>>>>>>>>> minutes)
>>>>>>>>>> the system rebooted, I dont know if the deadman caused that.
>>>>>>>>>> 
>>>>>>>>>> Now the system is up and running.
>>>>>>>>>> 
>>>>>>>>>> It is basically a freebsd 9.2 kernel.
>>>>>>>>>> 
>>>>>>>>>> Do someone has a clue?
>>>>>>>>>> 
>>>>>>>>>> Kojedzinszky Richard
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> freebsd-fs@freebsd.org mailing list
>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
>>>>>>>>>> To unsubscribe, send any mail to
>>>>>>>>>> "freebsd-fs-unsubscribe@freebsd.org"
>>>>>>>>> 
>>>>>>>>> ================================================
>>>>>>>>> This e.mail is private and confidential between Multiplay (UK) 
>>>>>>>>> Ltd.
>>>>>>>>> and the person or entity to whom it is addressed. In the event 
>>>>>>>>> of
>>>>>>>>> misdirection, the recipient is prohibited from using, copying,
>>>>>>>>> printing or otherwise disseminating it or any information 
>>>>>>>>> contained
>>>>>>>>> in
>>>>>>>>> it.
>>>>>>>>> 
>>>>>>>>> In the event of misdirection, illegible or incomplete 
>>>>>>>>> transmission
>>>>>>>>> please telephone +44 845 868 1337
>>>>>>>>> or return the E.mail to postmaster@multiplay.co.uk.
>>>>>> 
>>>>> 
>>>>> 
>>>>> ================================================
>>>>> This e.mail is private and confidential between Multiplay (UK) Ltd.
>>>>> and the person or entity to whom it is addressed. In the event of
>>>>> misdirection, the recipient is prohibited from using, copying,
>>>>> printing or otherwise disseminating it or any information contained 
>>>>> in
>>>>> it.
>>>>> 
>>>>> In the event of misdirection, illegible or incomplete transmission
>>>>> please telephone +44 845 868 1337
>>>>> or return the E.mail to postmaster@multiplay.co.uk.
>>> 
>>> 
>>> ================================================
>>> This e.mail is private and confidential between Multiplay (UK) Ltd.
>>> and the person or entity to whom it is addressed. In the event of
>>> misdirection, the recipient is prohibited from using, copying,
>>> printing or otherwise disseminating it or any information contained 
>>> in
>>> it.
>>> 
>>> In the event of misdirection, illegible or incomplete transmission
>>> please telephone +44 845 868 1337
>>> or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-fs@FreeBSD.ORG  Sat Dec  7 13:38:27 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1E6CC36A
 for <freebsd-fs@freebsd.org>; Sat,  7 Dec 2013 13:38:27 +0000 (UTC)
Received: from pi.nmdps.net (pi.nmdps.net [IPv6:2a01:be00:10:201:0:80:0:1])
 by mx1.freebsd.org (Postfix) with ESMTP id 131D11EAC
 for <freebsd-fs@freebsd.org>; Sat,  7 Dec 2013 13:38:25 +0000 (UTC)
Received: from pi.nmdps.net (localhost [127.0.0.1])
 (Authenticated sender: krichy@cflinux.hu)
 by pi.nmdps.net (Postfix) with ESMTPSA id CEAB017AA;
 Sat,  7 Dec 2013 14:38:22 +0100 (CET)
MIME-Version: 1.0
Date: Sat, 07 Dec 2013 14:38:20 +0100
From: krichy@cflinux.hu
To: Steven Hartland <killing@multiplay.co.uk>
Subject: Re: Re: zfs deadlock
In-Reply-To: <9d532168bb6eafa52fecef5e1bb833d7@cflinux.hu>
References: <ce83a25c57a1d62abce7a002e8da2949@cflinux.hu>
 <DF23B67C7A294429B5D47D7186156BEC@multiplay.co.uk>
 <3b3b22b13d8f1cce460da46c0dd71753@cflinux.hu>
 <b36ec81192f2d8fa11db5f2433b71456@cflinux.hu>
 <9d532168bb6eafa52fecef5e1bb833d7@cflinux.hu>
Message-ID: <6063a75f52a64d10aee4845ad07f410c@cflinux.hu>
X-Sender: krichy@cflinux.hu
User-Agent: Roundcube Webmail/0.9.5
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>;
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2013 13:38:27 -0000

Dear Steven,

A crash is very easily reproducible with the attached script, just make 
an empty dataset, make a snapshot of it,
and run the script.
In my virtual machine it crashed in a few seconds, producing the 
attached output.

Regards,
2013-12-06 17:28 időpontban krichy@cflinux.hu ezt írta:
> Dear Steven,
> 
> using the previously provided scripts, the bug still appears. And I
> got the attaches traces when the deadlock occured.
> 
> It seems that one process is in zfs_mount(), while the other is in
> zfs_unmount_snap(). Look for the 'zfs' and 'ls' commands.
> 
> Hope it helps.
> 
> Regards,
> 2013-12-06 16:59 időpontban krichy@cflinux.hu ezt írta:
>> So maybe the force flag is too strict. Under linux the snapshots
>> remains mounted after a send.
>> 
>> 2013-12-06 16:54 időpontban krichy@cflinux.hu ezt írta:
>>> Dear Steven,
>>> 
>>> Of course. But I got further now. You mentioned that is normal that
>>> zfs send umounts snapshots. I dont know, but this indeed causes a
>>> problem:
>>> 
>>> It is also reproducible without zfs send.
>>> 1. Have a large directory structure (just to make sure find runs long
>>> enough), make a snapshot of it.
>>> # cd /mnt/pool/set/.zfs/snapshot/snap
>>> # find .
>>> 
>>> meanwhile, on another console
>>> # umount -f /mnt/pool/set/.zfs/snapshot/snap
>>> 
>>> will cause a panic, or such.
>>> 
>>> So effectively a regular user on a system can cause a crash.
>>> 
>>> Regards,
>>> 
>>> 2013-12-06 16:50 időpontban Steven Hartland ezt írta:
>>>> kernel compiled, installed and rebooted?
>>>> ----- Original Message ----- From: <krichy@cflinux.hu>
>>>> To: <smh@FreeBSD.org>
>>>> Sent: Friday, December 06, 2013 12:17 PM
>>>> Subject: Fwd: Re: zfs deadlock
>>>> 
>>>> 
>>>>> Dear shm,
>>>>> 
>>>>> I've applied r258294 on top fo releng/9.2, but my test seems to 
>>>>> trigger
>>>>> the deadlock again.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> -------- Eredeti üzenet --------
>>>>> Tárgy: Re: zfs deadlock
>>>>> Dátum: 2013-12-06 13:17
>>>>> Feladó: krichy@cflinux.hu
>>>>> Címzett: freebsd-fs@freebsd.org
>>>>> 
>>>>> I've applied r258294 on top of releng/9.2, and using the attached
>>>>> scripts parallel, the system got into a deadlock again.
>>>>> 
>>>>> 2013-12-06 11:35 időpontban Steven Hartland ezt írta:
>>>>>> Thats correct it unmounts the mounted snapshot.
>>>>>> 
>>>>>>    Regards
>>>>>>    Steve
>>>>>> 
>>>>>> ----- Original Message ----- From: <krichy@cflinux.hu>
>>>>>> To: "Steven Hartland" <killing@multiplay.co.uk>
>>>>>> Cc: <freebsd-fs@freebsd.org>
>>>>>> Sent: Friday, December 06, 2013 8:50 AM
>>>>>> Subject: Re: zfs deadlock
>>>>>> 
>>>>>> 
>>>>>>> What is strange also, when a zfs send finishes, the paralell 
>>>>>>> running
>>>>>>> find command issues errors:
>>>>>>> 
>>>>>>> find: ./e/Chuje: No such file or directory
>>>>>>> find: ./e/singe: No such file or directory
>>>>>>> find: ./e/joree: No such file or directory
>>>>>>> find: ./e/fore: No such file or directory
>>>>>>> find: fts_read: No such file or directory
>>>>>>> Fri Dec  6 09:46:04 CET 2013 2
>>>>>>> 
>>>>>>> Seems if the filesystem got unmounted meanwhile. But the script 
>>>>>>> is
>>>>>>> changed its working directory to the snapshot dir.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> 
>>>>>>> 2013-12-06 09:03 időpontban krichy@cflinux.hu ezt írta:
>>>>>>>> Dear Steven,
>>>>>>>> 
>>>>>>>> While I was playig with zfs, trying to reproduce the previous 
>>>>>>>> bug,
>>>>>>>> accidentaly hit another one, which caused a trace I attached.
>>>>>>>> 
>>>>>>>> The snapshot contains directories in 2 depth, which contain 
>>>>>>>> files. It
>>>>>>>> was to simulate a vmail setup, with domain/user hierarchy.
>>>>>>>> 
>>>>>>>> I hope it is useful for someone.
>>>>>>>> 
>>>>>>>> I used the attached two scripts to reproduce the ZFS bug.
>>>>>>>> 
>>>>>>>> It definetly crashes the system, in the last 10 minutes it is 
>>>>>>>> the 3rd
>>>>>>>> time.
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> 2013-12-05 20:26 időpontban krichy@cflinux.hu ezt írta:
>>>>>>>>> Dear Steven,
>>>>>>>>> 
>>>>>>>>> Thanks for your reply. Do you know how to reproduce the bug? 
>>>>>>>>> Because
>>>>>>>>> simply sending a snapshot which is mounted does not 
>>>>>>>>> automatically
>>>>>>>>> trigger the deadlock. Some special cases needed, or what?
>>>>>>>>> How to prove that the patch fixes this?
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> 2013-12-05 19:39 időpontban Steven Hartland ezt írta:
>>>>>>>>>> Known issue you want:
>>>>>>>>>> http://svnweb.freebsd.org/changeset/base/258595
>>>>>>>>>> 
>>>>>>>>>>    Regards
>>>>>>>>>>    Steve
>>>>>>>>>> 
>>>>>>>>>> ----- Original Message ----- From: "Richard Kojedzinszky"
>>>>>>>>>> <krichy@cflinux.hu>
>>>>>>>>>> To: <freebsd-fs@freebsd.org>
>>>>>>>>>> Sent: Thursday, December 05, 2013 2:56 PM
>>>>>>>>>> Subject: zfs deadlock
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> Dear fs devs,
>>>>>>>>>>> 
>>>>>>>>>>> We have a freenas server, which is basicaly a freebsd. I was
>>>>>>>>>>> trying to look at snapshots using ls .zfs/snapshot/.
>>>>>>>>>>> 
>>>>>>>>>>> When I issued it, the system entered a deadlock. An NFSD was
>>>>>>>>>>> running, a zfs send was running when I issued the command.
>>>>>>>>>>> 
>>>>>>>>>>> I attached to command outputs while the system was in a 
>>>>>>>>>>> deadlock
>>>>>>>>>>> state. I tried to issue
>>>>>>>>>>> # reboot -q
>>>>>>>>>>> But that did not restart the system. After a while (5-10 
>>>>>>>>>>> minutes)
>>>>>>>>>>> the system rebooted, I dont know if the deadman caused that.
>>>>>>>>>>> 
>>>>>>>>>>> Now the system is up and running.
>>>>>>>>>>> 
>>>>>>>>>>> It is basically a freebsd 9.2 kernel.
>>>>>>>>>>> 
>>>>>>>>>>> Do someone has a clue?
>>>>>>>>>>> 
>>>>>>>>>>> Kojedzinszky Richard
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> freebsd-fs@freebsd.org mailing list
>>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
>>>>>>>>>>> To unsubscribe, send any mail to
>>>>>>>>>>> "freebsd-fs-unsubscribe@freebsd.org"
>>>>>>>>>> 
>>>>>>>>>> ================================================
>>>>>>>>>> This e.mail is private and confidential between Multiplay (UK) 
>>>>>>>>>> Ltd.
>>>>>>>>>> and the person or entity to whom it is addressed. In the event 
>>>>>>>>>> of
>>>>>>>>>> misdirection, the recipient is prohibited from using, copying,
>>>>>>>>>> printing or otherwise disseminating it or any information 
>>>>>>>>>> contained
>>>>>>>>>> in
>>>>>>>>>> it.
>>>>>>>>>> 
>>>>>>>>>> In the event of misdirection, illegible or incomplete 
>>>>>>>>>> transmission
>>>>>>>>>> please telephone +44 845 868 1337
>>>>>>>>>> or return the E.mail to postmaster@multiplay.co.uk.
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ================================================
>>>>>> This e.mail is private and confidential between Multiplay (UK) 
>>>>>> Ltd.
>>>>>> and the person or entity to whom it is addressed. In the event of
>>>>>> misdirection, the recipient is prohibited from using, copying,
>>>>>> printing or otherwise disseminating it or any information 
>>>>>> contained in
>>>>>> it.
>>>>>> 
>>>>>> In the event of misdirection, illegible or incomplete transmission
>>>>>> please telephone +44 845 868 1337
>>>>>> or return the E.mail to postmaster@multiplay.co.uk.
>>>> 
>>>> 
>>>> ================================================
>>>> This e.mail is private and confidential between Multiplay (UK) Ltd.
>>>> and the person or entity to whom it is addressed. In the event of
>>>> misdirection, the recipient is prohibited from using, copying,
>>>> printing or otherwise disseminating it or any information contained 
>>>> in
>>>> it.
>>>> 
>>>> In the event of misdirection, illegible or incomplete transmission
>>>> please telephone +44 845 868 1337
>>>> or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-fs@FreeBSD.ORG  Sat Dec  7 18:33:31 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F41A3797
 for <freebsd-fs@freebsd.org>; Sat,  7 Dec 2013 18:33:30 +0000 (UTC)
Received: from 01usbos01.prod.adjectivism.org (01usbos01.prod.adjectivism.org
 [208.118.230.84])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C1B511143
 for <freebsd-fs@freebsd.org>; Sat,  7 Dec 2013 18:33:30 +0000 (UTC)
Received: from an authenticated and subsequently anonymized source
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=adjectivism.org;
 s=01usbos01; t=1386440814;
 bh=+rdRS6m/3/+5gCL2XgBGcuvA8oee+mMwWUQyRTh07Yk=;
 h=Date:From:To:Subject:From;
 b=SurLGa0eXShiBHXUOmhw8E0MAkhuWg93a3iYwW0WZ5J4VkEbV3gM10R27StwP7zpM
 1qJzKPnzoAoCxVk6D7zTuRs4tarRfzuewv0llqHxkvw8Tyoh0ZI/PxIWV9ckDK+Czu
 +Acj2JV6q9zthQMlk/WoLmHzg8/Xk0jW9hWLDWtWjl5CO13NNZ1hbTZDAPhzL7McBV
 IMrffy/g0EHqrlB9vWi6SihMB/uGImDi+8fsa4ZGIT8b8SgkBvOI8GB7K8xn+IFqiE
 Gvy+7pz/q+V7aXdsJpYowZ+Wgw1WeoiYcjoNkeFh4mE/RBsKIt287HPjE4nplfkWA7
 5/nKyM6FtNoLxHGVBH74up3O0usqXRphwN98WFVnlS8/HlAOTkmuZ1OuEK49IuqcT8
 SRRhYeB1XYcRbBioFynGZndf4IdQ4vjMhaWn1ES+p7JUk8/E12bGHD6xHcws/w7/w3
 ES0gko/PJ2Dl2bPM3UwnMOT+eJxuC92Kyw+tN0wsUTQwk1rBPk3vdOL6nIV4rJ5ZgI
 B+BRfW5XjM6KL15npmRXgcFXxTyA2ohRAtzitRTCTVXroTfA5h7+KUkSHaRn7sEEdR
 FgMSCnuZ+oQ1+JzNbtoKy1lkchPf9QyRCUM1s4hKm//ZsyVZ7Bs4pYEXB4M8kwI7ax
 /OsRIH664vjwOwdfFqaTWjhA=
Date: Sat, 7 Dec 2013 13:26:49 -0500
From: Erick Turnquist <jhujhiti@adjectivism.org>
To: freebsd-fs@freebsd.org
Subject: Status of ZFS multilabel MAC support
Message-ID: <20131207182646.GA98699@scrubbed.adjectivism.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP"
Content-Disposition: inline
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>;
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2013 18:33:31 -0000


--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi list,

I'm not having much luck searching for this. What is the status of multilabel
MAC support for ZFS? Is it being worked on? Is it even possible?

This is an itch I'd like to try scratching, but this would be my first project
in kernel-land, so I want to make sure this isn't a complete waste of time.

Thanks

--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCAAGBQJSo2hkAAoJEPVscZllOOShTnUQAIgyzJX2gG0AIMRp0+IuC71f
tFtOpfT9iibThKR2Scr58Q+wUpnm2TX7M4FvI8EEPpYJzDnisetBi3wuj1P1iswf
TtQ2x8tyYxuOQxjB09Ob4w1SbDP3lrctsqwgDEEILmh8cB6bdWPCugjMAFBLGfX+
2TNVhoVPNzuXJHJ6VTFEReD2XZNZUVwbANGT6tkx7DAhACSwrVee8GKIp4fw0e2n
4A/YQXKzTSjquvOCG1io1Ks2JDAbk64HtNvxNRKqL0QU7oxmCTSTWCvI9v8T5zDw
X9vcpHc6kxQRQxAYPP8tqIxh4YKvBIUnruBOcrSdzTkJevsGWDlHxgCexljpafoe
KmXnBSbGkSIOwnpL1cVtt3pf9bTQgcVaIcpwwd+m5AXiUfwElXofiBpn9nMSdk0u
qkXviLtvljR7Ul5bFze7w2suwde947BQGYGYq0y5t2EoZZj919nb3DzhQPpDKJRA
CCv+Au9YzGyTV3nvBpAcBEFVtemEZlytOMIxtIeXfmueI6OXtKKN+F+rZCilJszM
ZphNmCggdhyfqhdAnz3R4L4lCAx3JKmkBxtmnN8tjKfg2e85esWy/4NvkK1kuIhL
8ZALTB9hU+4Xg7ig25PXg00jfsOAXS8HyK2iZuOew/qt5Ro5lAJAut6Eo/rXHMbn
oqXi6+d9wCMBrYPz1ce6
=wGz4
-----END PGP SIGNATURE-----

--5mCyUwZo2JvN/JJP--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9d532168bb6eafa52fecef5e1bb833d7>