committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r342769||kib||Jan. 4, 2019, 5:33 p.m.||i386: Use atomic 64bit load to read PDE value from PAE pagetables in
pmap_kextract(). pmap_kextract() can race with promotion/demotion on the kernel page table, in which case current non-atomic 64bit read would see torn value, breaking pmap_kextract(). pmap_kextract() would correctly handle either promoted or demoted PDE, but not a mix where one word is from a different state. It requires PAE and > 4G memory to reproduce. We observed this in real loads, both for intensive use of malloc(9)/free(9) where vtoslab() returned invalid pointer to the slab, and with the use of busdma_bounce, where incorrect page was bounced. In collaboration with: pho Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D18714ViewVC
|r342768||markj||Jan. 4, 2019, 5:31 p.m.||Support MSG_DONTWAIT in send*(2).
As it does for recv*(2), MSG_DONTWAIT indicates that the call should not block, returning EAGAIN instead. Linux and OpenBSD both implement this, so the change makes porting easier, especially since we do not return EINVAL or so when unrecognized flags are specified. Submitted by: Greg V <email@example.com> Reviewed by: tuexen MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D18728ViewVC
|r342767||kib||Jan. 4, 2019, 5:25 p.m.||x86: Report per-cpu IPI TLB shootdown generation in ddb 'show pcpu' output.
It is useful for inspecting tlb shootdown hangs. The smp_tlb_generation value is available using regular ddb data inspection commands. Sponsored by: The FreeBSD Foundation MFC after: 3 daysViewVC
|r342766||markj||Jan. 4, 2019, 5:14 p.m.||Don't enable interrupts in init_secondary().
The MI kernel assumes that interrupts will not be enabled on APs until after the first context switch. In particular, the problem was causing occasional deadlocks during boot. Remove an unneeded intr_disable() added in r335005. Reviewed by: jhb (previous version) MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D18738ViewVC
|r342765||markj||Jan. 4, 2019, 5:10 p.m.||Fix dirty bit handling in pmap_remove_write().|
|r342764||markj||Jan. 4, 2019, 5:08 p.m.||Clear PGA_WRITEABLE in pmap_remove_pages().|
|r342763||emaste||Jan. 4, 2019, 4:47 p.m.||newvers: retire p4 version support
Perforce no longer offers a FreeBSD client and it not a viable VCS for FreeBSD development. Remove p4 version logic to simplify newvers.sh in advance of other changes. Sponsored by: The FreeBSD FoundationViewVC
|r342762||chuck||Jan. 4, 2019, 3:03 p.m.||Fix bhyve's NVMe Completion Queue entry values
The function which processes Admin commands was not returning the Command Specific value in Completion Queue Entry, Dword 0 (CDW0). This effects commands such as Set Features, Number of Queues which returns the number of queues supported by the device in CDW0. In this case, the host will only create 1 queue pair (Number of Queues is zero based). This also masked a bug in the queue counting logic. Reviewed by: imp, araujo Approved by: imp (mentor) MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D18703ViewVC
|r342761||chuck||Jan. 4, 2019, 3:03 p.m.||Fix bhyve's NVMe queue bookkeeping
Many size / length parameters in NVMe are "0's based", meaning, a value of 0x0 represents 1, 0x1 represents 2, etc.. While this leads to an efficient encoding, it can lead to subtle bugs. With respect to queues, these parameters include: - Maximum number of queue entries - Maximum number of queues - Number of Completion Queues - Number of Submission Queues To be consistent, convert all 0's based values from the host to 1's based value internally. Likewise, covert internal 1's based values to 0's based values when returned to the host. This fixes an off-by-one bug when creating IO queues and simplifies some of the code. Note that this bug is masked by another bug. While in the neighborhood, - fix an erroneous queue ID check (checking CQ count when deleting SQ) - check for queue ID of 0x0 in a few places where this is illegal - clean up the Set Features, Number of Queues command and check for illegal values Reviewed by: imp, araujo Approved by: imp (mentor) MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D18702ViewVC
|r342760||emaste||Jan. 4, 2019, 2:42 p.m.||newvers: avoid clearing svn revision information with nested VCS dirs
Consider the case where FreeBSD is checked out via Subversion with a (perhaps unrelated) .git or .hg directory at a higher level - for example, .../.git .../src/freebsd Previously newvers obtained the SVN revision information via svnversion, and then tried to obtain the SVN revision corresponding to the git or hg commit, overwriting the existing information. As a short term fix use a different variable for hg-svn or git-svn information, setting $svn from hg or git info only if not empty. Reported by: Matthias Apitz Sponsored by: The FreeBSD FoundationViewVC
|r342759||avos||Jan. 4, 2019, 4:26 a.m.||rtwn_pci(4): sync r88ee_power_on() with OpenBSD|
|r342758||np||Jan. 4, 2019, 4:15 a.m.||cxgbe(4): Clear FW_OK if the firmware reports an error.
Sponsored by: Chelsio CommunicationsViewVC
|r342757||kevans||Jan. 4, 2019, 3:13 a.m.||getopt_long(3): fix case of malformed long opt
When presented with an arg string like '-l-', getopt_long will successfully parse out the 'l' short option, then proceed to match '--' against the first longopts entry as it later does a strncmp with len=0. This latter bit is arguably another bug in itself, but presumably not a practical issue as all callers of parse_long_options are already doing the right thing (except this one pointed out). An opt string like '-l-' should be considered malformed and throw a bad argument rather than behaving as if '--' were passed. It cannot possibly do what the invoker expects, and it's probably the result of a typo (ls -l- a) rather than any intent. Reported by: Tony Overfield <firstname.lastname@example.org> Reviewed by: imp MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D18616ViewVC
|r342754||allanjude||Jan. 4, 2019, 2:48 a.m.||The lam(1) man page is unclear about the uppercase versions of the flags|
|r342749||mmacy||Jan. 3, 2019, 11:06 p.m.||mp_ring: avoid items offset difference between iflib and mp_ring|