[Bug 283965] nfs: page fault during nfsrpc_readdir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283965 --- Comment #1 from Alan Somers --- I've determined that the cause of the failure in nfscl_invalidfname is because my test fuse file system includes the NUL character in its readdir entries. That is, it replies something like this: ents[0].d_namlen = 3; ents[0].d_name = ".."; ents[1].d_namlen = 2; ents[1].d_name = "."; I can and will fix that in the tests. But I can't guarantee that other fuse file systems won't do the same. Even if I have fusefs sanitize these strings in-kernel, other file systems might do the same. For example, I see that ext2 trusts the on-disk data, and copies it into a dirent without sanitizing it. So NFS must be able to handle that. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283965] nfs: page fault during nfsrpc_readdir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283965 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org --- Comment #2 from Rick Macklem --- Created attachment 256592 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256592&action=edit Fix handling of a nul in a file name received from an NFS server I think this patch should fix the crash. Hopefully Alan can test it? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278716] ucom(4)/uslcom(4)/uchcom(4) serial driver: communcation problem with FBSD > 13.2-RELENG
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278716 --- Comment #4 from O. Hartmann --- (In reply to Kyle Evans from comment #3) Of course, CURRENT and 14 STABLE, but give me some days, please, I have some time constraints at the moment. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 260121] panic: Unaligned free of 0xfffff8013cdfc800 from zone 0xfffff8001c279000(ada_ccb) slab 0xfffff8013cdfcfd8(7)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260121 Dennis Clarke changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #3 from Dennis Clarke --- Here in 2025 and I see no way to reproduce this with 15.0-CURRENT. I am thinking close this as something we may never ever see again. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 255393] panic: vm_fault_lookup: fault on nofault wntry, addr: 0xccf4000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255393 Dennis Clarke changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #4 from Dennis Clarke --- Here we are in 2025 and I see no easy way to reproduce this or even to look at it. Given that 32-bit i386 type platform is hardly tier2 these days I am going to close this as not easy to reproduce. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283939] bsdinstall: Show error message on firmware menu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283939 Renato Botelho changed: What|Removed |Added Status|Open|In Progress Assignee|b...@freebsd.org|ga...@freebsd.org --- Comment #3 from Renato Botelho --- I've proposed a fix for fwget https://reviews.freebsd.org/D48391 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283463] 14.2 Root-on-ZFS installation creates a second home directory under /mnt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283463 --- Comment #1 from drr --- T-Daemon has a detailed explanation of why this directory is being created in the Forum post below. https://forums.FreeBSD.org/threads/a-second-home-folder-created-under-mnt-on-freebsd-14-2-install.96144/post-684646 -- You are receiving this mail because: You are the assignee for the bug.
