[Bug 234454] ar produces corrupt .a archive when >4GB

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234454 Bug ID: 234454 Summary: ar produces corrupt .a archive when >4GB Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 233094] [meta] Base system tool chain modernization tracking

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Ed Maste changed: What|Removed |Added Depends on||234454 Referenced Bugs:

[Bug 167688] [fusefs] Incorrect signal handling with direct_io

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167688 --- Comment #7 from Conrad Meyer --- (In reply to Conrad Meyer from comment #6) Sigh. Yes, we PCATCH, *but*: 314 static int 315 fticket_wait_answer(struct fuse_ticket *ftick) 316 { ... 334 fuse_block_sigs(); 335 err =

[Bug 167688] [fusefs] Incorrect signal handling with direct_io

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167688 --- Comment #6 from Conrad Meyer --- That said, it seems like all sleeps in the read path in sys/fs/fuse use PCATCH. There is a PCATCH-less tsleep associated with flush, but I don't know why that would be invoked for a read. -- You are

[Bug 167688] [fusefs] Incorrect signal handling with direct_io

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167688 --- Comment #5 from Conrad Meyer --- (In reply to Alan Somers from comment #4) > The signal does not interrupt the read(2). Hm, isn't that part of the bug? Signals are supposed to interrupt blocked I/O; not interrupting explains the

[Bug 167688] [fusefs] Incorrect signal handling with direct_io

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167688 Alan Somers changed: What|Removed |Added CC||asom...@freebsd.org --- Comment #4

[Bug 234258] SIGIO not delivered on socket when incoming connection arrives

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234258 Jason A. Harmening changed: What|Removed |Added Assignee|b...@freebsd.org|j...@freebsd.org

[Bug 234205] /usr/include/sys/file.h uses the u_int typedef which causes C compilation to sometimes fail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234205 Jilles Tjoelker changed: What|Removed |Added CC||jil...@freebsd.org --- Comment

[Bug 233094] [meta] Base system tool chain modernization tracking

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Bug 233094 depends on bug 233056, which changed state. Bug 233056 Summary: [exp-run] Enable the new crtbegin/crtend in head https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233056 What|Removed |Added

Freebsd_12.0-RELEASE - reproduceable kernel trap on j1900 baytrail

Hello, every time when im booting freebsd 12.0 RELEASE, I got the following kernel-panic. If I boot in safemode gets no error/panic. Mainboard Gigabyte GA-J1900N-D3V with Intel J1900 Intel Baytrail Platform BiosVersion: F6a from 2018/03/28 Boot via USB-Stick with

[Bug 234444] cc_htcp + TCP_RFC7413

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=23 Bug ID: 23 Summary: cc_htcp + TCP_RFC7413 Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only