summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MFC r306610:sevan2016-10-101-28/+44
| | | | | | | | | | Note mount_fusefs appeared in FreeBSD 10. Move note regarding implementation to caveats. Address issued raised by Igor. PR: 212513 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306607:sevan2016-10-101-2/+2
| | | | | | | | mksnap_ffs appeared in FreeBSD 5.1. PR: 212510 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306606:sevan2016-10-101-2/+2
| | | | | | | | | mknod appeared in V4 UNIX http://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man8/mknod.8 PR: 212509 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306605:sevan2016-10-101-2/+2
| | | | | | | | | init was there in UNIX from V1 http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/init.s PR: 212503 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306604:sevan2016-10-101-1/+4
| | | | | | | | gbde first appeared in FreeBSD 5.0 PR: 212478 Approved by: brc (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306603:sevan2016-10-101-8/+9
| | | | | | | | | Document which version of BSD first showed up in and add the version info for NetBSD & FreeBSD. PR: 212477 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306602:sevan2016-10-101-2/+5
| | | | | | | | Mention the version of NetBSD the utility originated from. PR: 212476 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306601:sevan2016-10-101-2/+2
| | | | | | | | | dumpon(8) appears to be present in FreeBSD 2.0.5, despite initial import of man page listed FreeBSD 2.1. PR: 212445 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306600:sevan2016-10-101-2/+2
| | | | | | | | | | dump(8) first appeared in V4 UNIX http://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/man/man8 PR: 212444 Approved by: bcr (mentor) Obtained from: TUHS Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306598sevan2016-10-101-3/+3
| | | | | | | | | | | | | | ccdconfig first appeared in NetBSD 1.1 From NetBSD man page, confirmed with repo tags in CVS [1] (there was also no 1.0a release according to [2]) [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/sbin/ccdconfig/ccdconfig.c [2] http://netbsd.org/releases/formal.html#history PR: 212437 Approved by: bcr (mentor) Obtained from: NetBSD Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306582:sevan2016-10-101-6/+5
| | | | | | | | | | "POSIX doesn't specify -h." - r1.27 from NetBSD http://man.openbsd.org/?query=chmod&apropos=0&sec=0&arch=default&manpath=POSIX-2013 PR: 212337 Approved by: bcr (mentor) Obtained from: NetBSD Differential Revision: https://reviews.freebsd.org/D8118
* MFC r306581:sevan2016-10-101-2/+2
| | | | | | | | Use .At macro instead of specifying AT&T UNIX literaly. PR: 212034 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8114
* MFC r306714:sevan2016-10-101-1/+9
| | | | | | | | | Document where chio(1) originated from & which version of FreeBSD first included it. PR: 211776 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8104
* MFC r306584:sevan2016-10-101-5/+7
| | | | | | | | | | | Move the description of CHANGER variable to ENVIRONMENT section rather than in the DESCRIPTION section. From OpenBSD src/bin/chio/chio.1 r1.23 PR: 212158 Approved by: bjk Obtained from: OpenBSD Differential Revision: https://reviews.freebsd.org/D8117
* MFC: r306318tijl2016-10-101-1/+1
| | | | | | | | | | | | Allocate a zeroed LDT. Failing to do this might result in the LDT appearing to run out of free descriptors because of random junk in the descriptor's 'sd_type' field. http://lists.freebsd.org/pipermail/freebsd-amd64/2014-May/016088.html PR: 212639 Submitted by: wheelcomplex@gmail.com
* MFC r306478:hselasky2016-10-102-5/+7
| | | | | | | | | Add new USB ID. While at it remove some whitespaces. Submitted by: Jose Luis Duran <jlduran@gmail.com> PR: 213110
* MFC r306454:hselasky2016-10-101-0/+1
| | | | | | | Set hardware stats flag to avoid double counting the number of incoming bytes. Found by: Ben RUBSON <ben.rubson@gmail.com> Sponsored by: Mellanox Technologies
* MFC r306453:hselasky2016-10-101-0/+1
| | | | | | | Set hardware stats flag to avoid double counting the number of incoming bytes. Found by: Ben RUBSON <ben.rubson@gmail.com> Sponsored by: Mellanox Technologies
* MFC r306451:hselasky2016-10-101-9/+20
| | | | | | | | The IORESOURCE_XXX defines should resemble a bitmask while SYS_RES_XXX are not bitmasks. Fix return value of pci_resource_flags() to reflect this change. Sponsored by: Mellanox Technologies
* MFC r306441 and r306634:hselasky2016-10-102-1/+24
| | | | | | | | | | | | | | | | | | | | | | | While draining a timeout task prevent the taskqueue_enqueue_timeout() function from restarting the timer. Commonly taskqueue_enqueue_timeout() is called from within the task function itself without any checks for teardown. Then it can happen the timer stays active after the return of taskqueue_drain_timeout(), because the timeout and task is drained separately. This patch factors out the teardown flag into the timeout task itself, allowing existing code to stay as-is instead of applying a teardown flag to each and every of the timeout task consumers. Add assert to taskqueue_drain_timeout() which prevents parallel execution on the same timeout task. Update manual page documenting the return value of taskqueue_enqueue_timeout(). Differential Revision: https://reviews.freebsd.org/D8012 Reviewed by: kib, trasz
* While the thread is sleeping in taskqueue_drain_all() it isjulian2016-10-101-3/+20
| | | | | | | | | | posible that the queue entry it is looking at is removed from the queue, but we make no effort to account for this. when we wake up we need to check it's still there. PR: 209580 Sponsored by: Panzura inc Differential Revision: D8160
* MFC r306443:jch2016-10-091-1/+3
| | | | | | | | | | | | | | | | | Fix an issue with accept_filter introduced with r261242: As a side effect of r261242 when using accept_filter the first call to soisconnected() is done earlier in tcp_input() instead of tcp_do_segment() context. Restore the expected behaviour. Note: This call to soisconnected() seems to be extraneous in all cases (with or without accept_filter). Will be addressed in a separate commit. PR: 212920 Reported by: Alexey Tested by: Alexey, jch Sponsored by: Verisign, Inc.
* MFC r297314: rc.d: Make msgs a proper rc.d script.jilles2016-10-091-5/+17
| | | | | PR: 207149 Reported by: Jonathan de Boyne Pollard
* MFC r306560, r306561:pfg2016-10-091-4/+3
| | | | | | | | | patch(1): make some macros look boolean. Minor cleanup inspired by a new patch(1) variant in schily tools. For reference: https://sourceforge.net/p/schillix-on/
* MFC r305812:pfg2016-10-094-5/+5
| | | | | | | | | fifolog(1): invert order of calloc(3) arguments. The second argument to calloc(3) should be the size, make it so. While here be a little bit more cautious in fifolog_reader_open() to protect in the unlikely event of an overflowed allocation.
* MFC r306599:sevan2016-10-081-2/+2
| | | | | | | | | | dmesg(8) first appeared in 3BSD. http://minnie.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/man/man1/dmesg.1m PR: 212443 Approved by: bcr (mentor) Obtained from: TUHS Differential Revision: https://reviews.freebsd.org/D8105
* MFC r306568, r306569vangyzen2016-10-081-2/+2
| | | | | | | Add the __printflike attribute to the declarations of dprintf(3) and vdprintf(3). Sponsored by: Dell EMC
* MFH: r259647julian2016-10-073-18/+21
| | | | | | | | | | | | o Remove assertions on ipa_version as sometimes the version detection using cpuid can be quirky (this is the case of VMWare without the vPMC support) but fail to probe hwpmc. o Apply the fix for XEON family of processors as established by 315338-020 document (bug AJ85). Sponsored by: EMC / Isilon storage division Reviewed by: fabient MFC courtesy of panzura.
* MFC r306292: fix vnode lock assertion for extended attributes directoryavg2016-10-071-3/+8
|
* MFC r306291: the rest of changes intended to be committed in r306290avg2016-10-071-2/+5
|
* MFC r306218,306290: amdsbwd, intpm: unify bits specific to AMD chipsetsavg2016-10-074-115/+212
|
* MFC r299199: Add nid_namelen bounds check to nfssvc system callemaste2016-10-071-0/+4
| | | | | | | | This is only allowed by root and only used by the nfs daemon, which should not provide an incorrect value. However, it's still good practice to validate data provided by userland. PR: 206626
* MFC r306674:kib2016-10-071-3/+2
| | | | Style.
* MFC r296454:jtl2016-10-071-14/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some cleanup in tcp_respond() in preparation for another change: - Reorder variables by size - Move initializer closer to where it is used - Remove unneeded variable MFC r296455: As reported on the transport@ and current@ mailing lists, the FreeBSD TCP stack is not compliant with RFC 7323, which requires that TCP stacks send a timestamp option on all packets (except, optionally, RSTs) after the session is established. This patch adds that support. It also adds a TCP signature option to the packet, if appropriate. MFC r300764 (by jhb@): Don't reuse the source mbuf in tcp_respond() if it is not writable. Not all mbufs passed up from device drivers are M_WRITABLE(). In particular, the Chelsio T4/T5 driver uses a feature called "buffer packing" to receive multiple frames in a single receive buffer. The mbufs to receive multiple frames in a single receive buffer. The mbufs for these frames all share the same external storage so are treated as read-only by the rest of the stack when multiple frames are in flight. Previously tcp_respond() would blindly overwrite read-only mbufs when INVARIANTS was disabled or panic with an assertion failure if INVARIANTS was enabled. Note that the new case is a bit of a mix of the two other cases in tcp_respond(). The TCP and IP headers must be copied explicitly into the new mbuf instead of being inherited (similar to the m == NULL case), but the addresses and ports must be swapped in the reply (similar to the m != NULL case).
* MFC r306528: Fix `sesutil fault` operation.mav2016-10-071-3/+9
| | | | | Fault and ident bits are located in different control bytes, so previous code was just doing nothing, writing into reserved bit.
* MFC 302859: Include command line arguments in core dump process info.jhb2016-10-062-8/+56
| | | | | Fill in pr_psargs in the NT_PRSINFO ELF core dump note with command line arguments.
* MFC 299458: Fix buffer overrun in gcore(1) NT_PRPSINFOjhb2016-10-061-2/+2
| | | | | | | | | Use size of destination buffer, rather than a constant that may or may not correspond to the source buffer, to restrict the length of copied strings. In particular, pr_fname has 16+1 characters but MAXCOMLEN is 18+1. Use strlcpy instead of strncpy to ensure the result is nul-terminated. This seems to be what is expected of these fields.
* MFC r306522davidcs2016-10-064-150078/+150210
| | | | Upgrade Firmware/Bootloader/ResetSeq/Minidump to revision 5.4.62
* MFC r306279: Use g_wither_provider() where applicable.mav2016-10-0612-23/+14
| | | | | It is just a helper function combining G_PF_WITHER setting with g_orphan_provider().
* Fix ABI compat shims for FreeBSD 9.0-9.1 binaries (CAM_VERSION 0x16).mav2016-10-062-17/+17
| | | | | This is a direct commit to stable/10, inspired by some commits to later branches.
* MFC r306417: portsnap: only move expected snapshot contents from snap/ to files/emaste2016-10-051-0/+7
| | | | | | | | | | Previously it was possible to smuggle in addional files that would be used by later portsnap runs. Now we only move those files expected to be in the snapshot into files/ and require that there are no unexpected files. This was used by portsnap attacks 2, 3, and 4 in the "non-cryptanalytic attacks against FreeBSD update components" anonymous gist.
* Revert r306659 since the userland changes won't merge and this wouldrmacklem2016-10-0314-439/+196
| | | | break the build.
* MFC: r304026rmacklem2016-10-0314-196/+439
| | | | | | | | | | | | Update the nfsstats structure to include the changes needed by the patch in D1626 plus changes so that it includes counts for NFSv4.1 (and the draft of NFSv4.2). Also, make all the counts uint64_t and add a vers field at the beginning, so that future revisions can easily be implemented. There is code in place to handle the old vesion of the nfsstats structure for backwards binary compatibility. Subsequent commits will update nfsstat(8) to use the new fields.
* MFC r306048asomers2016-10-032-2/+2
| | | | | | | | | | | Fix periodic scripts when an NFS mount covers a local mount 100.chksetuid and 110.neggrpperm try to search through all UFS and ZFS filesystems. But their logic contains an error. They also search through remote filesystems that are mounted on top of the root of a local filesystem. For example, if a user installs a FreeBSD system with the default ZFS layout, he'll get a zroot/usr/home filesystem. If he then mounts /usr/home over NFS, these scripts would search through /usr/home.
* MFC r305977:kib2016-10-032-9/+18
| | | | Be more strict when selecting between snapshot/regular mount.
* MFC r306334:kib2016-10-033-0/+244
| | | | | | | Document thr_suspend(2) and thr_wake(2). MFC r306506: Reword the statement.
* MFC r306289:kp2016-10-021-31/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | bridge: Fix fragment handling and memory leak Fragmented UDP and ICMP packets were corrupted if a firewall with reassembling feature (like pf'scrub) is enabled on the bridge. This patch fixes corrupted packet problem and the panic (triggered easly with low RAM) as explain in PR 185633. bridge_pfil and bridge_fragment relationship: bridge_pfil() receive (IN direction) packets and sent it to the firewall The firewall can be configured for reassembling fragmented packet (like pf'scrubing) in one mbuf chain when bridge_pfil() need to send this reassembled packet to the outgoing interface, it needs to re-fragment it by using bridge_fragment() bridge_fragment() had to split this mbuf (using ip_fragment) first then had to M_PREPEND each packet in the mbuf chain for adding Ethernet header. But M_PREPEND can sometime create a new mbuf on the begining of the mbuf chain, then the "main" pointer of this mbuf chain should be updated and this case is tottaly forgotten. The original bridge_fragment code (Revision 158140, 2006 April 29) came from OpenBSD, and the call to bridge_enqueue was embedded. But on FreeBSD, bridge_enqueue() is done after bridge_fragment(), then the original OpenBSD code can't work as-it of FreeBSD. PR: 185633 Submitted by: Olivier Cochard-Labbé
* MFC: r284583, r285797, r285799, r287168, r298714, r298720, r298838,jkim2016-09-30344-14592/+23652
| | | | | | | | r300879 Merge ACPICA up to 20160527. Requested by: mav
* MFC 305034: Implement 'devctl clear driver' to undo a previous 'set driver'.jhb2016-09-307-6/+132
| | | | | | | | | | | Add a new 'clear driver' command for devctl along with the accompanying ioctl and devctl_clear_driver() library routine to reset a device to use a wildcard devclass instead of a fixed devclass. This can be used to undo a previous 'set driver' command. After the device's name has been reset to permit wildcard names, it is reprobed so that it can attach to newly-available (to it) device drivers. Sponsored by: Chelsio Communications
* MFC 305502: Reset PCI pass through devices via PCI-e FLR during VM start/end.jhb2016-09-306-4/+296
| | | | | | | | | | | | Add routines to trigger a function level reset (FLR) of a PCI-express device via the PCI-express device control register. This also includes support routines to wait for pending transactions to complete as well as calculating the maximum completion timeout permitted by a device. Change the ppt(4) driver to reset pass through devices before attaching to a VM during startup and before detaching from a VM during shutdown. Sponsored by: Chelsio Communications
OpenPOWER on IntegriCloud