[Bug 269341] [msdosfs] deadlock with sendfile

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269341 Bug ID: 269341 Summary: [msdosfs] deadlock with sendfile Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects M

[Bug 246886] [sendfile] Nginx + NFS or FUSE causes VM stall

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886 --- Comment #71 from Alan Somers --- I reproduced a similar hang in msdosfs, as described in bug 269341. Could you try the test method show there and see if it works on your fuse file system? -- You are receiving this mail because: You a

[Bug 269342] historical tzdata lost for many zones following 2021/2022 IANA tz changes

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269342 Bug ID: 269342 Summary: historical tzdata lost for many zones following 2021/2022 IANA tz changes Product: Base System Version: CURRENT Hardware: Any

[Bug 219802] Remove LINPROCFS/LINSYSFS from NOTES

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219802 Dmitry Chagin changed: What|Removed |Added Resolution|--- |FIXED Status|Open

Problem reports for b...@freebsd.org that need special attention

2023-02-05 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 269341] [msdosfs] deadlock with sendfile

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269341 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org,

[Bug 269341] [msdosfs] deadlock with sendfile

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269341 --- Comment #2 from Alan Somers --- The executable is too large to attach to bugzilla, so I put it on https://people.freebsd.org/~asomers/fsx.gz , compiled for 14.0 amd64. Also, I forgot to give the fsx.toml content used to reproduce this b

[Bug 269359] hv_hid needs a manpage

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269359 Bug ID: 269359 Summary: hv_hid needs a manpage Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 Konstantin Belousov changed: What|Removed |Added CC||p...@freebsd.org --- Comment

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 --- Comment #4 from Konstantin Belousov --- BTW, is the statement that msync(2)ing before deallocating avoids corruption, true for NFS? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 --- Comment #5 from Alan Somers --- (In reply to Konstantin Belousov from comment #4) Yes, enabling msync after every mmap write resolves the problem. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 --- Comment #6 from Konstantin Belousov --- (In reply to Alan Somers from comment #5) Is there a difference between msyncing after each write vs. msyncing before each deallocate? -- You are receiving this mail because: You are the assigne

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 --- Comment #7 from Alan Somers --- (In reply to Konstantin Belousov from comment #6) It seems that doing msync just before fspacectl doesn't fix the problem at all. Possibly that's because the test program immediately unmaps the file afte

[Bug 201650] (e)grep handling regexp wrong

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201650 --- Comment #11 from Christian Kujau --- No longer reproducible in 13.1-RELEASE-p3 (with bsdgrep 2.6.0-FreeBSD or GNU/grep 3.8): $ echo "abc" | /usr/bin/grep -Eo '^[a-z]' a $ echo "abc" | /usr/local/bin/ggrep -Eo '^[a-z]' a So...I

[Bug 269328] nfs client: data corruption using fspacectl and mmap

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269328 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org --- Comment #8

[Bug 269297] zfs: Unable to shutdown zfs machine after 52bcdd58f42dd37ca13e3671cb0d4ca87ce9a2a1(kgssapi: Increase timeout for kernel to gssd(8) upcalls)

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269297 Mark Linimon changed: What|Removed |Added CC||rmack...@freebsd.org Keyw

[Bug 269341] [msdosfs] deadlock with sendfile

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269341 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receiv

[Bug 201650] (e)grep handling regexp wrong

2023-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201650 Franz Bettag changed: What|Removed |Added Resolution|--- |FIXED Status|New