Date: Fri, 15 Feb 2013 01:07:55 +0800 From: =?ISO-8859-1?Q?Elias_M=E5rtenson?= <lokedhs@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-current@freebsd.org Subject: Re: Possible bug in NFSv4 with krb5p security? Message-ID: <CADtN0W%2BdqmN22sOkFMNeEUsc3Ljk6A1-QFNouCSqMtm_VWUv%2Bw@mail.gmail.com> In-Reply-To: <336731055.3000548.1360798935813.JavaMail.root@erie.cs.uoguelph.ca> References: <CADtN0W%2Bgd_2%2B=vxZQdL61NJAtHqpbE3BAaUp%2BQ9kAd0SXckkqw@mail.gmail.com> <336731055.3000548.1360798935813.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for your help. I'm currently in the process of analysing what is happening inside gssd during these operations. I'll get back later with a summary of my findings. However, I have found a real bug this time. An honest to FSM kernel crash. This is how I reproduced it: - Kill gssd - Attempt to mount a kerberised NFS mount from the Linux machine - The mount attempt will hang because gssd isn't running - While the mount is hung, start gssd - Kernel crash What should I do about that one? Regards, Elias
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADtN0W%2BdqmN22sOkFMNeEUsc3Ljk6A1-QFNouCSqMtm_VWUv%2Bw>