From nobody Mon Sep 16 22:31:16 2024 X-Original-To: fs@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 4X704j0v0Pz5W11Y for ; Mon, 16 Sep 2024 22:31:17 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X704h3V4Zz4Nb7 for ; Mon, 16 Sep 2024 22:31:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1726525876; a=rsa-sha256; cv=none; b=j6aZdxGuvTqnLxvpOHlBwpwIn1zAl3AbQIbh0fuVkKks+OwGk6Vnc8liwHiQcjy9Pq1Dus djw1qIXBgi3AN0QkSqps8sI19rNJx0yYkwaDpO7sWNvirksVFxnniir1s5GpYvofVecHFX PIjrtfgRDJrVlY0++S4Avxo43cANYNp95R78Llr+C3Aia01F8hZUbSrmljSonHdVKCbd6A lEUl4iwrn2xScXLavofYnxtmri9hkxZEddSkmx1Kk0OTZNCmeC0axFA6rCV+9WX/uP1vOd bbuoxf7oZ0Li/r/inXNBbDcmfQIaZmujAsHpBqlwu8maqd5w9Xvuc0LPwVUR9w== 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=1726525876; 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=NHnyatwbt9iAMYlmuKeizI1+QlYk3cqI4OdhYoEMdtA=; b=ByKa6WUgDpymXO/mwVP3p0ze4v/0h8IcY2BWO+1wj2SMdDCkiJA7zoniS4GiBaR9lUFQQO XScRRgH6AT1qulQhH700rUahVVbnuX31BAKRLBVOFxGBu6YOwiY/0QJMahn9/UlWkLCcnc EqeTNLJiyJhLjXpfdxFj/NcnkxX1XDAIuOWF+rNMYopdcffKy2zV6EgUOZSWGO0A0pHo9X abE82MAS70m5gFjKpqsO11W960j8zkDXjdBNG6HhBP0JOJ9hDkzsZEMCIhZwoBYGqqGmnV sMbLfJXkGs5m7l7SVdUMgaYRE7ek6oBntkmxE5saQK1AmGluBF7FWP/zGEE+mg== 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 4X704h36D9z1CRP for ; Mon, 16 Sep 2024 22:31:16 +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 48GMVGrf081228 for ; Mon, 16 Sep 2024 22:31:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 48GMVGD3081227 for fs@FreeBSD.org; Mon, 16 Sep 2024 22:31:16 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: fs@FreeBSD.org Subject: [Bug 281524] msdosfs error over USB causes a kernel panic Date: Mon, 16 Sep 2024 22:31:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: carlj@peak.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@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: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281524 --- Comment #2 from carlj@peak.org --- (In reply to Tomasz "CeDeROM" CEDRO from comment #1) I tried it with the -9 option and couldn't get it to panic. I then went ba= ck to without it and tried to verify that it still would panic, but it didn't panic. I tried various other things that I had done and still couldn't get= it to panic. That included mounting it with -r which didn't allow changes, so then I did a 'mount -uw' while I was in /mnt and mv'ed the file, but that s= till didn't panic it. I also tried unplugging it while it was still mounted, but even that didn't cause a panic. In that case I did have to umount/mount to= see any changes, which I would expect. In summary, I haven't been able to repe= at the original problem, so unless somebody can see something in the core.txt = it looks like this report should be closed. I won't do that yet to see if any= body thinks that it should be kept open. --=20 You are receiving this mail because: You are the assignee for the bug.=