From owner-freebsd-fs@freebsd.org Sun Jan 7 06:28:12 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id B784EE6CF1B
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 06:28:12 +0000 (UTC)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu
(wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
(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 7CB78793A2
for <freebsd-fs@freebsd.org>; Sun, 7 Jan 2018 06:28:12 +0000 (UTC)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id w076SACn049021
for <freebsd-fs@freebsd.org>; Sun, 7 Jan 2018 01:28:10 -0500 (EST)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id w076SAW0049020;
Sun, 7 Jan 2018 01:28:10 -0500 (EST) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23121.48634.348216.421634@hergotha.csail.mit.edu>
Date: Sun, 7 Jan 2018 01:28:10 -0500
From: Garrett Wollman <wollman@bimajority.org>
To: freebsd-fs@freebsd.org
Subject: Anyone managed to build a static gssd?
X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd10.3)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2
(hergotha.csail.mit.edu [127.0.0.1]); Sun, 07 Jan 2018 01:28:10 -0500 (EST)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,
HEADER_FROM_DIFFERENT_DOMAINS autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
hergotha.csail.mit.edu
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 06:28:12 -0000
I'm interesting in experimenting with GSSAPI security for NFS mounts,
but we run MIT Kerberos, not Heimdal. AIUI, the kernel code has to
have the same data structures as the userland code in gssd, which
implies that gssd has to be built against Heimdal libraries, not MIT.
Has anyone managed to build a gssd executable that is linked
statically against all the Heimdal libraries? I attempted to do this
(in a chroot initialized with stock 11.1) but ended up with something
that still tries to dlopen libgssapi.so.10, which obviously isn't
going to work.
-GAWollman
From owner-freebsd-fs@freebsd.org Sun Jan 7 16:40:38 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20C5FE7545B
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 16:40:38 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 050226D9DF
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 16:40:38 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EE6FC1EFF6
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 16:40:37 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w07GebEj015753
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 16:40:37 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w07GebDX015752
for freebsd-fs@FreeBSD.org; Sun, 7 Jan 2018 16:40:37 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 224974] [fsck] Mounting USB drive at boot time hangs boot
Date: Sun, 07 Jan 2018 16:40:37 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: linimon@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-224974-3630-JqL2XoFkzl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 16:40:38 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224974
Mark Linimon <linimon@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Sun Jan 7 19:13:23 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4160E7BD2D
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 19:13:23 +0000 (UTC)
(envelope-from kaduk@mit.edu)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu
[18.7.68.35])
(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 7F172743E8
for <freebsd-fs@freebsd.org>; Sun, 7 Jan 2018 19:13:22 +0000 (UTC)
(envelope-from kaduk@mit.edu)
X-AuditID: 12074423-487ff7000000527d-2c-5a52701ad3a1
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36])
(using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id
BB.E4.21117.B10725A5; Sun, 7 Jan 2018 14:08:11 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11])
by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w07J86f7011394;
Sun, 7 Jan 2018 14:08:08 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com
[24.107.191.124]) (authenticated bits=56)
(User authenticated as kaduk@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w07J8286003039
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Sun, 7 Jan 2018 14:08:05 -0500
Date: Sun, 7 Jan 2018 13:08:02 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Garrett Wollman <wollman@bimajority.org>
Cc: freebsd-fs@freebsd.org
Subject: Re: Anyone managed to build a static gssd?
Message-ID: <20180107190802.GD25484@kduck.kaduk.org>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <23121.48634.348216.421634@hergotha.csail.mit.edu>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKIsWRmVeSWpSXmKPExsUixG6noitdEBRlsGWvvsWxxz/ZLHZ8usvu
wORxaeptVo8Zn+azBDBFcdmkpOZklqUW6dslcGVMX76YveA9e8WhyS3MDYyb2LoYOTkkBEwk
Nsw6wNTFyMUhJLCYSWL5kw9QzgZGiZnHNzBDOFeYJJ6vmM0E0sIioCKxuGs5M4jNBmQ3dF8G
sjk4RAR0JJYu4wEJMwtISVxe8ocdJCwsYCzx7IoMSJgXaNnqt5PYQWwhATuJ71uesEHEBSVO
znzCAtGqJXHj30smkFZmAWmJ5f84QMKcAvYSm59sYASxRQWUJfb2HWKfwCgwC0n3LCTdsxC6
FzAyr2KUTcmt0s1NzMwpTk3WLU5OzMtLLdI108vNLNFLTSndxAgOURflHYwv+7wPMQpwMCrx
8O5QDowSYk0sK67MPcQoycGkJMor6hwQJcSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmElyUpKEqI
NyWxsiq1KB8mJc3BoiTO62GiHSUkkJ5YkpqdmlqQWgSTleHgUJLgNcgHahQsSk1PrUjLzClB
SDNxcIIM5wEaPiUPZHhxQWJucWY6RP4Uoy7Hs5mvG5iFWPLy81KlxHn/gxQJgBRllObBzQGl
Fons/TWvGMWB3hLm3QhSxQNMS3CTXgEtYQJa8m5fIMiSkkSElFQDo2BY7vmiN2fX/niXPd1g
jynTw6Ldzsq/Ht3f9eJOy2Pdx4uVZ8c+SY5nd3xn/vTYu4mTAi8tEZp5v9OSLXtHKsNVrRyO
1Qmmmw6dF2idVBX/snfr1vI2AcmYRS8Cm14w5oTt+uHKfuxCobO/88zKH18TP/iViFqINmzm
0pNuFnDNNAvrj+Y4qsRSnJFoqMVcVJwIAJssVJYIAwAA
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 19:13:24 -0000
On Sun, Jan 07, 2018 at 01:28:10AM -0500, Garrett Wollman wrote:
> I'm interesting in experimenting with GSSAPI security for NFS mounts,
> but we run MIT Kerberos, not Heimdal. AIUI, the kernel code has to
> have the same data structures as the userland code in gssd, which
> implies that gssd has to be built against Heimdal libraries, not MIT.
I think you might want to test that hypothesis experimentally --
both Heimdal and MIT have gss_export_lucid_sec_context() that
generate the gss_krb5_lucid_context_v1_t data type, which seems
to be defined identically between them. AIUI, this "lucid" (i.e.,
non-opaque) type is what is used for sending the GSS information
into the kernel.
-Ben
> Has anyone managed to build a gssd executable that is linked
> statically against all the Heimdal libraries? I attempted to do this
> (in a chroot initialized with stock 11.1) but ended up with something
> that still tries to dlopen libgssapi.so.10, which obviously isn't
> going to work.
From owner-freebsd-fs@freebsd.org Sun Jan 7 21:03:03 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADE84E5D2D6
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 21:03:03 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com
(mail-by2nam01on0089.outbound.protection.outlook.com [104.47.34.89])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(Client CN "mail.protection.outlook.com",
Issuer "Microsoft IT SSL SHA2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 544DF78E65
for <freebsd-fs@freebsd.org>; Sun, 7 Jan 2018 21:03:02 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) by
YTOPR0101MB2170.CANPRD01.PROD.OUTLOOK.COM (52.132.46.159) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.386.5; Sun, 7 Jan 2018 21:03:01 +0000
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7]) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7%13]) with mapi id 15.20.0386.009; Sun, 7 Jan 2018
21:03:01 +0000
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Benjamin Kaduk <kaduk@mit.edu>, Garrett Wollman <wollman@bimajority.org>
CC: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject: Re: Anyone managed to build a static gssd?
Thread-Topic: Anyone managed to build a static gssd?
Thread-Index: AQHTh+uZCGcGQRWzeUCLjeFj9rv2rKNo48Ow
Date: Sun, 7 Jan 2018 21:03:01 +0000
Message-ID: <YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>,
<20180107190802.GD25484@kduck.kaduk.org>
In-Reply-To: <20180107190802.GD25484@kduck.kaduk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=rmacklem@uoguelph.ca;
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2170;
7:aM5dL2/0n67eDQTKA7nXCoI813c4TEocG9pCbgv8Q57VK7ze5UgJWeOPRu7bz9nkzXVXXGfTPa9FAazYqS84MBMO0JAwULtmRGoRBPg6GkldKBR9rTVEEcNbOj0rB9Ynd76El1YlF9kJrmKZ6LNMylOROMYc7rxr/xVBgIF6g/Jqm5OnmEQBn8ajSr2siVKBHfy6AXZJCm0HVUpH0cvH3+b51moZEATP4V9gC+IipU1FF05H4Oju9xheUNRQygqQ
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 75256016-4c12-4bfd-0417-08d5561209f2
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020);
SRVR:YTOPR0101MB2170;
x-ms-traffictypediagnostic: YTOPR0101MB2170:
x-microsoft-antispam-prvs: <YTOPR0101MB217002F67D34B3F468EAB366DD120@YTOPR0101MB2170.CANPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
RULEID:(6040470)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231023)(944501075)(6041268)(20161123564045)(20161123558120)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011);
SRVR:YTOPR0101MB2170; BCL:0; PCL:0; RULEID:(100000803101)(100110400095);
SRVR:YTOPR0101MB2170;
x-forefront-prvs: 0545EFAC9A
x-forefront-antispam-report: SFV:NSPM;
SFS:(10009020)(979002)(376002)(39380400002)(396003)(39850400004)(346002)(366004)(24454002)(199004)(189003)(2171002)(6246003)(59450400001)(6506007)(97736004)(3280700002)(478600001)(55016002)(2906002)(5250100002)(7696005)(3660700001)(81156014)(81166006)(316002)(9686003)(786003)(8676002)(8936002)(53936002)(2950100002)(110136005)(102836004)(74482002)(99286004)(5660300001)(68736007)(33656002)(4326008)(305945005)(25786009)(229853002)(2900100001)(106356001)(74316002)(105586002)(76176011)(6436002)(86362001)(14454004)(969003)(989001)(999001)(1009001)(1019001);
DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2170;
H:YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords;
A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: uoguelph.ca does not designate
permitted sender hosts)
x-microsoft-antispam-message-info: iNyfaOG3FYTsVXPWsKVLvDemJBcsgKwPMP5fMbxIwKhEgdaZUE0PzhBhf0aLyB3Io0A9/w2sZhcFZxXhY3UCtg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: uoguelph.ca
X-MS-Exchange-CrossTenant-Network-Message-Id: 75256016-4c12-4bfd-0417-08d5561209f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jan 2018 21:03:01.8424 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2170
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 21:03:03 -0000
Benjamin Kaduk wrote:
>On Sun, Jan 07, 2018 at 01:28:10AM -0500, Garrett Wollman wrote:
>> I'm interesting in experimenting with GSSAPI security for NFS mounts,
>> but we run MIT Kerberos, not Heimdal. AIUI, the kernel code has to
>> have the same data structures as the userland code in gssd, which
>> implies that gssd has to be built against Heimdal libraries, not MIT.
>
>I think you might want to test that hypothesis experimentally --
>both Heimdal and MIT have gss_export_lucid_sec_context() that
>generate the gss_krb5_lucid_context_v1_t data type, which seems
>to be defined identically between them. AIUI, this "lucid" (i.e.,
>non-opaque) type is what is used for sending the GSS information
>into the kernel.
I haven't worked with this for a long time, but I vaguely recall that
the kernel RPCSEC_GSS code uses a relatively small subset to the
KGSSAPI upcalls to userland.
If you grep around in sys/rpc/rpcsec_gss you should be able to find
which ones they are (and see if they happen to be the same for Heimdal/MIT)=
.
I think the client side uses more than the server side, but beware that
the server becomes a client for callbacks for NFSv4.
Also, just fyi, RPCSEC_GSS Version 1 (the only one supported by FreeBSD)
uses good old DES and uses the session key created by the Kerberos
libraries via a TGT or keytab entry for this.
--> As such, your TGT encryption choice must result in a 56/64 bit session =
key.
(I never went beyond using DES for TGT encryption, but I suspect MIT
doesn't like that idea;-)
Good luck with it, rick
From owner-freebsd-fs@freebsd.org Sun Jan 7 22:13:20 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1958E61C19
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 22:13:20 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 88E017B7B4
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 22:13:20 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7E27621FCA
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 22:13:20 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w07MDKpj039247
for <freebsd-fs@FreeBSD.org>; Sun, 7 Jan 2018 22:13:20 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w07MDKV9039246
for freebsd-fs@FreeBSD.org; Sun, 7 Jan 2018 22:13:20 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 224974] [fsck] Mounting USB drive at boot time hangs boot
Date: Sun, 07 Jan 2018 22:13:20 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-224974-3630-FPFK0ZriiW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 22:13:20 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224974
Mark Millard <markmi@dsl-only.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markmi@dsl-only.net
--- Comment #1 from Mark Millard <markmi@dsl-only.net> ---
(In reply to pru13allan from comment #0)
Adding USB drives after boot and ending up with
FreeBSD hung up is one part of bugzilla 224330 .
This is tied to head -r326347 in some way, although
-r327347 may have just exposed a problem elsewhere.
The original context was Pine64+ 2GB's.
If you do not mount the USB drive at all via /etc/fstab,
and, do not plug it in until after FreeBSD has booted,
do you still get a hangup when the drive is plugged in?
If not, can you then mount it manually?
Such questions are mostly tied to getting an initial
clue how independent the bugzilla reports are.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Sun Jan 7 22:56:16 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0C29E642C2
for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 7 Jan 2018 22:56:16 +0000 (UTC)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu
(wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
(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 7A5A67D309
for <freebsd-fs@freebsd.org>; Sun, 7 Jan 2018 22:56:16 +0000 (UTC)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id w07MuEsQ060132;
Sun, 7 Jan 2018 17:56:14 -0500 (EST)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id w07MuEF7060131;
Sun, 7 Jan 2018 17:56:14 -0500 (EST) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23122.42381.906072.663073@hergotha.csail.mit.edu>
Date: Sun, 7 Jan 2018 17:56:13 -0500
From: Garrett Wollman <wollman@bimajority.org>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Benjamin Kaduk <kaduk@mit.edu>,
"freebsd-fs\@freebsd.org" <freebsd-fs@freebsd.org>
Subject: Re: Anyone managed to build a static gssd?
In-Reply-To: <YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>
<20180107190802.GD25484@kduck.kaduk.org>
<YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd10.3)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2
(hergotha.csail.mit.edu [127.0.0.1]); Sun, 07 Jan 2018 17:56:14 -0500 (EST)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,
HEADER_FROM_DIFFERENT_DOMAINS autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
hergotha.csail.mit.edu
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jan 2018 22:56:16 -0000
<<On Sun, 7 Jan 2018 21:03:01 +0000, Rick Macklem <rmacklem@uoguelph.ca> said:
> Also, just fyi, RPCSEC_GSS Version 1 (the only one supported by FreeBSD)
> uses good old DES and uses the session key created by the Kerberos
> libraries via a TGT or keytab entry for this.
> --> As such, your TGT encryption choice must result in a 56/64 bit session key.
> (I never went beyond using DES for TGT encryption, but I suspect MIT
> doesn't like that idea;-)
That's good to know, and suggests that maybe I shouldn't bother with
trying this right now. As it happens, I've been working on
benchmarking recently, and the performance of NFSv4.1 is downright
terrible compared to v3, at least with my particular combination of
client and server. Haven't investigated yet where the slowdown is.
What would it take to get AES support?
-GAWollman
From owner-freebsd-fs@freebsd.org Mon Jan 8 09:49:46 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57AAAE60551
for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 8 Jan 2018 09:49:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 3EEFF730EA
for <freebsd-fs@FreeBSD.org>; Mon, 8 Jan 2018 09:49:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3445C28086
for <freebsd-fs@FreeBSD.org>; Mon, 8 Jan 2018 09:49:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w089nkut024196
for <freebsd-fs@FreeBSD.org>; Mon, 8 Jan 2018 09:49:46 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w089nkfi024195
for freebsd-fs@FreeBSD.org; Mon, 8 Jan 2018 09:49:46 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 224974] [fsck] Mounting USB drive at boot time hangs boot
Date: Mon, 08 Jan 2018 09:49:46 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pru13allan@telia.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-224974-3630-i9pvlt8y4a@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-224974-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 09:49:46 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224974
--- Comment #2 from pru13allan@telia.com ---
The problem with the hang is only related to when I want to have the USB-di=
sk
checked at boot (/etc/fstab -> fs_passno =3D 2).
If I set fs_passno =3D 0 it works without any problems.
It gets mounted automatcally with the info from /etc/fstab.
I don't get the filesystem checked before mounting though.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Mon Jan 8 13:52:51 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5138E6DE56
for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 8 Jan 2018 13:52:51 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com
(mail-cys01nam02on0070.outbound.protection.outlook.com [104.47.37.70])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(Client CN "mail.protection.outlook.com",
Issuer "Microsoft IT SSL SHA2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 510F67C499
for <freebsd-fs@freebsd.org>; Mon, 8 Jan 2018 13:52:50 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) by
YTOPR0101MB2169.CANPRD01.PROD.OUTLOOK.COM (52.132.46.151) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.386.5; Mon, 8 Jan 2018 13:52:48 +0000
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7]) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7%13]) with mapi id 15.20.0386.009; Mon, 8 Jan 2018
13:52:48 +0000
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Garrett Wollman <wollman@bimajority.org>
CC: Benjamin Kaduk <kaduk@mit.edu>, "freebsd-fs@freebsd.org"
<freebsd-fs@freebsd.org>
Subject: Re: Anyone managed to build a static gssd?
Thread-Topic: Anyone managed to build a static gssd?
Thread-Index: AQHTh+uZCGcGQRWzeUCLjeFj9rv2rKNo48OwgAAh1ICAAPam0w==
Date: Mon, 8 Jan 2018 13:52:48 +0000
Message-ID: <YTOPR0101MB2172DBE2F99D65C3E7D8FCD3DD130@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>
<20180107190802.GD25484@kduck.kaduk.org>
<YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>,
<23122.42381.906072.663073@hergotha.csail.mit.edu>
In-Reply-To: <23122.42381.906072.663073@hergotha.csail.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=rmacklem@uoguelph.ca;
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2169;
7:rSV2cVflj+a1Fxq4357cp1/sX9wGGK2IwtIcRxB65wXWOJv+lh4yj4+knSCjO7hyVOKutqQ2QslI48H7TKX8cqYXez3g5pntEXL62tSi1avRCM/2Nhv3wlQ2Z/cFC8+dBF5Gv/tDSiwFqx8KBvW/+JzQ0ylkna87whJoXbGqfv6ejaU0Rtnp2XTPNOeHLbPCxZ0OPqOruwJ3ehUwR15HnUUgnZj1pJ7Fx8OUHPWbctDf1kqMCsqG+hXsgKGGwI1r
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: f0176608-ff27-4dbb-2e3e-08d5569f1aa6
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020);
SRVR:YTOPR0101MB2169;
x-ms-traffictypediagnostic: YTOPR0101MB2169:
x-microsoft-antispam-prvs: <YTOPR0101MB2169A25CAB6636680334E552DD130@YTOPR0101MB2169.CANPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
RULEID:(6040470)(2401047)(8121501046)(5005006)(3231023)(944501075)(3002001)(10201501046)(93006095)(93001095)(6041268)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(6072148)(201708071742011);
SRVR:YTOPR0101MB2169; BCL:0; PCL:0; RULEID:(100000803101)(100110400095);
SRVR:YTOPR0101MB2169;
x-forefront-prvs: 054642504A
x-forefront-antispam-report: SFV:NSPM;
SFS:(10009020)(346002)(376002)(396003)(39380400002)(39860400002)(366004)(24454002)(189003)(199004)(106356001)(105586002)(4326008)(93886005)(68736007)(55016002)(102836004)(316002)(786003)(25786009)(81166006)(5250100002)(2906002)(9686003)(97736004)(3280700002)(54906003)(3660700001)(305945005)(2900100001)(53936002)(6246003)(74482002)(33656002)(478600001)(74316002)(8676002)(7696005)(14454004)(6436002)(81156014)(86362001)(5660300001)(6916009)(2950100002)(76176011)(6506007)(8936002)(99286004)(229853002);
DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2169;
H:YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords;
MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: uoguelph.ca does not designate
permitted sender hosts)
x-microsoft-antispam-message-info: fDkp9f69yJ4Bxs81YbJ0cjB8mgWoAx4mIW/VyclwR0QJy17C1exREF7KYDCZXUHC/A1BU8zjQIx7gJaHEHix2g==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: uoguelph.ca
X-MS-Exchange-CrossTenant-Network-Message-Id: f0176608-ff27-4dbb-2e3e-08d5569f1aa6
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jan 2018 13:52:48.9211 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2169
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 13:52:51 -0000
Garrett Wollman wrote:
[good stuff snipped]
> What would it take to get AES support?
Good question. Unfortunately I don't know the answer.
(I shouldn't have blamed RPCSEC_GSS Version 1, since it isn't this spec
that is the problem, from what I know.)
1 - The kernel RPCSEC_GSS code does upcalls to the userland library for
the initialization phase (ie. GSS_Init() calls using the tokens).
--> So question #1 becomes "Does the Heimdal GSSAPI library know how
to do better checksum/encryption than was specified in the origina=
l
GSSAPI RFC?".
2 - The kernel RPCSEC_GSS code uses the session key from the GSS_Init()
handling of the tokens to do checksums/encryption. (Basically in kernel
versions of GSS_GetMIC(), GSS_VerifyMIC(), GSS_Wrap, GSS_Unwrap().)
If the answer to #1 is yes, then it might not be that much work?
3 - I have never seen any definition of what the QOPs are for better encryp=
tion
types in the GSSAPI. (Numbers that define the better checksum/encryption
algorithms.)
--> I have no idea if the NFS implementors have done anything about this.
I haven't seen discussions of it on nfsv4@ietf.org, but it may have=
happened.
Without this, you'd end up with a FreeBSD specific hack that didn't
interoperate with other NFS implementation.s
In practice these days "If Linux supports it, others will too.".
If you can answer all of the above, then you probably know the answer.
It could range from some fairly minor changes to the kernel RPCSEC_GSS
code to a whole lot of work.
Maybe some Kerberos conversant folk can shed light on this? rick=
From owner-freebsd-fs@freebsd.org Mon Jan 8 14:31:44 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87808E6FC81
for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 8 Jan 2018 14:31:44 +0000 (UTC)
(envelope-from borjam@sarenet.es)
Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com
[195.16.151.151])
(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 D2F637DBF3
for <freebsd-fs@freebsd.org>; Mon, 8 Jan 2018 14:31:42 +0000 (UTC)
(envelope-from borjam@sarenet.es)
Received: from [172.16.8.47] (unknown [192.148.167.11])
by proxypop01.sare.net (Postfix) with ESMTPA id 4277A9DD2F4
for <freebsd-fs@freebsd.org>; Mon, 8 Jan 2018 15:25:15 +0100 (CET)
From: Borja Marcos <borjam@sarenet.es>
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Subject: Academic exercise: trying to recover a corrupted pool
Message-Id: <F6B823C4-313E-4AF2-B1F6-6AFE8E17458B@sarenet.es>
Date: Mon, 8 Jan 2018 15:25:14 +0100
To: freebsd-fs@freebsd.org
X-Mailer: Apple Mail (2.3445.5.20)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 14:31:44 -0000
Hi,
ONLY AS AN ACADEMIC EXERCISE, WARNING :)
I have a broken ZFS pool and I=E2=80=99m wondering wether it should be =
readable. The pool was made with four
apparently troublesome OCZ SSD drives pulled from other systems. They =
are connected to a LSI2008 adapter.
The pool was created as a raidz2, so it=E2=80=99s supposed to survive =
the loss of two drives. It has lost two of them
and I am unable to import it.
I have lost no useful data, I was using it just for testing. Now it has =
become an interesting study subject though :)
Any ideas? I have tried to recover even doing the =E2=80=9Cradical =
thing=E2=80=9D (zdb -Z -AAA -e -p /dev poolname). No success.
Again, I am just curious.
Thanks!
Borja.
=20
Now, the data
If I try to recover it using zdb -e -X I get this:
# zdb -e -X cashopul
Configuration for import:
vdev_children: 1
version: 5000
pool_guid: 585029935900186516
name: 'cashopul'
state: 0
hostid: 605799378
hostname: ''
vdev_tree:
type: 'root'
id: 0
guid: 585029935900186516
children[0]:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
whole_disk: 1
DTL: 10390
create_txg: 4
path: '/dev/da2'
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
whole_disk: 1
DTL: 10389
create_txg: 4
path: '/dev/da3'
zdb: can't open 'cashopul': Device not configured
ZFS_DBGMSG(zdb):
Reading the individual labels of the surviving drives,
# zdb -l /dev/da2
------------------------------------
LABEL 0
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4780356075228908448
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 1
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4780356075228908448
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 2
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4780356075228908448
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 3
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4780356075228908448
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
# zdb -l /dev/da3
------------------------------------
LABEL 0
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4182482849823292334
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 1
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4182482849823292334
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 2
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4182482849823292334
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
------------------------------------
LABEL 3
------------------------------------
version: 5000
name: 'cashopul'
state: 0
txg: 26855087
pool_guid: 585029935900186516
hostid: 605799378
hostname: ''
top_guid: 17478362601057626606
guid: 4182482849823292334
vdev_children: 1
vdev_tree:
type: 'raidz'
id: 0
guid: 17478362601057626606
nparity: 2
metaslab_array: 40
metaslab_shift: 34
ashift: 12
asize: 2048421527552
is_log: 0
create_txg: 4
children[0]:
type: 'disk'
id: 0
guid: 5865132871942380009
path: '/dev/da2'
whole_disk: 1
not_present: 1
DTL: 10392
create_txg: 4
children[1]:
type: 'disk'
id: 1
guid: 17151294206067279763
path: '/dev/da2'
whole_disk: 1
DTL: 10391
create_txg: 4
children[2]:
type: 'disk'
id: 2
guid: 4780356075228908448
path: '/dev/da3'
whole_disk: 1
DTL: 10390
create_txg: 4
children[3]:
type: 'disk'
id: 3
guid: 4182482849823292334
path: '/dev/da4'
whole_disk: 1
DTL: 10389
create_txg: 4
features_for_read:
com.delphix:hole_birth
com.delphix:embedded_data
From owner-freebsd-fs@freebsd.org Mon Jan 8 16:24:41 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44C07E75A88
for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 8 Jan 2018 16:24:41 +0000 (UTC)
(envelope-from crest@rlwinm.de)
Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5])
(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 0E1F9836C0
for <freebsd-fs@freebsd.org>; Mon, 8 Jan 2018 16:24:40 +0000 (UTC)
(envelope-from crest@rlwinm.de)
Received: from crest.bultmann.eu (unknown
[IPv6:2a00:c380:c0d5:1:995a:4b9c:291a:4ea1])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mail.rlwinm.de (Postfix) with ESMTPSA id EB1E0BD5B
for <freebsd-fs@freebsd.org>; Mon, 8 Jan 2018 16:24:37 +0000 (UTC)
Subject: Re: kqueue/kevent - watching an entire filesystem?
To: freebsd-fs@freebsd.org
References: <9795fa64-b2dc-50c3-c7e0-8422e0388c15@aldan.algebra.com>
<CAG6CVpVXdvVAC7up9QRkM-W_NX8KE=+fj8QNhPyOoAE2oxvo=w@mail.gmail.com>
From: Jan Bramkamp <crest@rlwinm.de>
Message-ID: <73b64e9c-1f33-7522-4362-087bbc7e241e@rlwinm.de>
Date: Mon, 8 Jan 2018 17:24:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAG6CVpVXdvVAC7up9QRkM-W_NX8KE=+fj8QNhPyOoAE2oxvo=w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 16:24:41 -0000
On 25.12.17 18:41, Conrad Meyer wrote:
> If you want to watch whole system activity (and not just a single
> filesystem), that sounds like audit. Or its crappy cousin,
> filemon(4). Of course, neither of these options has a kevent-style
> interface, and filemon(4) in particular may miss relevant events.
>
> I'm afraid there is nothing better than recursively opening
> subdirectories to monitor a tree (even a whole filesystem) with
> kqueue/kevent.
Filemon would be useful in a lot of cases, but it uses newlines as
record separators without quoting them in the detected paths. See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224015 for more
details. Few source files contain new files so it won't break building
sane software in bmake meta mode, but it makes filemon unusable as a
poor mans inotify replacement for (untrusted) user data.
From owner-freebsd-fs@freebsd.org Tue Jan 9 00:45:04 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id A896DE6FA9F
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 00:45:04 +0000 (UTC)
(envelope-from kaduk@mit.edu)
Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu
[18.7.68.36])
(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 41BC77DF0B
for <freebsd-fs@freebsd.org>; Tue, 9 Jan 2018 00:45:03 +0000 (UTC)
(envelope-from kaduk@mit.edu)
X-AuditID: 12074424-679ff70000005c98-7a-5a5410810d3c
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])
(using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id
90.73.23704.180145A5; Mon, 8 Jan 2018 19:44:50 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11])
by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id w090imNS025220;
Mon, 8 Jan 2018 19:44:48 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com
[24.107.191.124]) (authenticated bits=56)
(User authenticated as kaduk@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w090ihxc025100
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 8 Jan 2018 19:44:46 -0500
Date: Mon, 8 Jan 2018 18:44:43 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Garrett Wollman <wollman@bimajority.org>,
"freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject: Re: Anyone managed to build a static gssd?
Message-ID: <20180109004443.GK25484@kduck.kaduk.org>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>
<20180107190802.GD25484@kduck.kaduk.org>
<YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
<23122.42381.906072.663073@hergotha.csail.mit.edu>
<YTOPR0101MB2172DBE2F99D65C3E7D8FCD3DD130@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YTOPR0101MB2172DBE2F99D65C3E7D8FCD3DD130@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnleLIzCtJLcpLzFFi42IR4hTV1m0SCIkyeDaZ2+LY459sFg+XXWOy
2PHpLrsDs8elqbdZPWZ8ms/i8XvzXqYA5igum5TUnMyy1CJ9uwSujG1bv7EVPBKueH/zAWsD
42b+LkZODgkBE4nLHz4xdTFycQgJLGaSmPJwFjOEs4FRouHcdDYI5wqTxJVnfxlBWlgEVCRW
T97EBmKzAdkN3ZeZQWwRAXWJzav7wWxmgQyJS7cOAdVwcAgLGEs8uyIDEuYF2nZjRR87xMwz
TBK/br5mhUgISpyc+YQFoldL4sa/l0wgvcwC0hLL/3GAhDkFEiUO/Z4MViIqoCyxt+8Q+wRG
gVlIumch6Z6F0L2AkXkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrrlebmaJXmpK6SZGUOiyu6js
YOzu8T7EKMDBqMTDW9AeHCXEmlhWXJl7iFGSg0lJlFfUOSBKiC8pP6UyI7E4I76oNCe1+BCj
BAezkgiv73ygct6UxMqq1KJ8mJQ0B4uSOK+HiXaUkEB6YklqdmpqQWoRTFaGg0NJgvcsf0iU
kGBRanpqRVpmTglCmomDE2Q4D9Dw+SA1vMUFibnFmekQ+VOMxhxzzl/+w8TxbObrBmYhlrz8
vFQpcd5zfEClAiClGaV5cNNA6Ucie3/NK0ZxoOeEeTVABvIAUxfcvFdAq5iAVr3bFwiyqiQR
ISXVwCgVNbO82fHIn886mQ2TNsacmnDDu/i5ardn0aZnX7767e3Jn9q2LTT/78OCYysXmpvf
8nxoafRa6qKti9vOiJbW14mKc5ZsX3btkXDqkquRVr9dFh3qFvxa+YVLY0I+r3rog4WP5qqL
Lgh7eXr57j121bG24uGVonNybISNw8/lCO/1CRFfdUmJpTgj0VCLuag4EQA0iiC+GgMAAA==
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 00:45:04 -0000
On Mon, Jan 08, 2018 at 01:52:48PM +0000, Rick Macklem wrote:
> Garrett Wollman wrote:
> [good stuff snipped]
> > What would it take to get AES support?
> Good question. Unfortunately I don't know the answer.
> (I shouldn't have blamed RPCSEC_GSS Version 1, since it isn't this spec
> that is the problem, from what I know.)
>
> 1 - The kernel RPCSEC_GSS code does upcalls to the userland library for
> the initialization phase (ie. GSS_Init() calls using the tokens).
> --> So question #1 becomes "Does the Heimdal GSSAPI library know how
> to do better checksum/encryption than was specified in the original
> GSSAPI RFC?".
Heavens; yes! Per RFC 6649, you shouldn't be using single-DES for
anything you actually care about the confidentiality of.
> 2 - The kernel RPCSEC_GSS code uses the session key from the GSS_Init()
> handling of the tokens to do checksums/encryption. (Basically in kernel
> versions of GSS_GetMIC(), GSS_VerifyMIC(), GSS_Wrap, GSS_Unwrap().)
> If the answer to #1 is yes, then it might not be that much work?
sys/kgssapi/krb5 has bits for aes/RC4/etc.
> 3 - I have never seen any definition of what the QOPs are for better encryption
> types in the GSSAPI. (Numbers that define the better checksum/encryption
> algorithms.)
> --> I have no idea if the NFS implementors have done anything about this.
> I haven't seen discussions of it on nfsv4@ietf.org, but it may have happened.
> Without this, you'd end up with a FreeBSD specific hack that didn't
> interoperate with other NFS implementation.s
> In practice these days "If Linux supports it, others will too.".
The GSS QOP should be considered deprecated as of GSS-API version2,
and GSS_C_QOP_DEFAULT is the only thing I ever see used.
The session key output by the GSS security context negotiation will
be of an encryption type supported by both peers, so there "ought
not" be any code changes needed to the GSS-API consumer code.
> If you can answer all of the above, then you probably know the answer.
> It could range from some fairly minor changes to the kernel RPCSEC_GSS
> code to a whole lot of work.
>
> Maybe some Kerberos conversant folk can shed light on this?
The above all adds up to a situation where the last time I tried to
look at this (a few years ago), I had managed to convince myself
that non-single-DES should "just work" as-is. But I didn't actually
spin up a test server to verify that.
-Ben
From owner-freebsd-fs@freebsd.org Tue Jan 9 09:49:18 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFCA3E7271A
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 09:49:18 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id C5EA87401C
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:49:18 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B936B4FE8
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:49:18 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w099nILR088810
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:49:18 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w099nId1088809
for freebsd-fs@FreeBSD.org; Tue, 9 Jan 2018 09:49:18 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 223803] zio_done() panic on system with cache devices
Date: Tue, 09 Jan 2018 09:49:18 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-223803-3630-p0PCPRnvaG@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 09:49:19 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803
--- Comment #6 from Andriy Gapon <avg@FreeBSD.org> ---
Has anyone tested this yet?
Please remember that your feedback is very important.
Without it the chances of the fix being committed are much lower.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Tue Jan 9 09:54:29 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EEF7E72C5A
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 09:54:29 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 760CE74449
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:54:29 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 68BBD5140
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:54:29 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w099sTK9003834
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:54:29 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w099sTlE003833
for freebsd-fs@FreeBSD.org; Tue, 9 Jan 2018 09:54:29 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 210409] zfs: panic during boot
Date: Tue, 09 Jan 2018 09:54:29 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-210409-3630-xBrX4nt4sf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210409-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-210409-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 09:54:29 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210409
--- Comment #9 from Andriy Gapon <avg@FreeBSD.org> ---
I am seeing this problem from time to time (very rarely) in my test VMs.
I suspect that under some conditions there is a race between a thread doing=
the
pool import and a txg sync thread spawned by it. If spa_minref is recorded
when the sync thread is accessing the pool, then the value would be higher =
than
it should be.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Tue Jan 9 09:57:21 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5D89E72EF9
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 09:57:21 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id AB3D374619
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:57:21 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A07BD5147
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:57:21 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w099vLCD007920
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 09:57:21 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w099vLOL007919
for freebsd-fs@FreeBSD.org; Tue, 9 Jan 2018 09:57:21 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 181966] [zfs] [panic] Kernel panic in ZFS I/O: solaris assert:
BP_EQUAL(bp, &zio->io_bp_orig); zio.c line 2955 [9.2/amd64]
Date: Tue, 09 Jan 2018 09:57:21 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Overcome By Events
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-181966-3630-oGDm2zu2U2@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-181966-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-181966-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 09:57:21 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D181966
Andriy Gapon <avg@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|In Progress |Closed
Resolution|--- |Overcome By Events
--- Comment #3 from Andriy Gapon <avg@FreeBSD.org> ---
Not sure why this bug is marked as in progress.
The code in supported version of FreeBSD is quite different from 9.x era.
Please re-open if the problem happens again.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Tue Jan 9 13:36:00 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C61EE7DAD3
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 13:36:00 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 83F207CBAB
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 13:36:00 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7861B6FE1
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 13:36:00 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w09Da0Ta023084
for <freebsd-fs@FreeBSD.org>; Tue, 9 Jan 2018 13:36:00 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w09Da0xK023081
for freebsd-fs@FreeBSD.org; Tue, 9 Jan 2018 13:36:00 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 223803] zio_done() panic on system with cache devices
Date: Tue, 09 Jan 2018 13:36:00 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: shiva.bhanujan@quorum.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-223803-3630-iIMKXllY0M@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 13:36:00 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803
--- Comment #7 from Shiva <shiva.bhanujan@quorum.com> ---
(In reply to Andriy Gapon from comment #6)
We've been testing the modified fix for 10.3 (the diffs that I posted in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803#c5) for a few we=
eks
now, and we haven't had a single crash since. The systems are fairly loade=
d,
w/ quite a few 'zfs receive' being done.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Tue Jan 9 14:52:54 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCF16E9AE51
for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 9 Jan 2018 14:52:54 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com
(mail-by2nam03on0059.outbound.protection.outlook.com [104.47.42.59])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(Client CN "mail.protection.outlook.com",
Issuer "Microsoft IT SSL SHA2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 71E007FCD5
for <freebsd-fs@freebsd.org>; Tue, 9 Jan 2018 14:52:53 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) by
YTOPR0101MB2170.CANPRD01.PROD.OUTLOOK.COM (52.132.46.159) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.386.5; Tue, 9 Jan 2018 14:52:53 +0000
Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7]) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM
([fe80::6d7a:1bb0:91b4:f3f7%13]) with mapi id 15.20.0386.009; Tue, 9 Jan 2018
14:52:52 +0000
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: Garrett Wollman <wollman@bimajority.org>, "freebsd-fs@freebsd.org"
<freebsd-fs@freebsd.org>
Subject: Re: Anyone managed to build a static gssd?
Thread-Topic: Anyone managed to build a static gssd?
Thread-Index: AQHTh+uZCGcGQRWzeUCLjeFj9rv2rKNo48OwgAAh1ICAAPam04AAuf+AgADptAs=
Date: Tue, 9 Jan 2018 14:52:52 +0000
Message-ID: <YTOPR0101MB21726A56FED9981295DFD4F9DD100@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
References: <23121.48634.348216.421634@hergotha.csail.mit.edu>
<20180107190802.GD25484@kduck.kaduk.org>
<YTOPR0101MB21723D8BB5B9AFFCD051F512DD120@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
<23122.42381.906072.663073@hergotha.csail.mit.edu>
<YTOPR0101MB2172DBE2F99D65C3E7D8FCD3DD130@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>,
<20180109004443.GK25484@kduck.kaduk.org>
In-Reply-To: <20180109004443.GK25484@kduck.kaduk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=rmacklem@uoguelph.ca;
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2170;
7:TUrjSidctuI0/ChO9CaW8ZgMlJDMhBkMrb93l7Cz5oUdPUDC4PeZUUr1WlUlXM6dOKgWR5juLseRJ23BpVVO41a+zpKjVDVyiEtrIma8scp/+UxpQ/66g42H1An9ivj0YCOPbW6eD3FfB1GTz9AEuP9GeVDIWv9v2UX3iCbu7QWu0BSKdUKdHlhWgTY26ZatDi/f8hfqJ6lKAyc3a2z91d06XDeoFdeMlwt18hN9R5X33dhAFqqceQHTmBm89yKU
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 70028241-5c19-435e-c3d2-08d55770a92f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020);
SRVR:YTOPR0101MB2170;
x-ms-traffictypediagnostic: YTOPR0101MB2170:
x-microsoft-antispam-prvs: <YTOPR0101MB2170A346D8D7CB75367A69E3DD100@YTOPR0101MB2170.CANPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
RULEID:(6040470)(2401047)(8121501046)(5005006)(3231023)(944501075)(3002001)(10201501046)(93006095)(93001095)(6041268)(20161123562045)(20161123564045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(6072148)(201708071742011);
SRVR:YTOPR0101MB2170; BCL:0; PCL:0; RULEID:(100000803101)(100110400095);
SRVR:YTOPR0101MB2170;
x-forefront-prvs: 0547116B72
x-forefront-antispam-report: SFV:NSPM;
SFS:(10009020)(376002)(366004)(396003)(39380400002)(346002)(39860400002)(189003)(199004)(24454002)(305945005)(14454004)(229853002)(105586002)(33656002)(54906003)(25786009)(68736007)(4326008)(2900100001)(106356001)(5660300001)(99286004)(74316002)(76176011)(86362001)(6436002)(2906002)(478600001)(97736004)(7696005)(55016002)(3280700002)(6246003)(81166006)(93886005)(6506007)(2171002)(59450400001)(5250100002)(8936002)(6916009)(102836004)(786003)(81156014)(3660700001)(2950100002)(74482002)(9686003)(8676002)(53936002)(316002);
DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2170;
H:YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords;
MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: uoguelph.ca does not designate
permitted sender hosts)
x-microsoft-antispam-message-info: u/kBIqSrpGtu/4leOIJxpljb0oyvXdvFBwMj8otEi3WID9Rju7PDrGHcgvCSc/58a9+9K4zE0MzzGsrkBnC9Qg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: uoguelph.ca
X-MS-Exchange-CrossTenant-Network-Message-Id: 70028241-5c19-435e-c3d2-08d55770a92f
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2018 14:52:52.8445 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2170
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 14:52:54 -0000
Benjamin Kaduk wrote:
>On Mon, Jan 08, 2018 at 01:52:48PM +0000, Rick Macklem wrote:
>> Garrett Wollman wrote:
>> [good stuff snipped]
>> > What would it take to get AES support?
>> Good question. Unfortunately I don't know the answer.
>> (I shouldn't have blamed RPCSEC_GSS Version 1, since it isn't this spec
>> that is the problem, from what I know.)
>>
>> 1 - The kernel RPCSEC_GSS code does upcalls to the userland library for
>> the initialization phase (ie. GSS_Init() calls using the tokens).
>> --> So question #1 becomes "Does the Heimdal GSSAPI library know how
>> to do better checksum/encryption than was specified in the orig=
inal
>> GSSAPI RFC?".
>
>Heavens; yes! Per RFC 6649, you shouldn't be using single-DES for
>anything you actually care about the confidentiality of.
I wasn't asking if they should. I just didn't know if they had been updated
to do so.
Anyhow, I took a quick look at the code and it does appear that everything
is there to make newer encryption types up to aes256 work, assuming the
userland library does its part.
(In sys/kgssapi/krb5 there is krb5_mech.c and in it there are krb5_encrypt_=
new()
as well as krb5_encrypt_old(). The one that ends in _new() appears to do t=
he
newer stuff like aes.)
>> 2 - The kernel RPCSEC_GSS code uses the session key from the GSS_Init()
>> handling of the tokens to do checksums/encryption. (Basically in kerne=
l
>> versions of GSS_GetMIC(), GSS_VerifyMIC(), GSS_Wrap, GSS_Unwrap().)
>> If the answer to #1 is yes, then it might not be that much work?
>
>sys/kgssapi/krb5 has bits for aes/RC4/etc.
Yep, as I noted above. The RPCSEC_GSS code used the gss context which
hopefully gets set to the right thing.
>> 3 - I have never seen any definition of what the QOPs are for better enc=
ryption
>> types in the GSSAPI. (Numbers that define the better checksum/encrypti=
on
>> algorithms.)
>> --> I have no idea if the NFS implementors have done anything about th=
is.
>> I haven't seen discussions of it on nfsv4@ietf.org, but it may h=
ave happened.
>> Without this, you'd end up with a FreeBSD specific hack that did=
n't
>> interoperate with other NFS implementation.s
>> In practice these days "If Linux supports it, others will too.".
>
>The GSS QOP should be considered deprecated as of GSS-API version2,
>and GSS_C_QOP_DEFAULT is the only thing I ever see used.
>The session key output by the GSS security context negotiation will
>be of an encryption type supported by both peers, so there "ought
>not" be any code changes needed to the GSS-API consumer code.
I looked and the RPCSEC_GSS kernel code only uses GSS_C_QOP_DEFAULT.
>> If you can answer all of the above, then you probably know the answer.
>> It could range from some fairly minor changes to the kernel RPCSEC_GSS
>> code to a whole lot of work.
>>
>> Maybe some Kerberos conversant folk can shed light on this?
>
>The above all adds up to a situation where the last time I tried to
>look at this (a few years ago), I had managed to convince myself
>that non-single-DES should "just work" as-is. But I didn't actually
>spin up a test server to verify that.
Yep. I would agree with this. I could only get DES to work, but that was
quite a few years ago and I was just testing the NFS side, so I didn't care
if newer encryption worked.
Hopefully someone will test and find out if it works, rick
ps: And sorry for misleading you by saying only 64bit keys worked. That
statement assumed that the krb5_encrypt_old() functions were the
only ones available.
From owner-freebsd-fs@freebsd.org Wed Jan 10 09:26:46 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6B3EE7489B
for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 10 Jan 2018 09:26:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 9D16F6A9A9
for <freebsd-fs@FreeBSD.org>; Wed, 10 Jan 2018 09:26:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8F33919701
for <freebsd-fs@FreeBSD.org>; Wed, 10 Jan 2018 09:26:46 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0A9Qk7m010800
for <freebsd-fs@FreeBSD.org>; Wed, 10 Jan 2018 09:26:46 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0A9Qkhj010799
for freebsd-fs@FreeBSD.org; Wed, 10 Jan 2018 09:26:46 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 223803] zio_done() panic on system with cache devices
Date: Wed, 10 Jan 2018 09:26:46 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: demis@yandex.ru
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-223803-3630-m6cLPQ8IOd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-223803-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 09:26:46 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803
Demis <demis@yandex.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |demis@yandex.ru
--- Comment #8 from Demis <demis@yandex.ru> ---
(In reply to Andriy Gapon from comment #6)
How apply this patch on FreeBSD 11.1 amd64?
uname -imrs
FreeBSD 11.1-RELEASE-p6 amd64 GENERIC
Errors:
Hunk #7 failed at 2207.
Hunk #10 failed at 2545.
cat sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c.rej
@@ -2193,7 +2207,7 @@
ASSERT(BP_IS_GANG(bp) && zio->io_gang_leader =3D=3D zio);
ASSERT(zio->io_child_type > ZIO_CHILD_GANG);
- if (zio->io_child_error[ZIO_CHILD_GANG] =3D=3D 0)
+ if (zio->io_child_error[zio_child(ZIO_CHILD_GANG)] =3D=3D 0)
zio_gang_tree_issue(zio, zio->io_gang_tree, bp, zio->io_abd,
0);
else
@@ -2531,7 +2545,7 @@
if (dde->dde_repair_abd !=3D NULL) {
abd_copy(zio->io_abd, dde->dde_repair_abd,
zio->io_size);
- zio->io_child_error[ZIO_CHILD_DDT] =3D 0;
+ zio->io_child_error[zio_child(ZIO_CHILD_DDT)] =3D 0;
}
ddt_repair_done(ddt, dde);
zio->io_vsd =3D NULL;
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Thu Jan 11 20:34:43 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2ABF7E7ACA0
for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 11 Jan 2018 20:34:43 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id C4F2FFFA
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:34:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 683C64455
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:34:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0BKYflf077365
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:34:41 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0BKYfj3077364
for freebsd-fs@FreeBSD.org; Thu, 11 Jan 2018 20:34:41 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 225080] ZFS feature request: L2ARC and encryption
compatibility: flag specifying L2ARC should hold data in encrypted form, if
source is encrypted
Date: Thu, 11 Jan 2018 20:34:41 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: cem@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-225080-3630-5curyKduYY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 20:34:43 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225080
Conrad Meyer <cem@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org
--- Comment #2 from Conrad Meyer <cem@freebsd.org> ---
$ zpool add <pool> cache <device>.eli
No?
If so, I suspect this can be CLOSED "Not a bug" or "Works as intended."
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Thu Jan 11 20:39:43 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ABAFE7B1C9
for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 11 Jan 2018 20:39:43 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 0025B1585
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:39:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D968C445E
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:39:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0BKdgCp083969
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:39:42 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0BKdgFU083966
for freebsd-fs@FreeBSD.org; Thu, 11 Jan 2018 20:39:42 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 225080] ZFS feature request: L2ARC and encryption
compatibility: flag specifying L2ARC should hold data in encrypted form, if
source is encrypted
Date: Thu, 11 Jan 2018 20:39:42 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: cem@freebsd.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Works As Intended
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-225080-3630-VoRlAv1WCC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 20:39:43 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225080
Conrad Meyer <cem@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |Works As Intended
Status|New |Closed
--- Comment #3 from Conrad Meyer <cem@freebsd.org> ---
This has been discussed and documented externally, e.g.,
http://blog.branix.net/freebsd-hints/en
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Thu Jan 11 20:47:10 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57780E7B826
for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 11 Jan 2018 20:47:10 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 3DF701C2A
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:47:10 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 270A645B4
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:47:10 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0BKlAK5003304
for <freebsd-fs@FreeBSD.org>; Thu, 11 Jan 2018 20:47:10 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0BKlAnW003303
for freebsd-fs@FreeBSD.org; Thu, 11 Jan 2018 20:47:10 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 225080] ZFS feature request: L2ARC and encryption
compatibility: flag specifying L2ARC should hold data in encrypted form, if
source is encrypted
Date: Thu, 11 Jan 2018 20:47:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Works As Intended
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-225080-3630-qGHmKaQ2Hy@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-225080-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 20:47:10 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225080
--- Comment #4 from Andriy Gapon <avg@FreeBSD.org> ---
I f you are using GELI or similar, please do use it for the cache as well, =
just
as Conrad suggested. OpenZFS is growing native encryption support and I am
confident that the cache encryption is properly handled there. But you don=
't
have to take my word for it. In any case, the proposed design is a big
layering violation and is much harder to implement that it may sound. So, =
we
are not going to do it.
If you had a patch, then it could be a slightly different story. But only
slightly.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
From owner-freebsd-fs@freebsd.org Sat Jan 13 07:18:42 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC5DCE79634
for <freebsd-fs@mailman.ysv.freebsd.org>; Sat, 13 Jan 2018 07:18:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
[IPv6:2001:1900:2254:206a::19:3])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mxrelay.ysv.freebsd.org",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id C395077E41
for <freebsd-fs@FreeBSD.org>; Sat, 13 Jan 2018 07:18:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B896A1EDAB
for <freebsd-fs@FreeBSD.org>; Sat, 13 Jan 2018 07:18:42 +0000 (UTC)
(envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0D7Igif062756
for <freebsd-fs@FreeBSD.org>; Sat, 13 Jan 2018 07:18:42 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from bugzilla@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0D7IggG062754
for freebsd-fs@FreeBSD.org; Sat, 13 Jan 2018 07:18:42 GMT
(envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to
bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 204140] ZFS's dsl_pool.c and spa_misc.c leak FreeBSD-specific
kernel routines into userland libraries
Date: Sat, 13 Jan 2018 07:18:42 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-204140-3630-kcVZ0fNL2C@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204140-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-204140-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jan 2018 07:18:43 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204140
--- Comment #3 from commit-hook@freebsd.org ---
A commit references this bug:
Author: cy
Date: Sat Jan 13 07:18:02 UTC 2018
New revision: 458892
URL: https://svnweb.freebsd.org/changeset/ports/458892
Log:
Fix build with OPENLDAP and gdbm-compatibility.
PR: 204140, 207687
Submitted by: Lawrence Chen <beastie@tardisi.com>
Changes:
head/sysutils/am-utils/Makefile
head/sysutils/am-utils/files/patch-configure.ac
head/sysutils/am-utils/pkg-plist
--=20
You are receiving this mail because:
You are the assignee for the bug.=