From nobody Mon Oct 02 16:40:45 2023 X-Original-To: bugs@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 4Rzmsn73gRz4wG49 for ; Mon, 2 Oct 2023 16:40:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rzmsn63RMz4PWT for ; Mon, 2 Oct 2023 16:40:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1696264845; a=rsa-sha256; cv=none; b=ueIQ1ca3kVU4dE5r+WP4ot6jlkeF43SxWBZ8FCqvg4yx5R0RkAjsqs3A3ebrICkJutn/Nr cPi3nFm21Rrbn4BbDRmZDvj0IkRAZDIRG9g1enzKvHesTHI9azi8Oi8uA7kqoQjeQMpBhr 46KS57g2iqjeagyaxvGcGFv+v86Mr59uhnEjKphdiadT6lekGwcG9DHqHlbKxfBOvN94J1 GRmWUEXoP1O1918SdFrblnekOYyYYLdbPxmxXbQY0m0abxRzCsaCVH0jc6gckji7qfJaey SjXQPpItGBNHki/Hv/5QGEkPRMze6CdjLa15xloATf8yvf3/LNFZXgzfBO7vCA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1696264845; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AJHdQqfXlDKV2Hun4nWVn1mTcKGWNt/IfXIcbr370/o=; b=KTkvCTs0SpdDxhtrTr25zCwmfzZfI0f077eMdqBtHf7VxPXDLrjQZZNHjLu9kKbPNR0vWn AvmN4pTkm3qRNpG72S3QwBctDewYlSi88wslazIj7X9sV85rgsIgX6k1YKmkrBbqGdXVFq kTuEOGvRgqbZd75AHB76X30s/xncVRt6j90U1kBGb/i6+XBw0uNMWwG5Fh8cUFCFnngUfH jK26RlCn96eh4YAYsljSfjcqWmHPpSUJas3ueg4ZSmdbmLD0RBvlXnks+fHDq9pIE5n+Pd Z65kFePWf6p2Ww8C7zE79FlrWt6uGdtklIse2epxm4b69gl2Yjybb3Yc1pD5/g== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Rzmsn55VWz4Ry for ; Mon, 2 Oct 2023 16:40:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 392GejoD074710 for ; Mon, 2 Oct 2023 16:40:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 392Gejpf074709 for bugs@FreeBSD.org; Mon, 2 Oct 2023 16:40:45 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: bugs@FreeBSD.org Subject: [Bug 273715] dumpon: Kernel panic on boot when enabling dumpon over IP Date: Mon, 02 Oct 2023 16:40:45 +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: 13.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zlei@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273715 --- Comment #11 from Zhenlei Huang --- A minimal snip to repeat this bug: ``` # dumpon -i 0 -c 192.168.255.3 -g 192.168.255.1 -s 192.168.255.1 nonexist ``` > I see various options how to resolve this: > 1. Always allow using the physical device name (so it would somehow poke = around and find it) > 2. Add a flag to dumpon (e.g., `-f` for force) to skip the device exists/= device supports debugnet check > 3. Allow specifying multiple devices netdump_client to try when dumping > 4. Determine based on the device name if it can exist early (feels wonky) The `dumpon` start quite early, even before `FILESYSTEMS`. At that time `ne= tif` (interface renaming) has no chances to run. I guess it is intended to let dumpon run as early as possible so that almost all kernel panics can be caught rightly. Well for netdump(4), if a pubkey is requested, then dumpon requires `FILESYSTEMS`. I guess we want to defer the setup of netdump(4), until `FILESYSTEMS` (prob= ably also `netif`) is/are ready. Or we can split the rc.d/dumpon into `rc.d/dumpon` and `rc.d/netdump`. --=20 You are receiving this mail because: You are the assignee for the bug.=