From owner-freebsd-current@FreeBSD.ORG  Sat Feb 16 18:17:15 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 9E380228
 for <freebsd-current@freebsd.org>; Sat, 16 Feb 2013 18:17:15 +0000 (UTC)
 (envelope-from dfr@rabson.org)
Received: from mail-la0-x22c.google.com (la-in-x022c.1e100.net
 [IPv6:2a00:1450:4010:c03::22c])
 by mx1.freebsd.org (Postfix) with ESMTP id EFCAE7B2
 for <freebsd-current@freebsd.org>; Sat, 16 Feb 2013 18:17:14 +0000 (UTC)
Received: by mail-la0-f44.google.com with SMTP id eb20so4437712lab.17
 for <freebsd-current@freebsd.org>; Sat, 16 Feb 2013 10:17:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type:x-gm-message-state;
 bh=yIfkw590ACjMWhwEgFumkpSsqyRB8U8cVoiwRoVbJKs=;
 b=Rc7whvJNkImTFt0x2tahaa/PPgqZVKLfsY08+sBhOGnPzfUrz5Y3pnTBtiPAQqqvzc
 Jwtva3J/39Qc4UT87uFYzwogmm2o2UHbLWWmZL4eAT17Za2hetl6QGNl79eTtR1hqX7w
 VX37vUGtboNi3H7CsZekmsSAxgD1GVJ/dX5Wunbh05rxgHvGtzDv0KBwZZ2I8Cfq3XZJ
 lkyUFWnCorHkDpBgoCPDOZwMIKADgyiOmW2BVjobjKZSaa2hT3eInPGXgfI4quMH9N5c
 IL2idgiXWfd1qtytuX0zYiu3aAs3WfA9L9Ig7eMplDkxohtypOE9bw0JoxOHpYkMywZ6
 zucQ==
MIME-Version: 1.0
X-Received: by 10.112.43.38 with SMTP id t6mr3151775lbl.69.1361038633770; Sat,
 16 Feb 2013 10:17:13 -0800 (PST)
Received: by 10.112.58.225 with HTTP; Sat, 16 Feb 2013 10:17:13 -0800 (PST)
In-Reply-To: <CADtN0WJBETAgMd30Y61zvjyETmmGaQRJXixoUShMuum9h0+dGQ@mail.gmail.com>
References: <CADtN0W+gd_2+=vxZQdL61NJAtHqpbE3BAaUp+Q9kAd0SXckkqw@mail.gmail.com>
 <336731055.3000548.1360798935813.JavaMail.root@erie.cs.uoguelph.ca>
 <CADtN0WL+WxvsQBE70apKxqKPmfhh40=MqTC_FGKAJD-xBnQimA@mail.gmail.com>
 <alpine.GSO.1.10.1302151236120.9389@multics.mit.edu>
 <CADtN0WKy6SpNC_qU1ihy0OosdO8BCzBJni7T1msoS8dJDRJcgA@mail.gmail.com>
 <CADtN0WJyocVTAgvdiT8uSfW8z3Wv_gyfLso1Smm=wwCsgeiO-g@mail.gmail.com>
 <CACA0VUiiXkn6dfWCMd_s2Wspc4XSZ3Rmjm6kh7bAd8825xXhUg@mail.gmail.com>
 <CADtN0WJQMjsjDSKrE6RPXdbjZ2=e4CObt7puYF04bKB2oMp-8w@mail.gmail.com>
 <CACA0VUhbJ4Hy-9WikdDtTy77rTZx5AM=KPJa=ntJ8nfOX89u+w@mail.gmail.com>
 <CADtN0WJBETAgMd30Y61zvjyETmmGaQRJXixoUShMuum9h0+dGQ@mail.gmail.com>
Date: Sat, 16 Feb 2013 18:17:13 +0000
Message-ID: <CACA0VUgoHsr+N7dOMF7N1HQO7UvA8f24W+PkKzE=_QdMZJf8vg@mail.gmail.com>
Subject: Re: Possible bug in NFSv4 with krb5p security?
From: Doug Rabson <dfr@rabson.org>
To: =?ISO-8859-1?Q?Elias_M=E5rtenson?= <lokedhs@gmail.com>
X-Gm-Message-State: ALoCoQkupi34/DllK3umdqYWQX4D/y1gspAloZw8ITKaDnLi6W4ViqNJzChy1TDKz82EUwVRydYe
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: Rick Macklem <rmacklem@uoguelph.ca>, Benjamin Kaduk <kaduk@mit.edu>,
 freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2013 18:17:15 -0000

On 16 February 2013 16:18, Elias M=E5rtenson <lokedhs@gmail.com> wrote:

> On 17 February 2013 00:03, Doug Rabson <dfr@rabson.org> wrote:
>
>> I don't think much (if anything) has changed with gssd between 9.1 and
>> current. When your gssd hangs, you can try to get a stack trace using gd=
b's
>> attach command.
>>
>> Fair enough. However, when it hangs, I have at least a 50% chance of
> hitting the gssd-realted kerberl panic. Should I apply the patch you gave
> me, or would you suggest an upgrade?
>

I think it was Rick that mentioned the patch. I would apply the patch and
rebuild your kernel in the interests of changing as little as possible
while debugging the original issue.