diff options
Diffstat (limited to 'module/os/freebsd')
| -rw-r--r-- | module/os/freebsd/zfs/zfs_ctldir.c | 2 | ||||
| -rw-r--r-- | module/os/freebsd/zfs/zfs_dir.c | 6 | ||||
| -rw-r--r-- | module/os/freebsd/zfs/zfs_vfsops.c | 4 | ||||
| -rw-r--r-- | module/os/freebsd/zfs/zfs_vnops.c | 5 | ||||
| -rw-r--r-- | module/os/freebsd/zfs/zfs_znode.c | 8 | ||||
| -rw-r--r-- | module/os/freebsd/zfs/zio_crypt.c | 6 |
6 files changed, 16 insertions, 15 deletions
diff --git a/module/os/freebsd/zfs/zfs_ctldir.c b/module/os/freebsd/zfs/zfs_ctldir.c index ed6652c3b..fb0ffc082 100644 --- a/module/os/freebsd/zfs/zfs_ctldir.c +++ b/module/os/freebsd/zfs/zfs_ctldir.c @@ -107,7 +107,7 @@ typedef struct sfs_node { /* * Check the parent's ID as well as the node's to account for a chance - * that IDs originating from different domains (snapshot IDs, artifical + * that IDs originating from different domains (snapshot IDs, artificial * IDs, znode IDs) may clash. */ static int diff --git a/module/os/freebsd/zfs/zfs_dir.c b/module/os/freebsd/zfs/zfs_dir.c index 964033f8d..2c32602b1 100644 --- a/module/os/freebsd/zfs/zfs_dir.c +++ b/module/os/freebsd/zfs/zfs_dir.c @@ -61,7 +61,7 @@ #include <sys/dsl_dir.h> /* - * zfs_match_find() is used by zfs_dirent_lookup() to peform zap lookups + * zfs_match_find() is used by zfs_dirent_lookup() to perform zap lookups * of names after deciding which is the appropriate lookup interface. */ static int @@ -295,7 +295,7 @@ zfs_unlinked_drain(zfsvfs_t *zfsvfs) int error; /* - * Interate over the contents of the unlinked set. + * Iterate over the contents of the unlinked set. */ for (zap_cursor_init(&zc, zfsvfs->z_os, zfsvfs->z_unlinkedobj); zap_cursor_retrieve(&zc, &zap) == 0; @@ -508,7 +508,7 @@ zfs_rmnode(znode_t *zp) } /* - * FreeBSD's implemention of zfs_zget requires a vnode to back it. + * FreeBSD's implementation of zfs_zget requires a vnode to back it. * This means that we could end up calling into getnewvnode while * calling zfs_rmnode as a result of a prior call to getnewvnode * trying to clear vnodes out of the cache. If this repeats we can diff --git a/module/os/freebsd/zfs/zfs_vfsops.c b/module/os/freebsd/zfs/zfs_vfsops.c index 317773e44..8a7626c86 100644 --- a/module/os/freebsd/zfs/zfs_vfsops.c +++ b/module/os/freebsd/zfs/zfs_vfsops.c @@ -1746,7 +1746,7 @@ zfsvfs_teardown(zfsvfs_t *zfsvfs, boolean_t unmounting) /* * At this point there are no vops active, and any new vops will * fail with EIO since we have z_teardown_lock for writer (only - * relavent for forced unmount). + * relevant for forced unmount). * * Release all holds on dbufs. */ @@ -2407,7 +2407,7 @@ zfs_get_zplprop(objset_t *os, zfs_prop_t prop, uint64_t *value) } /* - * Return true if the coresponding vfs's unmounted flag is set. + * Return true if the corresponding vfs's unmounted flag is set. * Otherwise return false. * If this function returns true we know VFS unmount has been initiated. */ diff --git a/module/os/freebsd/zfs/zfs_vnops.c b/module/os/freebsd/zfs/zfs_vnops.c index ff842afb0..ca23026be 100644 --- a/module/os/freebsd/zfs/zfs_vnops.c +++ b/module/os/freebsd/zfs/zfs_vnops.c @@ -385,7 +385,8 @@ page_busy(vnode_t *vp, int64_t start, int64_t off, int64_t nbytes) * aligned boundaries, if the range is not aligned. As a result a * DEV_BSIZE subrange with partially dirty data may get marked as clean. * It may happen that all DEV_BSIZE subranges are marked clean and thus - * the whole page would be considred clean despite have some dirty data. + * the whole page would be considered clean despite have some + * dirty data. * For this reason we should shrink the range to DEV_BSIZE aligned * boundaries before calling vm_page_clear_dirty. */ @@ -1139,7 +1140,7 @@ zfs_write(vnode_t *vp, uio_t *uio, int ioflag, cred_t *cr) /* * Clear Set-UID/Set-GID bits on successful write if not - * privileged and at least one of the excute bits is set. + * privileged and at least one of the execute bits is set. * * It would be nice to to this after all writes have * been done, but that would still expose the ISUID/ISGID diff --git a/module/os/freebsd/zfs/zfs_znode.c b/module/os/freebsd/zfs/zfs_znode.c index b9d5472b2..e2f941415 100644 --- a/module/os/freebsd/zfs/zfs_znode.c +++ b/module/os/freebsd/zfs/zfs_znode.c @@ -328,7 +328,7 @@ zfs_vnode_forget(vnode_t *vp) } /* - * Construct a new znode/vnode and intialize. + * Construct a new znode/vnode and initialize. * * This does not do a call to dmu_set_user() that is * up to the caller to do, in case you don't want to @@ -604,7 +604,7 @@ zfs_mknode(znode_t *dzp, vattr_t *vap, dmu_tx_t *tx, cred_t *cr, pflags |= ZFS_XATTR; /* - * No execs denied will be deterimed when zfs_mode_compute() is called. + * No execs denied will be determined when zfs_mode_compute() is called. */ pflags |= acl_ids->z_aclp->z_hints & (ZFS_ACL_TRIVIAL|ZFS_INHERIT_ACE|ZFS_ACL_AUTO_INHERIT| @@ -938,7 +938,7 @@ again: * But that is only possible if the other thread peforms * a ZFS vnode operation on the vnode. That either * should not happen if the vnode is dead or the thread - * should also have a refrence to the vnode and thus + * should also have a reference to the vnode and thus * our reference is not last. */ VN_RELE(vp); @@ -1099,7 +1099,7 @@ zfs_rezget(znode_t *zp) * If the file has zero links, then it has been unlinked on the send * side and it must be in the received unlinked set. * We call zfs_znode_dmu_fini() now to prevent any accesses to the - * stale data and to prevent automatical removal of the file in + * stale data and to prevent automatically removal of the file in * zfs_zinactive(). The file will be removed either when it is removed * on the send side and the next incremental stream is received or * when the unlinked set gets processed. diff --git a/module/os/freebsd/zfs/zio_crypt.c b/module/os/freebsd/zfs/zio_crypt.c index d6496a7ef..d89ef80ed 100644 --- a/module/os/freebsd/zfs/zio_crypt.c +++ b/module/os/freebsd/zfs/zio_crypt.c @@ -389,7 +389,7 @@ int failed_decrypt_size; * plaintext / ciphertext alone. */ /* - * The implemenation for FreeBSD's OpenCrypto. + * The implementation for FreeBSD's OpenCrypto. * * The big difference between ICP and FOC is that FOC uses a single * buffer for input and output. This means that (for AES-GCM, the @@ -1229,9 +1229,9 @@ zio_crypt_do_indirect_mac_checksum_abd(boolean_t generate, abd_t *abd, * the zil_chain_t header. Everything that is not encrypted is authenticated. */ /* - * The OpenCrypto used in FreeBSD does not use seperate source and + * The OpenCrypto used in FreeBSD does not use separate source and * destination buffers; instead, the same buffer is used. Further, to - * accomodate some of the drivers, the authbuf needs to be logically before + * accommodate some of the drivers, the authbuf needs to be logically before * the data. This means that we need to copy the source to the destination, * and set up an extra iovec_t at the beginning to handle the authbuf. * It also means we'll only return one uio_t, which we do via the clumsy |