summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Add support for DLINK DWA-127 Wireless Adapterbr2013-09-052-0/+2
| | | | | | | | Approved by: cognet (mentor)
* | Remove stub implementation.ae2013-09-051-11/+0
| | | | | | | | MFC after: 1 week
* | Correct the logic broken in my last commit.pjd2013-09-051-1/+1
| | | | | | | | Reported by: tijl
* | Remove unused code and sort variables declarations.ae2013-09-051-8/+2
| | | | | | | | | | PR: kern/181822 MFC after: 1 week
* | Add more references.mav2013-09-051-1/+5
| | | | | | | | | | Submitted by: Dmitry Luhtionov <dmitryluhtionov@gmail.com> MFC after: 1 week
* | Fix file selection logic for the RCS/SCCS case, as was done for the simplese2013-09-052-34/+27
| | | | | | | | | | | | | | file case before. Bump version because of the changed behavior, which now matches the documentation. Reviewed by: pfg
* | Restore builds on architectures that don't support CAPABILITIES (mips).sbruno2013-09-051-0/+4
| |
* | This looks like a typo that breaks the build. Yell at me if this isn't thesbruno2013-09-051-1/+1
| | | | | | | | intended declaration.
* | Fix the build.jhibbits2013-09-051-0/+2
| |
* | Remove fallback to fork(2) if pdfork(2) is not available. If the parentpjd2013-09-052-10/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | process dies, the process descriptor will be closed and pdfork(2)ed child will be killed, which is not the case when regular fork(2) is used. The PROCDESC option is now part of the GENERIC kernel configuration, so we can start depending on it. Add UPDATING entry to inform that this option is now required and log detailed instruction to syslog if pdfork(2) is not available: The pdfork(2) system call is not available; recompile the kernel with options PROCDESC Submitted by: Mariusz Zaborski <oshogbo@FreeBSD.org> Sponsored by: Google Summer of Code 2013
* | Add sysctl/tunables for various metaslab variables.pjd2013-09-051-4/+33
| |
* | Advise a full buildworld, because of the recent Capsicum changes.pjd2013-09-051-0/+8
| | | | | | | | Sponsored by: The FreeBSD Foundation
* | Add missing '2'.pjd2013-09-051-1/+1
| |
* | Remove trailing comma.pjd2013-09-051-1/+1
| |
* | Style fixes.pjd2013-09-051-122/+122
| |
* | Style fixes. Most fixes are about not treating integers and pointers aspjd2013-09-051-165/+137
| | | | | | | | booleans.
* | Regenerate after r255219.pjd2013-09-0511-171/+65
| | | | | | | | Sponsored by: The FreeBSD Foundation
* | Change the cap_rights_t type from uint64_t to a structure that we can extendpjd2013-09-0593-675/+1402
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in the future in a backward compatible (API and ABI) way. The cap_rights_t represents capability rights. We used to use one bit to represent one right, but we are running out of spare bits. Currently the new structure provides place for 114 rights (so 50 more than the previous cap_rights_t), but it is possible to grow the structure to hold at least 285 rights, although we can make it even larger if 285 rights won't be enough. The structure definition looks like this: struct cap_rights { uint64_t cr_rights[CAP_RIGHTS_VERSION + 2]; }; The initial CAP_RIGHTS_VERSION is 0. The top two bits in the first element of the cr_rights[] array contain total number of elements in the array - 2. This means if those two bits are equal to 0, we have 2 array elements. The top two bits in all remaining array elements should be 0. The next five bits in all array elements contain array index. Only one bit is used and bit position in this five-bits range defines array index. This means there can be at most five array elements in the future. To define new right the CAPRIGHT() macro must be used. The macro takes two arguments - an array index and a bit to set, eg. #define CAP_PDKILL CAPRIGHT(1, 0x0000000000000800ULL) We still support aliases that combine few rights, but the rights have to belong to the same array element, eg: #define CAP_LOOKUP CAPRIGHT(0, 0x0000000000000400ULL) #define CAP_FCHMOD CAPRIGHT(0, 0x0000000000002000ULL) #define CAP_FCHMODAT (CAP_FCHMOD | CAP_LOOKUP) There is new API to manage the new cap_rights_t structure: cap_rights_t *cap_rights_init(cap_rights_t *rights, ...); void cap_rights_set(cap_rights_t *rights, ...); void cap_rights_clear(cap_rights_t *rights, ...); bool cap_rights_is_set(const cap_rights_t *rights, ...); bool cap_rights_is_valid(const cap_rights_t *rights); void cap_rights_merge(cap_rights_t *dst, const cap_rights_t *src); void cap_rights_remove(cap_rights_t *dst, const cap_rights_t *src); bool cap_rights_contains(const cap_rights_t *big, const cap_rights_t *little); Capability rights to the cap_rights_init(), cap_rights_set(), cap_rights_clear() and cap_rights_is_set() functions are provided by separating them with commas, eg: cap_rights_t rights; cap_rights_init(&rights, CAP_READ, CAP_WRITE, CAP_FSTAT); There is no need to terminate the list of rights, as those functions are actually macros that take care of the termination, eg: #define cap_rights_set(rights, ...) \ __cap_rights_set((rights), __VA_ARGS__, 0ULL) void __cap_rights_set(cap_rights_t *rights, ...); Thanks to using one bit as an array index we can assert in those functions that there are no two rights belonging to different array elements provided together. For example this is illegal and will be detected, because CAP_LOOKUP belongs to element 0 and CAP_PDKILL to element 1: cap_rights_init(&rights, CAP_LOOKUP | CAP_PDKILL); Providing several rights that belongs to the same array's element this way is correct, but is not advised. It should only be used for aliases definition. This commit also breaks compatibility with some existing Capsicum system calls, but I see no other way to do that. This should be fine as Capsicum is still experimental and this change is not going to 9.x. Sponsored by: The FreeBSD Foundation
* | Correct blkback handling of the BLKIF_OP_FLUSH_DISKCACHE opcode.gibbs2013-09-041-12/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Properly round-trip the "operation code" for client requests. sys/dev/xen/blkback/blkback.c: In xbb_dispatch_dev() when processing a flush request, correctly set bio->bio_caller1 to the request list (not bare request) for the operation, as is expected by the completion handler xbb_bio_done(). In xbb_get_resources(), initialize "operation" in the driver's internal request object from the client's "ring request", so it is correct when used to populate the reply when this operation completes. Submitted by: Roger Pau Monné Sponsored by: Citrix Systems R&D Reviewed by: gibbs
* | Tidy up some loose ends in the PCID code:kib2013-09-048-73/+98
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Restore the pre-PCID TLB shootdown handlers for whole address space and single page invalidation asm code, and assign the IPI handler to them when PCID is not supported or disabled. Old handlers have linear control flow. But, still use the common return sequence. - Stop using pcpu for INVPCID descriptors in the invlrg handler. It is enough to allocate descriptors on the stack. As result, two SWAPGS instructions are shaved off from the code for Haswell+. - Fix the reverted condition in invlrng for checking of the PCID support [1], also in invlrng check that pmap is kernel pmap before performing other tests. For the kernel pmap, which provides global mappings, the INVLPG must be used for invalidation always. - Save the pre-computed pmap' %CR3 register in the struct pmap. This allows to remove several checks for pm_pcid validity when %CR3 is reloaded [2]. Noted by: gibbs [1] Discussed with: alc [2] Tested by: pho, flo Sponsored by: The FreeBSD Foundation
* | Crashes have been observed for NFSv4.1 mounts when the systemrmacklem2013-09-041-11/+9
| | | | | | | | | | | | | | | | | | | | is being shut down which were caused by the nfscbd_pool being destroyed before the backchannel is disabled. This patch is believed to fix the problem, by simply avoiding ever destroying the nfscbd_pool. Since the NFS client module cannot be unloaded, this should not cause a memory leak. MFC after: 2 weeks
* | sh: Make return return from the closest function or dot script.jilles2013-09-045-15/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | Formerly, return always returned from a function if it was called from a function, even if there was a closer dot script. This was for compatibility with the Bourne shell which only allowed returning from functions. Other modern shells and POSIX return from the function or the dot script, whichever is closest. Git 1.8.4's rebase --continue depends on the POSIX behaviour. Reported by: Christoph Mallon, avg
* | Add myself as a new committer and cognet as my mentor.zbb2013-09-041-0/+2
| | | | | | | | Approved by: cognet (mentor)
* | Add 32-bit support for Gxemul's oldtestmips machine emulationgonzo2013-09-046-7/+107
| | | | | | | | Original work by: kan@
* | Add myself to the list of ports committers.gnn2013-09-041-0/+3
| | | | | | | | Approved by: skreuzer (mentor)
* | Revert r255152:eadler2013-09-041-2/+2
| | | | | | | | | | | | | | | | | | It turns out that synaptics_support was turned off by default because its probing method is too intrusive not because it was unstable. Once this is fixed it should be enabled once again. Reported by: delphij, jkim
* | add links for the various vmem functions...jmg2013-09-041-0/+7
| |
* | MFP4 217312, 222008, 222052, 222053, 222673, 231484, 231491, 231565, 570643brooks2013-09-046-47/+340
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rework the timeout code to use actual time rather than a DELAY() loop and to use both typical and maximum to allow logging of timeout failures. Also correct the erase timeout, it is specified in milliseconds not microseconds like the other timeouts. Do not invoke DELAY() between status queries as this adds significant latency which in turn reduced write performance substantially. Sanity check timeout values from the hardware. Implement support for buffered writes (only enabled on Intel/Sharp parts for now). This yields an order of magnitude speedup on the 64MB Intel StrataFlash parts we use. When making a copy of the block to modify, also keep a clean copy around until we are ready to commit the block and use it to avoid unnecessary erases. In the non-buffer write case, also use it to avoid unnecessary writes when the block has not been erased. This yields a significant speedup when doing things like zeroing a block. Sponsored by: DARPA, AFRL Reviewed by: imp (previous version)
* | Add a c++/v1/tr1 include directory containing symlinks to all of the standardtheraven2013-09-042-0/+3
| | | | | | | | | | | | | | | | | | headrs. Lots of third-party code expects to find C++03 headers under tr1 because that's where GNU decided to hide them. This should fix ports that expect them there. MFC after: 1 week
* | Trim a couple of panic messages.jhb2013-09-041-8/+2
| |
* | - Add myself as a src committerbr2013-09-041-0/+2
| | | | | | | | | | | | - Note cognet is my mentor Approved by: cognet (mentor)
* | Make default cache size more modern.glebius2013-09-041-1/+1
| | | | | | | | Requested by: Slawa Olhovchenkov <slw zxy.spb.ru>
* | Fix hwpmc(4) for 32-bit PowerPC.jhibbits2013-09-042-8/+2
| |
* | For TOE connections, the window scale factor in CPL_PASS_ACCEPT_REQ isnp2013-09-031-1/+1
| | | | | | | | | | | | set to 15 to indicate that the peer did not send a window scale option with its SYN. Do not send a window scale option in the SYN|ACK reply in that case.
* | Add options GEOM_PART_GPT and options MSDOSFS to the DIR-825sbruno2013-09-031-0/+3
| | | | | | | | Reviewed by: adrian@
* | Newer versions of gcc define __INT64_C and __UINT64_C, so avoidimp2013-09-032-0/+4
| | | | | | | | redefining them if gcc provides them.
* | Add support for the 'invpcid' instruction to binutils and DDB'sjhb2013-09-035-4/+27
| | | | | | | | | | | | disassembler on amd64. MFC after: 1 month
* | Remove our hacked GNU patch.pfg2013-09-0320-4809/+3
| | | | | | | | | | | | | | | | | | | | | | The old (2.1) GNU patch has outlived its days. The major local changes have been moved into the less restrictedly licensed patch(1) we adopted in usr.bin/ . A much newer version of GNU patch is available in the ports tree (devel/patch). Disconnect from the build and remove.
* | Remove redundant field pr_sctp_on.tuexen2013-09-035-13/+3
| | | | | | | | MFC after: 1 week
* | Use the fact that the AES-NI instructions can be pipelined to improvejmg2013-09-0310-428/+380
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | performance... Use SSE2 instructions for calculating the XTS tweek factor... Let the compiler do more work and handle register allocation by using intrinsics, now only the key schedule is in assembly... Replace .byte hard coded instructions w/ the proper instructions now that both clang and gcc support them... On my machine, pulling the code to userland I saw performance go from ~150MB/sec to 2GB/sec in XTS mode. GELI on GNOP saw a more modest increase of about 3x due to other system overhead (geom and opencrypto)... These changes allow almost full disk io rate w/ geli... Reviewed by: -current, -security Thanks to: Mike Hamburg for the XTS tweek algorithm
* | add support to gcc for AES and PCLMUL intrinsics... This addes thejmg2013-09-038-7/+135
| | | | | | | | | | | | | | | | -maes option, but not the -mpclmul option as I ran out of bits in the 32 bit flags field... You can -D__PCLMUL__ to get this, but it won't be compatible w/ clang and modern gcc... Reviewed by: -current, -toolchain
* | Connect libexecinfo to the buildemaste2013-09-033-1/+3
| | | | | | | | Sponsored by: DARPA, AFRL
* | sys/dev/xen/blkback/blkback.c:gibbs2013-09-031-1/+1
| | | | | | | | | | | | | | | | | | | | Initialize the request id for requests in xbb_get_resources() instead of its previous location in xbb_dispatch_io(). This guarantees that all request types (e.g. BLKIF_OP_FLUSH_DISKCACHE) have the front-end specified id recorded. Submitted by: Roger Pau Monné Sponsored by: Citrix Systems R&D
* | Include the calling context in the mail subject, if any.jlh2013-09-031-4/+6
| | | | | | | | | | | | | | | | | | | | More concretely, periodic security scripts defaults to being called from daily ones -- daily context -- so the mail subject will now be "${HOST} daily security run output" instead of "{HOST} security run output". If you switch the period of some security checks to weekly, you will receive another email "${HOST} weekly security run output".
* | Add svn:keywords propertyemaste2013-09-030-0/+0
| |
* | Add $FreeBSD$ tag for user-facing headeremaste2013-09-031-0/+1
| |
* | Don't install private libexecinfo headersemaste2013-09-031-1/+1
| |
* | Fix 'make depend'uqs2013-09-032-1/+2
| |
* | Document SIGLIBRT in signal(3); take a stab at the signal description asrwatson2013-09-031-0/+1
| | | | | | | | | | | | the original committer didn't provide one. MFC after: 3 days
* | Since r254974, periodic scripts' period can be configuredjlh2013-09-031-208/+236
| | | | | | | | | | independently. There is no reason to leave their options with the daily ones, so move them to their own section.
OpenPOWER on IntegriCloud