https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
Mina Galić changed:
What|Removed |Added
CC||free...@igalic.co
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270841
Bug ID: 270841
Summary: fstat causes kernel panic with nullfs mount from NFS
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270841
Henry Hu changed:
What|Removed |Added
Summary|fstat causes kernel panic |fstat causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270841
--- Comment #1 from Henry Hu ---
It seems like that I'm speaking too soon. After removing the nullfs mounts from
NFS mount, I can still trigger kernel panic:
Unread portion of the kernel message buffer:
Fatal double fault
rip 0x8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270785
--- Comment #6 from bllcha...@myuct.ac.za ---
Interestingly, there is a bug report for Minecraft that seems related:
https://bugs.mojang.com/browse/MC-183518
It seems that an extremely low timeout is causing massive numbers of calls per
sec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270785
--- Comment #7 from Alexander Motin ---
Your analysis exactly matches my expectations. I'd say it is a Minecraft bug,
not OS. May be we could introduce some tunable to limit minimal sleep time,
but I hate tunables in general.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270841
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270841
Henry Hu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270842
Bug ID: 270842
Summary: [nfsclient] sees out-of-date metadata until stat(1)
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
--- Comment #3 from Ihor Antonov ---
Nathan's motivation for the shutdown delay is to avoid race conditions caused
by asynchronous signal processing.
After https://reviews.freebsd.org/rG8935a3993219be76c7ea03e9ad4509657d08af6c
was merged
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254511
Mina Galić changed:
What|Removed |Added
CC||free...@igalic.co
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Marek Zarychta changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270728
--- Comment #4 from free...@thehugheslogcabin.net ---
Created attachment 241491
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241491&action=edit
Output from script tracking time
This is the output of a script I wrote to track ti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=116643
Dave Cottlehuber changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
--- Comment #4 from Nathan Huff ---
I think the only thing the kqueue version doesn't do that my patch does is send
SIGKILL to the supervised process after the delay. I see there is a TODO in
the kqueue version to do something like that, b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270810
--- Comment #5 from geoff...@dommett.com ---
update. calling msync with MS_SYNC only reduces the number of pages that fail
to be written. it does not eliminate them. The return value of msync is 0, so
the system claims that the call has succ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=143962
Dave Cottlehuber changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
--- Comment #5 from Ihor Antonov ---
We can add sleep before sending SITERM to the child, but why is this needed?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
--- Comment #6 from Ihor Antonov ---
Sorry, disregard my previous comment. SIGKILL after delay is planned.
I will use EVFILT_TIMER for this.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580
Nathan Huff changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212829
--- Comment #8 from Ihor Antonov ---
After reading all comments I take the side of Phillip R. Jaenke (prj)
Different services expect different signals, so creating a mechanism to pass
signals to a child leaves a question "how to signal dae
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212829
--- Comment #9 from Ihor Antonov ---
See /etc/rc.d/ipfilter for a concrete example of custom commands
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236117
--- Comment #2 from Ihor Antonov ---
zhou...@laocius.org:
You could send logs to syslog, if that works for you.
Check these daemon options:
--syslog Send output to syslog
--output-mask What to send to syslog/file
1=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270842
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=270785
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|thre...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270811
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
CC
27 matches
Mail list logo
