Page MenuHomeFreeBSD

rmacklem (Rick Macklem)
User

Projects

User Details

User Since
Jan 13 2015, 10:58 PM (560 w, 6 d)

Recent Activity

Yesterday

rmacklem accepted D52961: sys/rpc: Define AUTH_SYS_MAX_{GROUPS,HOSTNAME}.
Mon, Oct 13, 10:41 PM
rmacklem accepted D52963: sys/rpc: UNIX auth: Use AUTH_SYS_MAX_{GROUPS,HOSTNAME} as limits (2/2).
Mon, Oct 13, 10:40 PM
rmacklem committed rG4fc1e7546f12: RELNOTES: Fix a typo in the 5000d023a446 entry (authored by rmacklem).
RELNOTES: Fix a typo in the 5000d023a446 entry
Mon, Oct 13, 10:08 PM
rmacklem added inline comments to D52962: sys/rpc: UNIX auth: Use AUTH_SYS_MAX_{GROUPS,HOSTNAME} as limits (1/2).
Mon, Oct 13, 1:57 PM
rmacklem committed rGa7fc4e326c8d: rpc.tlsservd.c: Pin max threads at 1 for now (authored by rmacklem).
rpc.tlsservd.c: Pin max threads at 1 for now
Mon, Oct 13, 12:33 AM

Sun, Oct 12

rmacklem accepted D52960: sys/rpc: UNIX auth: Fix OOB accesses, notably writes on decode.

Looks ok to me. I'll leave min vs MIN up to you.

Sun, Oct 12, 11:50 PM
rmacklem committed rG1129bf441e99: RELNOTES: Fix up the entry for 5000d023a446 (authored by rmacklem).
RELNOTES: Fix up the entry for 5000d023a446
Sun, Oct 12, 12:48 AM
rmacklem committed rG9504e956c508: RELNOTES: Add an entry for commit 5000d023a446 (authored by rmacklem).
RELNOTES: Add an entry for commit 5000d023a446
Sun, Oct 12, 12:41 AM

Fri, Oct 10

rmacklem committed rG7a289fe3cd5c: rpc.tlsservd.c: Pin max threads at 1 for now (authored by rmacklem).
rpc.tlsservd.c: Pin max threads at 1 for now
Fri, Oct 10, 11:33 PM
rmacklem accepted D52962: sys/rpc: UNIX auth: Use AUTH_SYS_MAX_{GROUPS,HOSTNAME} as limits (1/2).

Looks ok to me. You can decide whether or not to add the
KASSERT for x_op != XDR_FREE?

Fri, Oct 10, 10:29 PM

Wed, Oct 8

rmacklem accepted D52964: sys/rpc: UNIX auth: Fix OOB reads on too short message.

Looks fine to me. Feel free to ignore the minor comments.

Wed, Oct 8, 2:04 PM
rmacklem committed rG23fbea8cf2f3: kadmin.8: Document the new dump -f flag (authored by rmacklem).
kadmin.8: Document the new dump -f flag
Wed, Oct 8, 1:54 AM
rmacklem committed rG9fd3b28d4e0d: heimdal-kadmin: Add support for the -f dump option (authored by rmacklem).
heimdal-kadmin: Add support for the -f dump option
Wed, Oct 8, 1:53 AM

Tue, Oct 7

rmacklem added a comment to D52970: krb5: create the KDC database directory.
In D52970#1210155, @cy wrote:

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

In share/examples/krb5 maybe?

Tue, Oct 7, 9:50 PM
rmacklem accepted D52970: krb5: create the KDC database directory.

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

Tue, Oct 7, 9:13 PM

Sun, Oct 5

rmacklem committed rG03da141d59ae: kadmin.8: Document the new dump -f flag (authored by rmacklem).
kadmin.8: Document the new dump -f flag
Sun, Oct 5, 9:10 PM
rmacklem committed rG5000d023a446: heimdal-kadmin: Add support for the -f dump option (authored by rmacklem).
heimdal-kadmin: Add support for the -f dump option
Sun, Oct 5, 4:22 PM

Wed, Oct 1

rmacklem committed rG4771b65fde48: rpc_generic.c: Fix a rpcbind core dump when rpcinfo is done (authored by rmacklem).
rpc_generic.c: Fix a rpcbind core dump when rpcinfo is done
Wed, Oct 1, 12:56 AM

Sun, Sep 28

rmacklem closed D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.
Sun, Sep 28, 3:01 PM
rmacklem committed rG70730cd21c9f: rpc_generic.c: Fix a rpcbind core dump when rpcinfo is done (authored by rmacklem).
rpc_generic.c: Fix a rpcbind core dump when rpcinfo is done
Sun, Sep 28, 3:01 PM
rmacklem added inline comments to D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.
Sun, Sep 28, 2:44 PM
rmacklem added inline comments to D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.
Sun, Sep 28, 1:35 PM

Sat, Sep 27

rmacklem added a comment to D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.

Just fyi. Unless I hear otherwise I am going to commit
this patch Monday, so that it can be MFC'd to stable/15.
It stops rpcbind from crashing. If others don't like the
choice of address string for netlink, that can be changed
later.

Sat, Sep 27, 7:24 PM

Thu, Sep 25

rmacklem added a comment to D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.

What code does call into this function with netlink argument? IMHO, this transport layer abstraction of RPC is a big code bloat where most of the code is never executed. Of course a crash if it happens needs to be fixed.

Thu, Sep 25, 10:49 PM
rmacklem added a comment to D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.

What code does call into this function with netlink argument? IMHO, this transport layer abstraction of RPC is a big code bloat where most of the code is never executed. Of course a crash if it happens needs to be fixed.

Thu, Sep 25, 10:05 PM

Sat, Sep 20

rmacklem updated the summary of D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.
Sat, Sep 20, 11:11 PM
rmacklem requested review of D52651: rpcbind: Fix a coredump that occurs when rpcinfo is done.
Sat, Sep 20, 11:10 PM

Sep 9 2025

rmacklem committed rGbda48373633c: exports.5: Add a paragraph clarifying the use of "V4:" (authored by rmacklem).
exports.5: Add a paragraph clarifying the use of "V4:"
Sep 9 2025, 1:03 AM
rmacklem committed rGcaf162412dbc: exports.5: Add a paragraph clarifying the use of "V4:" (authored by rmacklem).
exports.5: Add a paragraph clarifying the use of "V4:"
Sep 9 2025, 12:55 AM

Sep 7 2025

rmacklem committed rGb84156e7f136: nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir (authored by rmacklem).
nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir
Sep 7 2025, 1:38 AM

Sep 4 2025

rmacklem committed rG1c52d525f064: nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir (authored by rmacklem).
nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir
Sep 4 2025, 1:52 AM
rmacklem closed D52370: nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir.
Sep 4 2025, 1:52 AM

Sep 3 2025

rmacklem requested review of D52370: nfsd: Fix the NFSv4 Readdir operation for an empty ZFS dir.
Sep 3 2025, 10:40 PM

Sep 2 2025

rmacklem added inline comments to D52263: krpc: UNIX auth: Prevent DoS, fix various OOB accesses.
Sep 2 2025, 2:51 PM
rmacklem added a comment to D52263: krpc: UNIX auth: Prevent DoS, fix various OOB accesses.

So, while I'm here, I'd also like to know what you think about discarding groups exceeding the NGROUPS limit.
(snip)

According to RFC 5531, the authsys_parms structure for AUTH_SYS contains in fact the effective group ID (spelled out exactly like this in the RFC) and then an array of 16 groups "that contain the caller as a member". But we only have XU_NGROUPS (16) in total in struct xucred.

So, what do you think of:

  1. To support the protocol, we accept up to 17 groups (1 + 16), but no more (extensions are not supported).
  2. But we discard the 17th one, as we don't have room to store it.

This is in fact what the inline decode version is already doing.

Sep 2 2025, 2:38 PM
rmacklem added a comment to D52263: krpc: UNIX auth: Prevent DoS, fix various OOB accesses.

I made a few comments, but stopped there.
You seem to be confusing the 16 which is
a hardwired RPC constant with what happens
to be defined elsewhere.
(Even if XU_NGROUPS == 16 there is nothing
stopping someone from changing that someday.)

Sep 2 2025, 1:06 AM

Aug 29 2025

rmacklem resigned from D52273: NFS users: Do not pass effective GID in group list, fill all fields.

I'll admit I do not understand what your recent gid
changes are, so I will resign as a reviewer.

Aug 29 2025, 11:56 PM
rmacklem committed rGb06973a2f2a8: nfsd: Fix slow leaks of NAMEI buffers (authored by rmacklem).
nfsd: Fix slow leaks of NAMEI buffers
Aug 29 2025, 3:23 AM

Aug 27 2025

rmacklem accepted D52195: nfs client: switch nfs_advlock() to use exclusive vnode lock.

Looks fine to me.

Aug 27 2025, 10:32 PM

Aug 26 2025

rmacklem committed rG200730f29dbc: exports.5: Add a paragraph clarifying the use of "V4:" (authored by rmacklem).
exports.5: Add a paragraph clarifying the use of "V4:"
Aug 26 2025, 1:43 AM
rmacklem closed D52141: exports.5: Add a paragraph clarifying the use of "V4:".
Aug 26 2025, 1:43 AM

Aug 24 2025

rmacklem requested review of D52141: exports.5: Add a paragraph clarifying the use of "V4:".
Aug 24 2025, 11:14 PM

Aug 23 2025

rmacklem added a comment to D51845: vfs_syscalls.c: Fix handling of offset arguments for copy_file_range.

The not so good news is that this bug made it out into 14.3.

I'll submit an EN since this is my bug (unless you'd really like to).

You are more than welcome to do so.
I'll give it a 2week MFC and you'll see it go into stable/14 in two weeks.

Aug 23 2025, 9:49 PM
rmacklem committed rGea35c5b54fcc: UPDATING: Add an entry for commit 3f61ececacd8 (authored by rmacklem).
UPDATING: Add an entry for commit 3f61ececacd8
Aug 23 2025, 9:36 PM
rmacklem committed rG4f22d274ab0d: param.h: Bump __FreeBSD_version for 3f61ececacd8 (authored by rmacklem).
param.h: Bump __FreeBSD_version for 3f61ececacd8
Aug 23 2025, 9:34 PM
rmacklem committed rG2fd0083fcc23: vfs_syscalls.c: Fix handling of offset args for copy_file_range (authored by rmacklem).
vfs_syscalls.c: Fix handling of offset args for copy_file_range
Aug 23 2025, 9:25 PM
rmacklem committed rG248daca0b3c3: nfscl: Fix GetACL so that it does not want a reply cached (authored by rmacklem).
nfscl: Fix GetACL so that it does not want a reply cached
Aug 23 2025, 9:24 PM
rmacklem committed rG3f61ececacd8: nfsd: Avoid relocking vnode for NFSv4 Readdir (authored by rmacklem).
nfsd: Avoid relocking vnode for NFSv4 Readdir
Aug 23 2025, 9:20 PM

Aug 22 2025

rmacklem committed rGe39c9ac21358: copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flag (authored by rmacklem).
copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flag
Aug 22 2025, 10:05 PM
rmacklem closed D51938: copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flags argument.
Aug 22 2025, 10:05 PM
rmacklem updated the diff for D51938: copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flags argument.

Made changes suggested by kib@.

Aug 22 2025, 8:44 PM
rmacklem committed rGb5a18ea27f7a: vfs_vnops.c: Change the error return from ENOSYS to EOPNOTSUPP (authored by rmacklem).
vfs_vnops.c: Change the error return from ENOSYS to EOPNOTSUPP
Aug 22 2025, 8:36 PM

Aug 18 2025

rmacklem added inline comments to D51988: nfs and cd9660: normalize handling of va_rdev.
Aug 18 2025, 4:21 AM
rmacklem added inline comments to D51988: nfs and cd9660: normalize handling of va_rdev.
Aug 18 2025, 3:28 AM
rmacklem accepted D51988: nfs and cd9660: normalize handling of va_rdev.
Aug 18 2025, 3:23 AM
rmacklem accepted D51987: nfsport.h: minor comments cleanup.
Aug 18 2025, 3:21 AM

Aug 17 2025

rmacklem added a comment to D51938: copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flags argument.

Thanks for the feedback. I'm off doing other things for
a few days, but will update this next weekend.

Aug 17 2025, 3:16 AM

Aug 16 2025

rmacklem requested review of D51938: copy_file_range.2: Document the COPY_FILE_RANGE_CLONE flags argument.
Aug 16 2025, 11:02 PM
rmacklem accepted D51930: zfs: fixes for readdir.
Aug 16 2025, 4:48 AM
rmacklem added inline comments to D51930: zfs: fixes for readdir.
Aug 16 2025, 1:57 AM

Aug 15 2025

rmacklem committed rG9cd3860c10b6: nfsd: Fix slow leaks of NAMEI buffers (authored by rmacklem).
nfsd: Fix slow leaks of NAMEI buffers
Aug 15 2025, 7:15 PM

Aug 13 2025

rmacklem committed rGef5e966e6e7c: RELNOTES: Make an entry for cce64f2e6851 (authored by rmacklem).
RELNOTES: Make an entry for cce64f2e6851
Aug 13 2025, 8:02 PM
rmacklem committed rGdb57584068f6: UPDATING: Make an entry for cce64f2e6851 (authored by rmacklem).
UPDATING: Make an entry for cce64f2e6851
Aug 13 2025, 7:55 PM
rmacklem committed rGcce64f2e6851: nfsv4: Add support for the NFSv4.2 Clone operation (authored by rmacklem).
nfsv4: Add support for the NFSv4.2 Clone operation
Aug 13 2025, 7:42 PM
rmacklem committed rGdec341af7695: pathconf.2: Add an entry for _PC_CLONE_BLKSIZE (authored by rmacklem).
pathconf.2: Add an entry for _PC_CLONE_BLKSIZE
Aug 13 2025, 3:09 PM
rmacklem closed D51851: pathconf.2: Add an entry for _PC_CLONE_BLKSIZE.
Aug 13 2025, 3:09 PM

Aug 12 2025

rmacklem updated the diff for D51851: pathconf.2: Add an entry for _PC_CLONE_BLKSIZE.

Reworded to mention copy_file_range.

Aug 12 2025, 9:00 PM

Aug 11 2025

rmacklem accepted D51856: tests: Add some regression tests for copy_file_range().

Looks good to me. Thanks for doing this, rick

Aug 11 2025, 3:23 PM

Aug 10 2025

rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
In D51808#1183889, @mav wrote:

So, unless you think there is a better answer than
vp->v_mount->mnt_stat.f_iosize,

If it is per-file-system, then this is probably the best you can get.

I think that will work.

I think it may matter only if client decide to clone file in several parts/requests. It may fail if the file appear having its block size bigger than f_iosize. It may be not very often, but possible.

(I will take a look at the block cloning code called from
zfs_copy_file_range() to see what it uses?)

Take a look at the beginning of zfs_clone_range(). It has a number of different constraints.

I did and from what I can see, they are exactly the constraints
that RFC7862 specifies for the NFSv4.2 CLONE operation.
(I suspect this all came from the way Linux does it?)

The one thing I have found is that zfs_clone_range() uses
z_blksz, which varies depending on the file's size.
(It is 512 for small files and 128K for bigger ones, for my
setup. mnt_stat.f_iosize is 128K.)

I am trying to find out if the NFSv4.2 clone_blksize
attribute is considered per-file or per-file-system.

Oh, and I might have found a bug in zfs_copy_file_range().
(It doesn't appear to advance the offsets when presented
as pointers and is not using f_offsets. I'll investigate further.)

The bug is in vn_copy_file_range() and not in the ZFS function.
For the case where the offset arguments are being passed in,
it doesn't update them properly.
I'll work on it, but it is not a bug in the ZFS code.

rick

This is getting interesting, rick

Aug 10 2025, 9:27 PM

Aug 9 2025

rmacklem committed rG4046ad6bb0ee: vfs_syscalls.c: Fix handling of offset args for copy_file_range (authored by rmacklem).
vfs_syscalls.c: Fix handling of offset args for copy_file_range
Aug 9 2025, 9:21 PM
rmacklem closed D51845: vfs_syscalls.c: Fix handling of offset arguments for copy_file_range.
Aug 9 2025, 9:21 PM
rmacklem added a comment to D51845: vfs_syscalls.c: Fix handling of offset arguments for copy_file_range.

The not so good news is that this bug made it out into 14.3.

I'll submit an EN since this is my bug (unless you'd really like to).

Aug 9 2025, 9:05 PM
rmacklem requested review of D51851: pathconf.2: Add an entry for _PC_CLONE_BLKSIZE.
Aug 9 2025, 8:48 PM
rmacklem committed rG7a9834041c91: vfs: Put the definition of COPY_FILE_RANGE_CLONE in unistd.h (authored by rmacklem).
vfs: Put the definition of COPY_FILE_RANGE_CLONE in unistd.h
Aug 9 2025, 8:37 PM
rmacklem closed D51838: vfs: Put the definition of COPY_FILE_RANGE_CLONE in an appropriate place.
Aug 9 2025, 8:37 PM
rmacklem requested review of D51845: vfs_syscalls.c: Fix handling of offset arguments for copy_file_range.
Aug 9 2025, 2:34 PM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
In D51808#1183889, @mav wrote:

So, unless you think there is a better answer than
vp->v_mount->mnt_stat.f_iosize,

If it is per-file-system, then this is probably the best you can get.

I think that will work.

I think it may matter only if client decide to clone file in several parts/requests. It may fail if the file appear having its block size bigger than f_iosize. It may be not very often, but possible.

(I will take a look at the block cloning code called from
zfs_copy_file_range() to see what it uses?)

Take a look at the beginning of zfs_clone_range(). It has a number of different constraints.

I did and from what I can see, they are exactly the constraints
that RFC7862 specifies for the NFSv4.2 CLONE operation.
(I suspect this all came from the way Linux does it?)

The one thing I have found is that zfs_clone_range() uses
z_blksz, which varies depending on the file's size.
(It is 512 for small files and 128K for bigger ones, for my
setup. mnt_stat.f_iosize is 128K.)

I am trying to find out if the NFSv4.2 clone_blksize
attribute is considered per-file or per-file-system.

Oh, and I might have found a bug in zfs_copy_file_range().
(It doesn't appear to advance the offsets when presented
as pointers and is not using f_offsets. I'll investigate further.)

The bug is in vn_copy_file_range() and not in the ZFS function.
For the case where the offset arguments are being passed in,
it doesn't update them properly.
I'll work on it, but it is not a bug in the ZFS code.

Aug 9 2025, 4:28 AM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
In D51808#1183889, @mav wrote:

So, unless you think there is a better answer than
vp->v_mount->mnt_stat.f_iosize,

If it is per-file-system, then this is probably the best you can get.

I think that will work.

I think it may matter only if client decide to clone file in several parts/requests. It may fail if the file appear having its block size bigger than f_iosize. It may be not very often, but possible.

(I will take a look at the block cloning code called from
zfs_copy_file_range() to see what it uses?)

Take a look at the beginning of zfs_clone_range(). It has a number of different constraints.

Aug 9 2025, 3:08 AM
rmacklem added inline comments to D51838: vfs: Put the definition of COPY_FILE_RANGE_CLONE in an appropriate place.
Aug 9 2025, 2:31 AM
rmacklem requested review of D51838: vfs: Put the definition of COPY_FILE_RANGE_CLONE in an appropriate place.
Aug 9 2025, 1:11 AM
rmacklem committed rG62fd20bde5a6: rpcsec_gss: Rename KRBIMP_HESIOD1 to KRBIMP_HEIMDALV1 (authored by rmacklem).
rpcsec_gss: Rename KRBIMP_HESIOD1 to KRBIMP_HEIMDALV1
Aug 9 2025, 12:35 AM

Aug 8 2025

rmacklem added a comment to D51812: gssd: Be consistent about Makefile conditionals.

Thanks for doing this. I was going to start looking at this
to-day, but I'm glad to see you've done it.

Aug 8 2025, 12:48 PM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
In D51808#1183580, @mav wrote:

The kernel had a ZFS patch that set _PC_CLONE_BLKSIZE correctly.

I am not sure what you mean with "correctly", but for a note, in ZFS different files might have different block sizes if created (grown beyond one block) during recordsize property was set to different values, or if the file is smaller than recordsize. Also the last block is predictably more flexible, but also with some limitations.

Aug 8 2025, 3:20 AM
rmacklem committed rG49eba35ce80d: RELNOTES: Add an entry for COPY_FILE_RANGE_CLONE (authored by rmacklem).
RELNOTES: Add an entry for COPY_FILE_RANGE_CLONE
Aug 8 2025, 1:15 AM
rmacklem committed rG37b2cb5ecb0f: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE (authored by rmacklem).
vfs: Add support for file cloning to VOP_COPY_FILE_RANGE
Aug 8 2025, 12:59 AM
rmacklem closed D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
Aug 8 2025, 12:59 AM

Aug 7 2025

rmacklem committed rG0080571ee0a5: RELNOTES: Make an entry for Solaris style extended attributes (authored by rmacklem).
RELNOTES: Make an entry for Solaris style extended attributes
Aug 7 2025, 10:46 PM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.

Here's a stupid question. Is it possible for nfsd to reexport an NFS mountpoint? If so, then nfs_copy_file_range will need to check the flag, too.

Not a stupid question. Linux allows this and they have endless bugs to deal
with because of it. FreeBSD does not and I hope to keep it that way.

Should we add the check anyway, just in case we ever add the FIONBCLONE (or whatever it's called) ioctl for userspace processes to use?

Aug 7 2025, 9:45 PM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.

Here's a stupid question. Is it possible for nfsd to reexport an NFS mountpoint? If so, then nfs_copy_file_range will need to check the flag, too.

Aug 7 2025, 9:37 PM
rmacklem updated the diff for D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.

Added check to fuse_copy_file_range() as pointed
out by asomers@.

Aug 7 2025, 9:36 PM
rmacklem added a comment to D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.

Shouldn't there also be some ZFS code that returns ENOSYS if the cloning requirement cannot be satisfied? And fuse_vnop_copy_file_range cannot ever satisfy that requirement, so it should return ENOSYS just like in vn_generic_copy_file_range

Aug 7 2025, 9:19 PM
rmacklem committed rG3a6c62e69597: named_attribute.7: Add an explanation for a quirk (authored by rmacklem).
named_attribute.7: Add an explanation for a quirk
Aug 7 2025, 9:16 PM
rmacklem closed D51751: named_attribute.7: Add an explanation for a quirk.
Aug 7 2025, 9:16 PM
rmacklem committed rGe3ac01e18eb3: kgssapi: Fix the kgssapi so that it can use MIT Kerberos (authored by rmacklem).
kgssapi: Fix the kgssapi so that it can use MIT Kerberos
Aug 7 2025, 9:06 PM
rmacklem requested review of D51808: vfs: Add support for file cloning to VOP_COPY_FILE_RANGE.
Aug 7 2025, 8:41 PM
rmacklem added a reverting change for rG554651ebf1c1: kgssapi: Fix the kgssapi so that it can use MIT Kerberos: rG4de9547f322b: Revert "kgssapi: Fix the kgssapi so that it can use MIT Kerberos".
Aug 7 2025, 12:07 AM
rmacklem committed rG4de9547f322b: Revert "kgssapi: Fix the kgssapi so that it can use MIT Kerberos" (authored by rmacklem).
Revert "kgssapi: Fix the kgssapi so that it can use MIT Kerberos"
Aug 7 2025, 12:07 AM
rmacklem added a reverting change for D51731: kgssapi: Fix the kgssapi so that it can use MIT Kerberos: rG4de9547f322b: Revert "kgssapi: Fix the kgssapi so that it can use MIT Kerberos".
Aug 7 2025, 12:07 AM
rmacklem committed rG1a10f2f2042e: Revert "gssd: Fix build for now" (authored by rmacklem).
Revert "gssd: Fix build for now"
Aug 7 2025, 12:04 AM
rmacklem added a reverting change for rG784069e172c5: gssd: Fix build for now: rG1a10f2f2042e: Revert "gssd: Fix build for now".
Aug 7 2025, 12:04 AM