From nobody Tue Jul 20 18:36:39 2021 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 D50171245AD7 for ; Tue, 20 Jul 2021 18:36:39 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GTnVb5GNBz3jRX for ; Tue, 20 Jul 2021 18:36:39 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qv1-xf2b.google.com with SMTP id i4so10565259qvq.10 for ; Tue, 20 Jul 2021 11:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ETAvJPBFeXLknJ0zGbykGOpSV/CJF7Ppj9JkNTq60EI=; b=qavS47Fki+mVzdEnQWvKKEGR0kyN1quIIqB55cRt3tx4K4SXiiHe88gqVDAXNOxM8l TVrSlml3tS6qT3dUCTjYxywmJCcudK0dO0k2WjzdSUEcDEpXZEGKXGh8Wzib8aVCQvL/ shBijxSW22vBX6NONOUlaRCe9C7c+a4RFzDCTiTYHIrNhXvtA+NewBx4wIfv6WPT7u7Q z6rl0UN0m0AexMrHIHY4/Qj/56hWenYrwrFPlCWI7o+wPBVpYAEmE/2d6VF4W/JOE200 XKAaxU8OV+uOzUuH6lPLIB/nH9vbVTk+DsmtlNj0WgWZypalRpeZ8ZuM7BkuzbYwJRa7 PNFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=ETAvJPBFeXLknJ0zGbykGOpSV/CJF7Ppj9JkNTq60EI=; b=UsaHzkW08yDc/6NOTZFNfAifVS8aCvlv+SqseOBf4PDcwO5/L7+8bqHlhkyt5fZCgl rdAD0WVlcjiRjSQx4AMRHOPSd39QHTjwieBA7CMEGcISugqUGZgq3UTxnMVqo26a2L6e +ub81lfFNXlXa/ePhxG68IVma+Kw/UkbtY+C/QD4LKwmtzt4bpKw5NPpuRDV2GkBO3FY tRqlhc7iMjEnXV9eEHjF5gHjfUiDyUdsBxcPDbCm7ucxzZz10VfuuK9DrUqv+iC8EkKL yufOnH2iyl14Di6PSUiethM6nl9MBKqaxSbV5jZJmrN0zVGgGRmr7u3XZiH6c7EB0vZM LTxw== X-Gm-Message-State: AOAM533fvuG5Qqwc6l/RcxIz0OQD5G2cilR9HyABQs/ej9MzHKOs59Ok 01vhTXoXaK3OoCSHVnQE9xPl1hBaJFg= X-Google-Smtp-Source: ABdhPJy5Piv3M8GidsgJB/KThv5bjsIVgQvnxiPYojeoh1THSeFa9dsKt7QtbsM+KkIQFAGFSYaH3Q== X-Received: by 2002:a0c:fac9:: with SMTP id p9mr32201405qvo.57.1626806198764; Tue, 20 Jul 2021 11:36:38 -0700 (PDT) Received: from nuc ([142.126.183.196]) by smtp.gmail.com with ESMTPSA id r5sm7949494qtm.75.2021.07.20.11.36.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Jul 2021 11:36:38 -0700 (PDT) Date: Tue, 20 Jul 2021 14:36:39 -0400 From: Mark Johnston To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: panic: vm_domainset_iter_first: Unknown policy 15168 Message-ID: References: <20210719220219.GA1010@troutmask.apl.washington.edu> <20210720020503.GA32856@troutmask.apl.washington.edu> <20210720160704.GA35184@troutmask.apl.washington.edu> <20210720171320.GA35542@troutmask.apl.washington.edu> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210720171320.GA35542@troutmask.apl.washington.edu> X-Rspamd-Queue-Id: 4GTnVb5GNBz3jRX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Jul 20, 2021 at 10:13:20AM -0700, Steve Kargl wrote: > On Tue, Jul 20, 2021 at 12:15:58PM -0400, Mark Johnston wrote: > > On Tue, Jul 20, 2021 at 09:07:04AM -0700, Steve Kargl wrote: > > > On Mon, Jul 19, 2021 at 07:05:03PM -0700, Steve Kargl wrote: > > > > On Mon, Jul 19, 2021 at 07:55:07PM -0400, Mark Johnston wrote: > > > > > On Mon, Jul 19, 2021 at 03:02:19PM -0700, Steve Kargl wrote: > > > > > > > > > > > > (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > > > > > > #1 doadump (textdump=textdump@entry=1) > > > > > > at /usr/src/sys/kern/kern_shutdown.c:399 > > > > > > #2 0xffffffff805fe263 in kern_reboot (howto=260) > > > > > > at /usr/src/sys/kern/kern_shutdown.c:486 > > > > > > #3 0xffffffff805fe6b0 in vpanic (fmt=, ap=) > > > > > > at /usr/src/sys/kern/kern_shutdown.c:919 > > > > > > #4 0xffffffff805fe4b3 in panic (fmt=) > > > > > > at /usr/src/sys/kern/kern_shutdown.c:843 > > > > > > #5 0xffffffff8085dcbb in vm_domainset_iter_first (di=, > > > > > > domain=) at /usr/src/sys/vm/vm_domainset.c:189 > > > > > > #6 0xffffffff8085dbd2 in vm_domainset_iter_page_init ( > > > > > > di=di@entry=0xfffffe012ae5e2a0, obj=obj@entry=0xfffff8003c21f420, > > > > > > pindex=, pindex@entry=16931, > > > > > > domain=domain@entry=0xfffffe012ae5e2f4, req=, > > > > > > req@entry=0xfffffe012ae5e2f0) at /usr/src/sys/vm/vm_domainset.c:217 > > > > > > > > > > Could you please show output from: > > > > > > > > > > (kgdb) frame 6 > > > > > (kgdb) p *dr > > > > > (kgdb) p obj->domain > > > > > > > > > > > > > The system is at work. I'll do this tomorrow morning. > > > > Thanks for asking for additional info. > > > > > > > > > > Hi Mark, I poked around and tried to supply the request info > > > along with content of other structs. > > > > Is the problem reproducible? > > Don't know if it matters, but the DVD was prepared on a MS > Windows 10 system. I don't know what software was used. > > I got 4 different panics while trying to copy data from > the UDF disk. > > % mount_udf /dev/cd0 /cdrom > > This mounts the drive and I can ls and cd into it. If I do > > % cd ${HOME}/data <-- UFS2, softupdate > % cp -R /cdrom/data . > > where /cdrom/data is a directory with 4000-ish files, I > eventually get a panic. Two of the other panics are of > the form (which may be a result of UDF handing FFS bad > data). I see, it looks like there is some generic memory corruption triggered by the UDF implementation. Our implementation is fairly stale, unfortunately, but it shouldn't trigger a panic. If you don't already have INVARIANTS configured, that would probably help narrow this down. If you're able to share the image that can trigger this, I could try to debug from that.