atus: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: p...@freebsd.org
write(2) sys call fuzzing. Easy to reproduce.
20231110 02:08:35 all (547/926): write2.sh
panic: Assertion ti->ti_linestart
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275006
Kristof Provost changed:
What|Removed |Added
Status|New |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275006
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=83dbbe8295ff0bb06a8f6b621c25d8224b026b77
commit 83dbbe8295ff0bb06a8f6b621c25d8224b026b77
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273950
andr...@gmail.com changed:
What|Removed |Added
CC||andr...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274992
--- Comment #4 from Edward Tomasz Napierala ---
It doesn't panic now, but still looks broken:
trasz@pustak:~ % doas automount -c
automount: cannot flush /net: Invalid fstype: Invalid argument
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274974
--- Comment #4 from Piotr Kubaj ---
Trying to mount on CURRENT:
nvme1: Resetting controller due to a timeout and possible hot unplug.
nvme1: resetting controller
nvme1: failing outstanding i/o
nvme1: READ sqid:5 cid:127 nsid:1 lba:73 len:8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274992
--- Comment #5 from Konstantin Belousov ---
You did see the D42023 review and referenced revisions?
Please start with ktrace and see what syscall causes the EINVAL error,
then perhaps it should be easy to see how userspace triggers it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275016
Bug ID: 275016
Summary: Move disable_rtc_set, wall_cmos_clock, adjkerntz and
rtc_save_period sysctl variables to kern namespace
Product: Base System
Version: CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274968
Alan Somers changed:
What|Removed |Added
Status|New |In Progress
