https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #27 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=896c3e6e8a61606adf4414279c4699918f921510
commit 896c3e6e8a61606adf4414279c4699918f921510
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #26 from Boris Korzun ---
(In reply to Kirk McKusick from comment #25)
Thx. The fix is working properly.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #25 from Kirk McKusick ---
Created attachment 238401
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238401&action=edit
proposed fix
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #24 from Boris Korzun ---
(In reply to Mark Millard from comment #23)
Yep, the kernel is built successful without FFS and GEOM_LABEL options.
But there wasn't a problem before b999366aab4e2d59cb8869b0e5ef0f70ab9b9bbe with
GEOM_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #23 from Mark Millard ---
(In reply to Mark Millard from comment #22)
May be the answer is geom_label not being disabled as well?
ufs/ffs/ffs_subr.c optional ffs | geom_label
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #22 from Mark Millard ---
(In reply to Boris Korzun from comment #21)
So, I info that for:
#ifdef STANDALONE_SMALL
#define MPRINT(...) do { } while (0)
#else
#define MPRINT(...) if (prtmsg) printf(__VA_ARGS__)
/*
* Pr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #21 from Boris Korzun ---
(In reply to Kirk McKusick from comment #17)
I've downloaded
FreeBSD-13.1-STABLE-amd64-20221123-b51ee7ac252c-253133-bootonly.iso, installed
it on clean ZFS system.
Tried to buildkernel with commented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #20 from Boris Korzun ---
(In reply to Mark Millard from comment #18)
There're no src.conf and make.conf.
root@boris:/usr/src# git log --oneline --no-color -n 1
c2a74ca2c3 (HEAD -> stable/13, origin/stable/13) Fix to b999366aa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #19 from Mark Millard ---
(In reply to Mark Millard from comment #18)
Cross checks on work tree status? :
git log --oneline --no-color -n 1
git branch --show-current
git status
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #18 from Mark Millard ---
(In reply to Boris Korzun from comment #16)
src.conf ? make.conf ? Anything else that might contribute to your
buildkernel details?
--
You are receiving this mail because:
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #17 from Kirk McKusick ---
(In reply to Boris Korzun from comment #16)
Just commenting out FFS from GENERIC builds fine for me. Can you send me the
output of your build that shows the error?
--
You are receiving this mail beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #16 from Boris Korzun ---
Created attachment 238218
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238218&action=edit
GENERIC-BUG
(In reply to Kirk McKusick from comment #15)
Only commented FFS options from GENERIC.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #15 from Kirk McKusick ---
(In reply to Boris Korzun from comment #13)
My 13 build was successful. Can you please provide you configuration file so I
can try building with it.
--
You are receiving this mail because:
You are on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #14 from Kirk McKusick ---
(In reply to Boris Korzun from comment #13)
I just built a 14 kernel without the FFS option and it worked fine. I will try
building a 13 kernel without FFS to see if I can reproduce your build failure.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #13 from Boris Korzun ---
(In reply to Mark Millard from comment #12)
Yep, I don't use an FFS option in my KERNEL.
=
options FFS # Berkeley Fast Filesystem
=
The buildkernel process is ok wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #12 from Mark Millard ---
(In reply to Boris Korzun from comment #11)
https://ci.freebsd.org/job/FreeBSD-stable-13-amd64-build/
reports for the official builds on the build servers:
Last build (#2244), 2 hr 5 min ago
Last sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #11 from Boris Korzun ---
(In reply to Mark Millard from comment #9)
The problem is still reproducible after the
c2a74ca2c3d9ad3465f7cb88ea60907a097fbdbc
--
You are receiving this mail because:
You are on the CC list for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kirk McKusick changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244342, which changed state.
Bug 244342 Summary: geom(4): Panic plugging in UFS USB drive: panic:
g_read_data(): invalid length 11866112 (13-CURRENT, 12.1-RELEASE r354233,
12.1-STABLE r358121)
https://bugs.freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244344, which changed state.
Bug 244344 Summary: geom(4): Panic plugging in UFS USB drive: Memory modified
after free 0xfe003a559000(65528) val=4 @ 0xfe003a559000 (13-CURRENT,
12.1-RELEASE r354233, 12.1-ST
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244346, which changed state.
Bug 244346 Summary: geom(4): Kernel panic plugging in UFS USB drive on panic:
vm_fault_lookup: fault on nofault entry, addr: 0xfe003200 (
FreeBSD13-CURRENT) via readsuper() / f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244350, which changed state.
Bug 244350 Summary: ffs(4): Kernel panic mounting UFS USB drive: panic: getblk:
size(75776) > maxbcachebuf(65536) via ffs_use_bread() (13-CURRENT, 12.1-RELEASE
r354233, 12.1-STABLE r35
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244351, which changed state.
Bug 244351 Summary: [7] Kernel panic observed while plugging the UFS USB drive
on FreeBSD13-CURRENT, FreeBSD 12.1-RELEASE r354233 and FreeBSD 12.1-STABLE
r358121
https://bugs.freebsd.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 244352, which changed state.
Bug 244352 Summary: [8] [Kernel panic: ufs_dirbad: /mnt/test: bad dir ino 2 at
offset 154: mangled entry] observed while mouting the UFS USB drive on
FreeBSD13-CURRENT, FreeBSD 12.1-RE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 257557, which changed state.
Bug 257557 Summary: geom(4): Garbage on disk (or USB memory stick) can cause
GEOM taste ffs_sbget() to crash via g_label_ufs_taste_common: panic:
vm_fault_lookup: fault on nofault entr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263811, which changed state.
Bug 263811 Summary: ffs(4): Disk with garbage can cause crash in taste ffs
crc32 code: panic: g_read_data(): invalid length -268744963
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263822, which changed state.
Bug 263822 Summary: ffs(4): malicious USB memory stick can cause panic in FFS
taste code: panic: Assertion size > 0 failed at
/usr/rtm/symbsd/src/sys/kern/subr_vmem.c:1332
https://bugs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263836, which changed state.
Bug 263836 Summary: ffs(4): Crash or hang in taste call to ffs_sbget() if not
an FFS superblock: panic: g_read_data(): invalid length -268744963
https://bugs.freebsd.org/bugzilla/show_b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263934, which changed state.
Bug 263934 Summary: buffer overflow in ffs_sbget() if superblock fields are
broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263934
What|Removed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263971, which changed state.
Bug 263971 Summary: ffs: malicious superblock can cause buffer overflow during
tasting: panic: vm_fault_lookup: fault on nofault entry, addr:
0xffc07cb67000
https://bugs.freebsd.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Boris Korzun changed:
What|Removed |Added
CC||drtr0...@yandex.ru
--- Comment #8 f
/ FFS / GEOM crash (panic) tracking
which is tracking the reported corruption bugs.
This change upgrades the checks that are performed. These additional
checks should prevent panics from a corrupted superblock. Although
it appears in only one place, the new code will apply to the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug 263979 depends on bug 263765, which changed state.
Bug 263765 Summary: panic: ffs_sync: modification on read-only filesystem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263765
What|Removed |Added
was assumed that fsck would have been run to
correct any errors before attempting to use the filesystem. Recently
several bug reports have been submitted reporting kernel panics
that can be triggered by deliberately corrupting filesystem superblocks,
see Bug 263979 - [meta] UFS / FFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
Flags|maintainer-feedback?(mckusi |
|c...@freebsd.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
--- Comment #3 from Kirk McKusick ---
See https://reviews.freebsd.org/D35219 for a proposed fix to these bug reports.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kirk McKusick changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #2 from Ki
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
Depends on||244346
Referenced Bugs:
https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
Depends on||244350
Referenced Bugs:
https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263979
Bug ID: 263979
Summary: [meta] UFS / FFS / GEOM crash (panic) tracking
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
K
46 matches
Mail list logo
