summaryrefslogtreecommitdiffstats
path: root/gnu/llvm/unittests/Bitcode/BitReaderTest.cpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-04-06Use the existing pf state to speed up UDP socket lookup. This wasbluhm1-2/+2
disabled as there were some stability issues. It seems that the crashes were fixed when reference counting for pf states was implemented. Se reenable this code. Apart from the performance improvement it also makes corner cases for pf divert-to more reliable. OK henning@
2018-04-06Retain the UF_PLEDGED flag from the original fd during dup(2).bluhm1-2/+2
Nothing uses this fd-tracking part of pledge yet. OK deraadt@
2018-04-06All users of the PFLOG_PACKET() macro are inside "#if NPFLOG > 0".bluhm2-12/+7
So this macro does not make much sense, just call pflog_packet(). OK sashan@ henning@
2018-04-06Avoid leaking str if EVP_Digest() fails.tb1-3/+6
Found and fixed by Bernd Edlinger as part of OpenSSL commit 83b4049ab75e9da1815e9c854a9297bca3d4af6b ok jsing, deraadt, bcook
2018-04-06Fix link, from Eliran Gonen.nicm1-2/+2
2018-04-06poison for X509_VERIFY_PARAM'sbeck4-45/+107
Tighten up checks for various X509_VERIFY_PARAM functions, and allow for the verify param to be poisoned (preculding future successful cert validation) if the setting of host, ip, or email for certificate validation fails. (since many callers do not check the return code in the wild and blunder along anyway) Inspired by some discussions with Adam Langley. ok jsing@
2018-04-06Add test for username options parsing order, prompted by bz#2849.dtucker1-1/+12
2018-04-06relax checking of authorized_keys environment="..." options to allowdjm1-2/+2
underscores in variable names (regression introduced in 7.7). bz2851, ok deraadt@
2018-04-06add a couple of missed options to the config dump; patch fromdjm1-1/+9
Jakub Jelen via bz2835
2018-04-06ssh does not accept -oInclude=... on the commandline, the Include keyworddjm1-3/+2
is for configuration files only. bz#2840, patch from Jakub Jelen
2018-04-05We don't offer CBC cipher by default any more. Spotted by Renauddjm1-4/+3
Allard (via otto@)
2018-04-05Stop documenting the non-portable .R man(7) macro. Neither groffschwarze1-17/+4
nor the heirloom-doctools support it. Adding it was a mistake in the first place.
2018-04-05Do not use a non-portable .R man(7) macro. Neither groff nor theschwarze1-2/+2
heirloom-doctools support it. Work around the gap by using .BR with an empty first argument. This was noticed more than once in the past, but i always forgot to fix it.
2018-04-05Add more initialization code such that things work with the EDK2-basedkettenis1-31/+196
UEFI firmware as well.
2018-04-05syncderaadt1-1/+1
2018-04-05use the portable \(lq and \(rq internally rather than \(Lq and \(Rqschwarze3-50/+50
2018-04-05For .Do/.Dq, use the documented and portable \(lq and \(rqschwarze1-3/+3
character escape sequences rather than the undocumented and non-portable \(Lq and \(Rq. Bug reported by Tim L <darkxst at github> via Thomas Klausner <wiz at NetBSD>; see https://github.com/nih-at/libzip/pull/42
2018-04-05Import pcap_set_immediate_mode() from mainline libpcap which allows alteo6-7/+39
libpcap-based program to process packets as soon as they arrive. feedback from jasper@ ok jca@ (a long time ago)
2018-04-05Zap the obsolete PF_TRANS_ALTQ.lteo1-2/+2
Note: Remember to "make includes" and recompile the following programs together with the kernel: sbin/pfctl usr.sbin/authpf usr.sbin/ftp-proxy usr.sbin/relayd usr.sbin/tftp-proxy Thanks to sthen@ for checking the ports tree. ok bluhm@ sashan@ visa@
2018-04-05Explicitly check PF_TRANS_RULESET in DIOCXBEGIN, DIOCXCOMMIT, and DIOCXROLLBACK.lteo1-5/+29
ok bluhm@ sashan@ visa@
2018-04-05typo in printf - was _PRO, should be _PR0mlarkin1-3/+3
ok kettenis
2018-04-04syncderaadt2-0/+6
2018-04-04Update default IPQoS in ssh(1), sshd(8) to DSCP AF21 for interactive and CS1 for bulkjob4-14/+18
AF21 was selected as this is the highest priority within the low-latency service class (and it is higher than what we have today). SSH is elastic and time-sensitive data, where a user is waiting for a response via the network in order to continue with a task at hand. As such, these flows should be considered foreground traffic, with delays or drops to such traffic directly impacting user-productivity. For bulk SSH traffic, the CS1 "Lower Effort" marker was chosen to enable networks implementing a scavanger/lower-than-best effort class to discriminate scp(1) below normal activities, such as web surfing. In general this type of bulk SSH traffic is a background activity. An advantage of using "AF21" for interactive SSH and "CS1" for bulk SSH is that they are recognisable values on all common platforms (IANA https://www.iana.org/assignments/dscp-registry/dscp-registry.xml), and for AF21 specifically a definition of the intended behavior exists https://tools.ietf.org/html/rfc4594#section-4.7 in addition to the definition of the Assured Forwarding PHB group https://tools.ietf.org/html/rfc2597, and for CS1 (Lower Effort) there is https://tools.ietf.org/html/rfc3662 The first three bits of "AF21" map to the equivalent IEEEE 802.1D PCP, IEEE 802.11e, MPLS EXP/CoS and IP Precedence value of 2 (also known as "Immediate", or "AC_BE"), and CS1's first 3 bits map to IEEEE 802.1D PCP, IEEE 802.11e, MPLS/CoS and IP Precedence value 1 ("Background" or "AC_BK"). OK deraadt@, "no objection" djm@
2018-04-04mention which locale categories this is related to, and add SEE ALSOschwarze1-1/+11
2018-04-04add SEE ALSOschwarze1-1/+6
2018-04-04Split the useless localeconv(3) function out of the importantschwarze3-145/+195
setlocale(3) manual page, such that the latter becomes easier to read. No text change.
2018-04-04adapt armv7 manual pages for arm64jsg7-3/+229
2018-04-04Fix two bugs in X509_NAME_add_entry(3):schwarze1-7/+4
(1) Evaluate the "set" argument, which says whether to create a new RDN or to prepend or append to an existing one, before reusing it for a different purpose, i.e. for the "set" field of the new X509_NAME_ENTRY structure. (2) When incrementing of some "set" fields is needed, increment the correct ones: All those to the right of the newly inserted entry, but not the one of that entry itself. These two bugs caused wrong results whenever using loc != -1, i.e. whenever inserting rather than appending entries, even when using set == 0 only, that is, even when using single-values RDNs only. Both bugs have been continuously present since at least SSLeay-0.8.1 (released July 18, 1997) and the second one since at least SSLeay-0.8.0 (released June 25, 1997), so both are over twenty years old. I found these bugs by code inspection while trying to document the function X509_NAME_ENTRY_set(3), which is public, but undocumented in OpenSSL. OK beck@, jsing@
2018-04-04TEST_LOG is owned by bsd.port.mk, actuallyespie1-2/+3
okay jca@
2018-04-03KNF: move two opening curly braces of function bodies to their own linestb2-4/+6
2018-04-03Typo: typdef -> typedef.tb1-3/+3
From Edgar Pettijohn
2018-04-03syncderaadt1-1/+1
2018-04-03Add missing $OpenBSD$ tags.tb2-0/+2
2018-04-03Fix crash in dig(1) +trace when falling back to TCP after a truncated replyjca1-1/+4
Problem reported by jj@ on bugs@, fix based on https://gitlab.isc.org/isc-projects/bind9/commit/084ba95b083dc55fd10631ad43fa8fff48707648 (under ISC license) by Caspar Schutijser.
2018-04-03regenkettenis2-2/+7
2018-04-03Add Marvell ARMADA 7K/8K (CP110) Root Complex.kettenis1-1/+2
2018-04-03Match on the more specific "marvell,armada8k-pcie" instead of the generickettenis1-2/+2
"snps,dw-pcie" for now. There are considerable variations between implementations of the Synapsys Designware PCIe core and glue logic and the current code isn't flexible enough to deal with that yet.
2018-04-03Move FREF()s just after fd_getfile() in sys_kevent(), sys_lseek() andmpi2-13/+20
getvnode(). ok millert@
2018-04-03Add proper FREF()/FRELE() dance in sys_fchdir().mpi1-2/+6
The syscall doesn't sleep before a vnode reference is taken, so it doesn't stickly need the refcounts now. But they will be soon be used for parrallelism, so make it ready. ok bluhm@
2018-04-03Call FREF() right after fd_getfile() in dodup3().mpi1-3/+6
ok millert@, bluhm@
2018-04-03Silence assertwaitok() if we are in ddb(4).mpi1-1/+4
ok bluhm@
2018-04-03Deactivate witness(4) checks if we are in ddb(4), when `db_active' is set.mpi1-17/+24
Prevents witness(4) from panic'ing the kernel now that mutexes and rwlock are always "taken" while in ddb(4). ok visa@
2018-04-03remove a 15-year old #if 0mlarkin1-4/+1
2018-04-03mention i.MX 8jsg1-3/+3
2018-04-03document the use of llprio for tranmistted packets with link0dlg1-3/+17
2018-04-03fec moved from arch/armv7 to dev/fdtjsg3-6/+6
2018-04-03use link0 to use llprio in transmitted packets, regardless of mbuf prio.dlg1-2/+3
some ISPs now provide services over vlans, but require vlan packets going to the internet have their priority set to 1 (ie, 0 on the wire) or they will be dropped. configuring this on openbsd requires config in several places, eg, pf rules to set the prio on ip packets, llprio on the pppoe interface for it's management frames, and the llprio on the vlan interface if you're using dhclient on it. this has the side effect that you can no longer use priority queuing, and can be error prone to get right. using link0 to flatteng the priority for isp transit is simple to configure, and allows priority queuing. a man page update is coming. ok henning@
2018-04-03Import regenerated moduli file.dtucker7-811/+873
2018-04-03tweak vlan printing to properly decode the priority field.dlg1-5/+13
the vlan specs have the priority of 0 and 1 swapped on the wire, which is how the kernel handles them. eg, if you use pf to set prio 1, it will end up being 0 on the wire. this makes 0 on the wire come out as 1 in tcpdump so it is consistent with the rest of the tooling. ok henning@
2018-04-03syncderaadt2-0/+3