[Bug 273962] copy_file_range does not work on shared memory objects

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962 --- Comment #9 from David Chisnall --- (In reply to Rick Macklem from comment #7) What are the range locking guarantees? I don't see anything in the man page (ours or Linux's) that mentions anything about locking ranges or any guarantees

[Bug 273962] copy_file_range does not work on shared memory objects

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962 --- Comment #10 from Konstantin Belousov --- (In reply to David Chisnall from comment #9) >From IEEE Standard for Information Technology— Portable Operating System Interface (POSIX®) Base Specifications, Issue 7 2.9.7 Thread Interactions w

[Bug 273962] copy_file_range does not work on shared memory objects

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962 --- Comment #11 from David Chisnall --- (In reply to Konstantin Belousov from comment #10) > when they operate on regular files or symbolic links So not necessary for the fallback case for file descriptors that are not regular files? --

[Bug 274044] FreeBSD Handbook: crypt(3) algorithms: Handbook consistency with the manual page

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274044 Bug ID: 274044 Summary: FreeBSD Handbook: crypt(3) algorithms: Handbook consistency with the manual page Product: Documentation Version: Latest Hardware: Any

[Bug 274044] FreeBSD Handbook: crypt(3) algorithms: Handbook consistency with the manual page

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274044 Graham Perrin changed: What|Removed |Added Status|New |Open -- You are receiving this ma

[Bug 273962] copy_file_range does not work on shared memory objects

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962 --- Comment #12 from Konstantin Belousov --- (In reply to David Chisnall from comment #11) It is not required, it is quality of implementation. POSIX does not require that read(2) works on shmfd at all. -- You are receiving this mail beca

[Bug 273918] Support tiers for 14.x can become actual (no longer projected)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273918 --- Comment #4 from Graham Perrin --- Thanks, (In reply to Muhammad Moinur Rahman from comment #3) +1 to 'tentative'. Narrowing of the table in comment 2 was partly to accommodate 15.x, only if re@ intends to add the column before the e

[Bug 274048] 14.0R/schedule: order, clarity, conciseness

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274048 Bug ID: 274048 Summary: 14.0R/schedule: order, clarity, conciseness Product: Documentation Version: Latest Hardware: Any URL: https://github.com/freebsd/freebsd-doc/blob/m

[Bug 274048] 14.0R/schedule: order, clarity, conciseness

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274048 --- Comment #1 from Graham Perrin --- Created attachment 245163 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=245163&action=edit Changed, rendered -- You are receiving this mail because: You are the assignee for the bug.

[Bug 274048] 14.0R/schedule: order, clarity, conciseness

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274048 Graham Perrin changed: What|Removed |Added Keywords|needs-patch | Status|New

[Bug 274048] 14.0R/schedule: order, clarity, conciseness

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274048 Graham Perrin changed: What|Removed |Added CC||r...@freebsd.org Attachment #24516

[Bug 263330] Extend the FreeBSD Handbook jails section to mention iocage

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263330 Graham Perrin changed: What|Removed |Added CC|carlavi...@freebsd.org |d...@freebsd.org Assigne

[Bug 273700] NVIDIA (not NVidia, not Nvidia)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273700 Graham Perrin changed: What|Removed |Added Resolution|FIXED |--- Status|Closed

[Bug 273700] NVIDIA (not NVidia, not Nvidia)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273700 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/doc/commit/?id=4e527c57b377839647ce0d3648b1a241668d63a5 commit 4e527c57b377839647ce0d3648b1a241668d63a5 Author:

[Bug 273700] NVIDIA (not NVidia, not Nvidia)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273700 Sergio Carlavilla Delgado changed: What|Removed |Added Keywords|needs-patch | Status|Op

[Bug 273700] NVIDIA (not NVidia, not Nvidia)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273700 --- Comment #6 from Graham Perrin --- (In reply to commit-hook from comment #5) Thanks. Incidentally (for the future): after the first use of ® for a registered trademark, it's normally unnecessary to repeat the character for subsequent

[Bug 182819] pfctl(8) interprets "# .... \" as multi-line comment

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182819 Graham Perrin changed: What|Removed |Added Priority|Normal |--- CC|

[Bug 274019] certctl(8): manual page following 05a16147fb39 (certctl: fix hashed link generation with duplicate subjects)

2023-09-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274019 Graham Perrin changed: What|Removed |Added Product|Base System |Documentation Summary|c