src/sys/compat/linux/linux_file.c, branch releng/15.0 FreeBSD source tree kern: allow kern_shm_open2 of an anonymous preconstructed shmfd 2025-07-26T21:31:40+00:00 Kyle Evans kevans@FreeBSD.org 2025-07-14T23:28:35+00:00 6b49d119489944abbef87b5892c21f65e7a7055e The motivation here is for future changes to the coredump code to be able to build up a coredump into a shmfd instead of a vnode, which then gets tapped out to userland via a character device. This also opens up the possibility that it's useful for the kernel to be able to construct a shmfd and pass it out to a process that shouldn't need to write to it. Reviewed by: emaste, kib, markj Differential Revision: https://reviews.freebsd.org/D51336 
The motivation here is for future changes to the coredump code to be
able to build up a coredump into a shmfd instead of a vnode, which then
gets tapped out to userland via a character device.  This also opens up
the possibility that it's useful for the kernel to be able to construct
a shmfd and pass it out to a process that shouldn't need to write to it.

Reviewed by:	emaste, kib, markj
Differential Revision:	https://reviews.freebsd.org/D51336
linux: Add inotify support 2025-07-04T14:42:34+00:00 Mark Johnston markj@FreeBSD.org 2025-06-06T13:25:09+00:00 3965de642c29d831649c8307203303de560d721a Implement the Linux inotify system calls using the native implementation in vfs_inotify.c. PR: 240874 Reviewed by: brooks MFC after: 3 months Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D50761 
Implement the Linux inotify system calls using the native implementation
in vfs_inotify.c.

PR:		240874
Reviewed by:	brooks
MFC after:	3 months
Sponsored by:	Klara, Inc.
Differential Revision:	https://reviews.freebsd.org/D50761
faccessat(2): Honor AT_SYMLINK_NOFOLLOW 2024-08-11T15:49:06+00:00 Fernando Apesteguía fernape@FreeBSD.org 2024-08-11T15:43:04+00:00 5ab6ed93cd3680f8b69dd4d05823f4740a2bdef9 Make the system call honor `AT_SYMLINK_NOFOLLOW`. Also enable this from `linux_faccessat2` where the issue arised the first time. Update manual pages accordingly. PR: 275295 Reported by: kenrap@kennethraplee.com Approved by: kib@ Differential Revision: https://reviews.freebsd.org/D46267 
Make the system call honor `AT_SYMLINK_NOFOLLOW`.

Also enable this from `linux_faccessat2` where the issue arised the first time.
Update manual pages accordingly.

PR:			275295
Reported by:		kenrap@kennethraplee.com
Approved by:		kib@
Differential Revision:	https://reviews.freebsd.org/D46267
linux: Export linux_common_openflags() 2024-05-23T19:40:46+00:00 Ricardo Branco rbranco@suse.de 2024-05-17T20:08:24+00:00 9c7b1bf27122f975ea70c81931d48b751f8a1bfa Reviewed by: imp, kib Pull Request: https://github.com/freebsd/freebsd-src/pull/1248 
Reviewed by: imp, kib
Pull Request: https://github.com/freebsd/freebsd-src/pull/1248
Abstract UIO allocation and deallocation. 2024-02-10T16:38:04+00:00 Alfredo Mazzinghi am2419@cl.cam.ac.uk 2024-01-18T13:04:41+00:00 61cc4830a7b16400efade3d884a59fda6d80d651 Introduce the allocuio() and freeuio() functions to allocate and deallocate struct uio. This hides the actual allocator interface, so it is easier to modify the sub-allocation layout of struct uio and the corresponding iovec array. Obtained from: CheriBSD Reviewed by: kib, markj MFC after: 2 weeks Sponsored by: CHaOS, EPSRC grant EP/V000292/1 Differential Revision: https://reviews.freebsd.org/D43711 
Introduce the allocuio() and freeuio() functions to allocate and
deallocate struct uio. This hides the actual allocator interface, so it
is easier to modify the sub-allocation layout of struct uio and the
corresponding iovec array.

Obtained from:	CheriBSD
Reviewed by:	kib, markj
MFC after:	2 weeks
Sponsored by:	CHaOS, EPSRC grant EP/V000292/1
Differential Revision:	https://reviews.freebsd.org/D43711
linux(4): Replace linux32_copyinuio by freebsd32_copyinuio 2023-08-20T07:36:32+00:00 Dmitry Chagin dchagin@FreeBSD.org 2023-08-20T07:36:32+00:00 c987ff4d7bd25e9186ffca84c7e873fd7382a1c7 MFC after: 1 month 
MFC after:		1 month
linux(4): Return EAGAIN instead of ENOBUFS for non-blocking sockets in pwrite 2023-08-20T07:36:31+00:00 Dmitry Chagin dchagin@FreeBSD.org 2023-08-20T07:36:31+00:00 d6cb9e728b3737d19da7a5554d1c6b740a29e69d MFC after: 1 month 
MFC after:		1 month
linux(4): Return EAGAIN instead of ENOBUFS for non-blocking sockets in pwritev 2023-08-20T07:36:31+00:00 Dmitry Chagin dchagin@FreeBSD.org 2023-08-20T07:36:31+00:00 dfbb3e2aaec2709f3e68a6657bf2a656a4adbe27 MFC after: 1 month 
MFC after:		1 month
linux(4): Add a dedicated writev syscall wrapper 2023-08-20T07:36:31+00:00 Dmitry Chagin dchagin@FreeBSD.org 2023-08-20T07:36:31+00:00 4231b825ac19112b84b4001625e0ef7a80e82f80 Adding a writev syscall wrapper is needed due to Linux family of write syscalls doesn't distinguish between in kernel blocking operations and always returns EAGAIN while FreeBSD can return ENOBUFS. MFC after: 1 month 
Adding a writev syscall wrapper is needed due to Linux family of write
syscalls doesn't distinguish between in kernel blocking operations
and always returns EAGAIN while FreeBSD can return ENOBUFS.

MFC after:		1 month
linux(4): Add a write syscall wrapper 2023-08-20T07:36:29+00:00 Dmitry Chagin dchagin@FreeBSD.org 2023-08-20T07:36:29+00:00 e58ff66464ac313296b683992c9131d7a85047de Adding a write syscall wrapper is needed due to Linux family of write syscalls doesn't distinguish between in kernel blocking operations and always returns EAGAIN while FreeBSD can return ENOBUFS. MFC after: 1 month 
Adding a write syscall wrapper is needed due to Linux family of write
syscalls doesn't distinguish between in kernel blocking operations
and always returns EAGAIN while FreeBSD can return ENOBUFS.

MFC after:		1 month