committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|9685f363||behlendorf1||June 8, 2021, 3:59 a.m.||tests/file_check: remove unused variable|
|f423411c||behlendorf1||June 8, 2021, 3:58 a.m.||module/zfs: vdev_removal: spa_vdev_remove_thread: remove unused variable|
|6bab6ee8||behlendorf1||June 8, 2021, 3:58 a.m.||module/zfs: vdev_indirect: vdev_indirect_repair: remove unused variable|
|f70f3e2f||behlendorf1||June 8, 2021, 3:58 a.m.||module/zfs: dbuf: dbuf_read_impl: remove unused variable|
|f719d3b1||behlendorf1||June 8, 2021, 3:58 a.m.||module/zfs: arc: arc_hdr_realloc_crypt: remove unused variables|
|4ff49c5a||behlendorf1||June 8, 2021, 3:58 a.m.||libzfs: zfs_send: remove unused variable|
|4f1009fa||behlendorf1||June 8, 2021, 3:58 a.m.||zdb: zdb_decompress_block: don't needlessly set buf|
|77f3b675||behlendorf1||June 8, 2021, 3:58 a.m.||libzutil: zpool_find_config: remove unused variable|
|1b602f64||nc||June 7, 2021, 11:37 p.m.||linuxkpi: Fix build from redefined pr_err_once()|
|37d64dcd||nc||June 7, 2021, 10:53 p.m.||linuxkpi: Include pr_err_once() in printk.h|
|096104e7||nc||June 7, 2021, 10:53 p.m.||linuxkpi: Add rom and romlen to struct pci_dev|
|225605ec||emaste||June 7, 2021, 10:50 p.m.||Cirrus-CI: Use the default Git history depth
Which is `50`. I saw a few errors like `Failed to force reset to SHA: object not found!` which seems is happening because the SHA is not available because there were two commits pushed almost simultaneously and the second from the top fails with this error because the SHA is not in the history. Pull Request: https://github.com/freebsd/freebsd-src/pull/454 Comments on re-commit from emaste: Originally committed as fcb4797c90f3 and reverted in 80a840b8ba03 due to the clone operation taking significantly longer. However, I have seen many failures due to the "object not found" issue recently. 7 of 37 recent runs failed because of this, and intermittent failures like this makes CI much less useful. Prefer longer-running runs to intermittent failures.cgit
|03c81af2||rmacklem||June 7, 2021, 8:48 p.m.||nfscl: Fix generation of va_fsid for a tree of NFSv4 server file systems
Pre-r318997 the code looked like: if (vp->v_mount->mnt_stat.f_fsid.val != (uint32_t)np->n_vattr.na_filesid) vap->va_fsid = (uint32_t)np->n_vattr.na_filesid; Doing this assignment got lost by r318997 and, as such, NFSv4 mounts of servers with trees of file systems on the server is broken, due to duplicate fileno values for the same st_dev/va_fsid. Although I could have re-introduced the assignment, since the value of na_filesid is not guaranteed to be unique across the server file systems, I felt it was better to always do the hash for na_filesid[0,1]. Since dev_t (st_dev/va_fsid) is now 64bits, I switched to a 64bit hash. There is a slight chance of a hash conflict where 2 different na_filesid values map to same va_fsid, which will be documented in the BUGS section of the man page for mount_nfs(8). Using a table to keep track of mappings to catch conflicts would not easily scale to 10,000+ server file systems and, when the conflict occurs, it only results in fts(3) reporting a "directory cycle" under certain circumstances. Reviewed by: kib MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D30660cgit
|887c753c||markj||June 7, 2021, 8:45 p.m.||Fix handling of D_GIANTOK
It was meant to suppress only the printf(), not the subsequent injection of Giant-protected thunks for various file operations. Fixes: fbeb4ccac9 Reported by: pho Tested by: pho MFC after: 6 days Pointy hat: markjcgit
|2d815d95||noreply||June 7, 2021, 7:41 p.m.||Modernise/fix/rewrite unlinted manpages
zpool-destroy.8: flatten, fix description zfs-wait.8: flatten, fix description, use list for events zpool-reguid.8: flatten, fix description zpool-history.8: flatten, fix description zpool-export.8: flatten, fix description, remove -f "unmount" reference AFAICT no such command exists even in Illumos (as of today, anyway), and we definitely don't call it zpool-labelclear.8: flatten, fix description zpool-features.5: modernise spl-module-parameters.5: modernise zfs-mount-generator.8: rewrite zfs-module-parameters.5: modernise Reviewed-by: Richard Laager <email@example.com> Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Signed-off-by: Ahelenia Ziemiańska <email@example.com> Closes #12169cgit