From nobody Mon Jan 15 08:31:16 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TD52m0dJ1z56L4c for ; Mon, 15 Jan 2024 08:31:28 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from mail.bsd4all.org (mail.bsd4all.org [88.99.169.216]) by mx1.freebsd.org (Postfix) with ESMTP id 4TD52l0C0Dz4n0M for ; Mon, 15 Jan 2024 08:31:26 +0000 (UTC) (envelope-from pblok@bsd4all.org) Authentication-Results: mx1.freebsd.org; none Received: from mail.bsd4all.org (localhost [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 53F4872E6; Mon, 15 Jan 2024 09:31:23 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from mail.bsd4all.org ([127.0.0.1]) by mail.bsd4all.org (mail.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id recFAljcsVeK; Mon, 15 Jan 2024 09:31:22 +0100 (CET) Received: from smtpclient.apple (pony_ip [204.168.249.121]) by mail.bsd4all.org (Postfix) with ESMTPSA id 5208B72E3; Mon, 15 Jan 2024 09:31:21 +0100 (CET) From: Peter Blok Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_4DC50FFC-0461-4C1F-9E20-CFD2DE6F9458" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: NFSv4 crash of CURRENT Date: Mon, 15 Jan 2024 09:31:16 +0100 In-Reply-To: <20240115064704.611fe0c4@thor.intern.walstatt.dynvpn.de> Cc: Cy Schubert , Rick Macklem , Ronald Klop , FreeBSD CURRENT To: FreeBSD User References: <20240113193324.3fd54295@thor.intern.walstatt.dynvpn.de> <1369645989.13766.1705178331205@localhost> <20240115043412.B6998C8@slippy.cwsent.com> <20240115064704.611fe0c4@thor.intern.walstatt.dynvpn.de> X-Mailer: Apple Mail (2.3696.120.41.1.4) X-Rspamd-Queue-Id: 4TD52l0C0Dz4n0M X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE] --Apple-Mail=_4DC50FFC-0461-4C1F-9E20-CFD2DE6F9458 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, I do have a crash on a NFS client with stable of today = (4c4633fdffbe8e4b6d328c2bc9bb3edacc9ab50a). It is also autofs related. = Maybe it is the same problem. I have ports automounted on /am/ports. When I do cd /am/ports/sys and = type tab to autocomplete it crashes with the below stack trace. If I = plainly mount ports on /usr/ports and do the same everything works. I am = using NFSv3 Peter Fatal trap 12: page fault while in kernel mode cpuid =3D 2; apic id =3D 04 fault virtual address =3D 0x89 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff809645d4 stack pointer =3D 0x28:0xfffffe00acadb830 frame pointer =3D 0x28:0xfffffe00acadb830 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 6869 (csh) trap number =3D 12 panic: page fault cpuid =3D 2 time =3D 1705306940 KDB: stack backtrace: #0 0xffffffff806232f5 at kdb_backtrace+0x65 #1 0xffffffff805d7a02 at vpanic+0x152 #2 0xffffffff805d78a3 at panic+0x43 #3 0xffffffff809d58ad at trap_fatal+0x38d #4 0xffffffff809d58ff at trap_pfault+0x4f #5 0xffffffff809af048 at calltrap+0x8 #6 0xffffffff804c7a7e at ncl_bioread+0xb7e #7 0xffffffff804b9d90 at nfs_readdir+0x1f0 #8 0xffffffff8069c61a at vop_sigdefer+0x2a #9 0xffffffff809f8ae0 at VOP_READDIR_APV+0x20 #10 0xffffffff81ce75de at autofs_readdir+0x2ce #11 0xffffffff809f8ae0 at VOP_READDIR_APV+0x20 #12 0xffffffff806c3002 at kern_getdirentries+0x222 #13 0xffffffff806c33a9 at sys_getdirentries+0x29 #14 0xffffffff809d6180 at amd64_syscall+0x110 #15 0xffffffff809af95b at fast_syscall_common+0xf8 > On 15 Jan 2024, at 06:46, FreeBSD User wrote: >=20 > Am Sun, 14 Jan 2024 20:34:12 -0800 > Cy Schubert > schrieb: >=20 >> In message = > om> =20 >> , Rick Macklem writes: >>> On Sat, Jan 13, 2024 at 12:39=3DE2=3D80=3DAFPM Ronald Klop = =3D >>> wrote: =20 >>>>=20 >>>>=20 >>>> Van: FreeBSD User >>>> Datum: 13 januari 2024 19:34 >>>> Aan: FreeBSD CURRENT >>>> Onderwerp: NFSv4 crash of CURRENT >>>>=20 >>>> Hello, >>>>=20 >>>> running CURRENT client (FreeBSD 15.0-CURRENT #4 = main-n267556-69748e62e82a=3D =20 >>> : Sat Jan 13 18:08:32 =20 >>>> CET 2024 amd64). One NFSv4 server is same OS revision as the = mentioned cl=3D =20 >>> ient, other is FreeBSD =20 >>>> 13.2-RELEASE-p8. Both offer NFSv4 filesystems, non-kerberized. >>>>=20 >>>> I can crash the client reproducable by accessing the one or other = NFSv4 F=3D =20 >>> S (a simple ls -la). =20 >>>> The NFSv4 FS is backed by ZFS (if this matters). I do not have = physicla a=3D =20 >>> ccess to the client =20 >>>> host, luckily the box recovers. =20 >>> Did you rebuild both the nfscommon and nfscl modules from the same = sources? >>> I did a commit to main that changes the interface between these two >>> modules and did bump the >>> __FreeBSD_version to 1500010, which should cause both to be rebuilt. >>> (If you have "options NFSCL" in your kernel config, both should have >>> been rebuilt as a part of >>> the kernel build.) >>>=20 >>=20 >> Is anyone by chance seeing autofs in the backtrace too? >>=20 >>=20 >=20 > Hello Cy Shubert, >=20 > I forgot to mention that those crashes occur with autofs mounted = filesystems. Good question, > by the way, I will check whether crashes also happen when mounting the = tradidional way. >=20 > Kind regards, >=20 > oh >=20 > --=20 > O. Hartmann --Apple-Mail=_4DC50FFC-0461-4C1F-9E20-CFD2DE6F9458 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

I do = have a crash on a NFS client with stable of today = (4c4633fdffbe8e4b6d328c2bc9bb3edacc9ab50a). It is also autofs related. = Maybe it is the same problem.

I have ports automounted on /am/ports. = When I do cd /am/ports/sys and type tab to autocomplete it crashes with = the below stack trace. If I plainly mount ports on /usr/ports and do the = same everything works. I am using NFSv3

Peter




Fatal trap 12: page fault while in kernel mode
cpuid =3D 2; apic id =3D 04
fault = virtual address = =3D 0x89
fault code =3D= supervisor read data, page not present
instruction = pointer = =3D 0x20:0xffffffff809645d4
stack = pointer =        =3D 0x28:0xfffffe00acadb830
frame pointer        =3D = 0x28:0xfffffe00acadb830
code segment =3D= base 0x0, limit 0xfffff, type 0x1b
= =3D DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags =3D interrupt enabled, resume, = IOPL =3D 0
current process =3D= 6869 (csh)
trap number =3D 12
panic: page fault
cpuid =3D 2
time =3D 1705306940
KDB: stack = backtrace:
#0 0xffffffff806232f5 at = kdb_backtrace+0x65
#1 0xffffffff805d7a02 at = vpanic+0x152
#2 0xffffffff805d78a3 at = panic+0x43
#3 0xffffffff809d58ad at = trap_fatal+0x38d
#4 0xffffffff809d58ff at = trap_pfault+0x4f
#5 0xffffffff809af048 at = calltrap+0x8
#6 0xffffffff804c7a7e at = ncl_bioread+0xb7e
#7 0xffffffff804b9d90 at = nfs_readdir+0x1f0
#8 0xffffffff8069c61a at = vop_sigdefer+0x2a
#9 0xffffffff809f8ae0 at = VOP_READDIR_APV+0x20
#10 0xffffffff81ce75de at = autofs_readdir+0x2ce
#11 0xffffffff809f8ae0 at = VOP_READDIR_APV+0x20
#12 0xffffffff806c3002 at = kern_getdirentries+0x222
#13 0xffffffff806c33a9 at = sys_getdirentries+0x29
#14 0xffffffff809d6180 at = amd64_syscall+0x110
#15 0xffffffff809af95b at = fast_syscall_common+0xf8



On 15 Jan 2024, at 06:46, = FreeBSD User <freebsd@walstatt-de.de> wrote:

Am Sun, 14 Jan 2024 20:34:12 -0800
Cy Schubert <Cy.Schubert@cschubert.com> schrieb:

In message <CAM5tNy5aat8vUn2fsX9jV=3DD9yGZdnO20Q0Ea7qtszx+zSES2bw@mail.gmai= l.c
om>  
, Rick Macklem = writes:
On Sat, Jan = 13, 2024 at 12:39=3DE2=3D80=3DAFPM Ronald Klop <ronald-lists@klop.ws>=3D
wrote: =  


Van: FreeBSD User <freebsd@walstatt-de.de>
Datum: 13 = januari 2024 19:34
Aan: FreeBSD CURRENT <freebsd-current@freebsd.org>
Onderwerp: = NFSv4 crash of CURRENT

Hello,

running CURRENT client (FreeBSD 15.0-CURRENT = #4 main-n267556-69748e62e82a=3D  
: Sat = Jan 13 18:08:32  
CET 2024 amd64). One NFSv4 server is same OS revision as the = mentioned cl=3D  
ient, other is FreeBSD =  
13.2-RELEASE-p8.= Both offer NFSv4 filesystems, non-kerberized.

I can crash the client reproducable by accessing the one or = other NFSv4 F=3D  
S (a simple ls -la). =  
The NFSv4 FS = is backed by ZFS (if this matters). I do not have physicla a=3D =  
ccess to the client  
host, luckily the box = recovers.  
Did you rebuild both the = nfscommon and nfscl modules from the same sources?
I did a = commit to main that changes the interface between these two
modules and did bump the
__FreeBSD_version to = 1500010, which should cause both to be rebuilt.
(If you = have "options NFSCL" in your kernel config, both should have
been rebuilt as a part of
the kernel build.)


Is anyone by = chance seeing autofs in the backtrace too?



Hello Cy Shubert,

I forgot to mention that those crashes occur with autofs = mounted filesystems. Good question,
by the way, I will check whether crashes also happen when = mounting the tradidional way.

Kind regards,

oh

-- 
O. = Hartmann

= --Apple-Mail=_4DC50FFC-0461-4C1F-9E20-CFD2DE6F9458--