summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Set net.inet6.ip6.fw.enable as well.ume2010-04-061-0/+2
|
* When OOM searches for a process to kill, ignore the processes alreadykib2010-04-064-9/+20
| | | | | | | | | | | | | | | killed by OOM. When killed process waits for a page allocation, try to satisfy the request as fast as possible. This removes the often encountered deadlock, where OOM continously selects the same victim process, that sleeps uninterruptibly waiting for a page. The killed process may still sleep if page cannot be obtained immediately, but testing has shown that system has much higher chance to survive in OOM situation with the patch. In collaboration with: pho Reviewed by: alc MFC after: 4 weeks
* In wait_for_pids(), pwait(1) can return when the process exits, butdougb2010-04-061-1/+4
| | | | | | | | | | | | | | | | still exists as a zombie. The 'kill -0' test in this function can therefore return true even if the process isn't actually running. This could lead to wait_for_pids() printing an endless string of the pid number until the zombie finally exits. Solve this problem by moving the sleep up to after the 'kill -0' test, but only after we've run through the function once already. In the common case (only one pid in the list) this will always do the right thing. On the rare occasion that there is more than one pid in the list this will sleep 1 second per zombie process which will allow that process, and any other in the list a chance to exit. While I'm here, local'ize the variables that this function uses.
* Remove yet another vestage of alpha support.imp2010-04-061-2/+0
|
* Harden the experimental NFS server a little, by adding rangermacklem2010-04-061-0/+22
| | | | | | | | | checks on the length of the client's open/lock owner name. Also, add free()'s for one case where they were missing and would have caused a leak if NFSERR_BADXDR had been replied. Probably never happens, but the leak is now plugged, just in case. MFC after: 2 weeks
* MFV of tzdata2010h:edwin2010-04-053-41/+50
| | | | | | | | | | | | | | | | | From tzdata2010h: - Tunis will not go into DST this year. - Pakistan will not go into DST this year. From tzdata2010g: - Bangladesh cancels DST. - Palestine goes into DST one day later than expected. - Russian timezones update: Europe/Samara goes to Moscow time. Asia/Kamchatka goes to Moscow+8 time. Asia/Anadyr goes to Moscow+8 time.
* I feel this wording of the history is more clear.obrien2010-04-052-9/+6
| | | | ANSIfy vasprintf() while I'm here.
* Synchronize Coda kernel module definitions in our coda.h to Coda 6'srwatson2010-04-059-137/+149
| | | | | | | | | | | | | | | | | | | coda.h: - CodaFid typdef -> struct CodaFid throughout. - Use unsigned int instead of unsigned long for venus_dirent and other cosmetic fixes. - Introduce cuid_t and cgid_t and use instead of uid_t and gid_t in RPCs. - Synchronize comments and macros. - Use u_int32_t instead of unsigned long for coda_out_hdr. With these changes, a 64-bit Coda kernel module now works with coda6_client, whereas previous userspace and kernel versions of RPCs differed sufficiently to prevent using the file system. This has been verified only with casual testing, but /coda is now usable for at least basic operations on amd64. MFC after: 1 week
* Correct definition of CIOC_KERNEL_VERSION Coda ioctl() for systemsrwatson2010-04-051-1/+1
| | | | | | | where sizeof(int) != sizeof(sizeof(int)), or the ioctl will return EINVAL. MFC after: 3 days
* Refine previous partial merge of OpenSolaris onnv revision 9396:f41cf682d0d3.delphij2010-04-051-1/+6
| | | | | | | | | | This fixes a regression that zfs list would crash on zfs having user properties. PR: kern/145377 Submitted by: mm Approved by: pjd Obtained from: OpenSolaris MFC after: 10 days
* First steps as committer:jacula2010-04-051-0/+4
| | | | | | - add an entry for myself to committers-ports.dot Approved by: pgj (mentor)
* sh: Automatically enable -o emacs in interactive shells with terminals.jilles2010-04-052-3/+7
| | | | | | | This makes sh a bit more friendly in single user mode, make buildenv, chroot and the like, and matches other shells. The -o emacs can be overridden on the command line or in the ENV file.
* Add missing @ to the NORMAL_CTFCONVERT line to keep it from appearingimp2010-04-051-1/+1
| | | | in the output.
* libc/db/hash: cap auto-tuned block size with a value that actually worksavg2010-04-052-1/+3
| | | | | | | | | | | | | This fix mostly matters after r206129 that made it possible for st_blksize to be greater than 4K. For this reason, this change should be MFC-ed before r206129. Also, it seems that all FreeBSD uitlities that use db(3) hash databases and create new databases in files, specify their own block size value and thus do not depend on block size autotuning. PR: bin/144446 Submitted by: Peter Jeremy <peterjeremy@acm.org> MFC after: 5 days
* hash.3: fix a factual mistake in the man pageavg2010-04-051-1/+1
| | | | | | PR: bin/144446 Submitted by: Peter Jeremy <peterjeremy@acm.org> MFC after: 3 days
* indent.pro example: put all options one per lineavg2010-04-051-2/+30
| | | | | | | This should help with modification tracking. Discussed with: bde MFC after: 7 days
* indent.pro example: correctly place -ta optionavg2010-04-051-2/+1
| | | | | | | The options are sorted, leading 'n' (for 'off') should be ignored. Pointed out by: bde MFC after: 7 days
* vm_reserv_alloc_page() should never be called on an OBJT_SG object, just asalc2010-04-051-0/+1
| | | | | | | | it is never called on an OBJT_DEVICE object. (This change should have been included in r195840.) Reported by: dougb@, avg@ MFC after: 3 days
* Harden the experimental NFS server a little, by adding extra checksrmacklem2010-04-041-12/+11
| | | | | | | | | | in the readdir functions for non-positive byte count arguments. For the negative case, set it to the maximum allowable, since it was actually a large positive value (unsigned) on the wire. Also, fix up the readdir function comment a bit. Suggested by: dillon AT apollo.backplane.com MFC after: 2 weeks
* sh: Add test for nested arithmetic substitution.jilles2010-04-041-0/+17
| | | | | Pre-r206145 sh changes nested arithmetic substitution to parentheses, which is not always correct, as exercised by this test.
* sh: Add test for some associativity in arithmetic.jilles2010-04-041-0/+20
|
* Fix compilation error on amd64.ume2010-04-041-2/+3
| | | | | Reported by: stefanf MFC after: 2 weeks
* Add missing MNT_NFS4ACLS.jh2010-04-041-0/+1
|
* Fix compilation error on 9-CURRENT.ume2010-04-041-6/+6
| | | | | Reported by: nyan MFC after: 2 weeks
* sh: Document the expansion changes in the man page.jilles2010-04-041-2/+20
| | | | | | | | Note that the following sentence > Enclosing the full parameter expansion string in double-quotes does not > cause the following four varieties of pattern characters to be quoted, > whereas quoting characters within the braces has this effect. is now true, but used to be incorrect.
* services_mkdb; generate db file from services(5) to increaseume2010-04-045-0/+695
| | | | | | | speed of getserv*() Obtained from: NetBSD MFC after: 2 weeks
* Add capability to use a db version of services. It is enabled byume2010-04-046-3/+224
| | | | | | specifying `db' as source of service in /etc/nsswitch.conf. MFC after: 2 weeks
* Reduce duplicate code.ume2010-04-041-59/+33
| | | | MFC after: 2 weeks
* Treat '+' as special only when in compat mode, and simplifyume2010-04-041-22/+19
| | | | | | the logic bit. MFC after: 2 weeks
* Stop adding trailing '\n'. The servent_unpack() doesn't expectume2010-04-041-10/+3
| | | | | | lines terminated with '\n'. MFC after: 2 weeks
* Use also SCTP/IPv6 checksum offloading in special cases.tuexen2010-04-031-13/+60
| | | | MFC after: 2 weeks
* sh: Do tilde expansion in substitutions.jilles2010-04-032-3/+93
| | | | | | | | | | | | | This applies to word in ${v-word}, ${v+word}, ${v=word}, ${v?word} (which inherits quoting from the outside) and in ${v%word}, ${v%%word}, ${v#word}, ${v##word} (which does not inherit any quoting). In all cases tilde expansion is only attempted at the start of word, even if word contains spaces. This agrees with POSIX and other shells. This is the last part of the patch tested in the exp-run. Exp-run done by: erwin (with some other sh(1) changes)
* sh: Fix duplicate variable name in test.jilles2010-04-031-2/+2
|
* sh: Add some testcases for the working parts of tilde expansion.jilles2010-04-031-0/+56
|
* sh: Allow quoting pattern match characters in ${v%pat} and ${v#pat}.jilles2010-04-032-1/+58
| | | | | | | | Note that this depends on r206145 for allowing pattern match characters to have their special meaning inside a double-quoted expansion like "${v%pat}". PR: bin/117748 Exp-run done by: erwin (with some other sh(1) changes)
* sh: Remove special handling for ' and " in arithmetic.jilles2010-04-032-6/+1
| | | | | | | They will be treated like normal characters, resulting in a runtime arithmetic expression error. Exp-run done by: erwin (with some other sh(1) changes)
* sh: Fix various things about expansions:jilles2010-04-033-73/+256
| | | | | | | | | | | | | | | | | | | | * remove the backslash from \} inside double quotes inside +-=? substitutions, e.g. "${$+\}a}" * maintain separate double-quote state for ${v#...} and ${v%...}; single and double quotes are special inside, even in a double-quoted string or here document * keep track of correct order of substitutions and arithmetic This is different from dash's approach, which does not track individual double quotes in the parser, trying to fix this up during expansion. This treats single quotes inside "${v#...}" incorrectly, however. This is similar to NetBSD's approach (as submitted in PR bin/57554), but recognizes the difference between +-=? and #% substitutions hinted at in POSIX and is more refined for arithmetic expansion and here documents. PR: bin/57554 Exp-run done by: erwin (with some other sh(1) changes)
* sh: Treat unexpected newlines in substitutions as a syntax error.jilles2010-04-031-0/+4
| | | | | | | The old approach was wrong because PS2 was not used and seems unlikely to parse extensions (ksh93's ${ COMMAND} may well fail to parse). Exp-run done by: erwin (with some other sh(1) changes)
* sh: Add some testcases for the working parts of ${v%...} and ${v#...}.jilles2010-04-031-0/+85
|
* Make _vm_map_init() the one place where the vm map's pmap field isalc2010-04-033-13/+12
| | | | | | initialized. Reviewed by: kib
* Just use <stdint.h> instead of <inttypes.h>. We don't need it here.ed2010-04-031-1/+1
|
* Re-enable the call to pmap_release() by vmspace_dofree(). The accountingalc2010-04-031-6/+3
| | | | | | | | problem that is described in the comment has been addressed. Submitted by: kib Tested by: pho (a few months ago) MFC after: 6 weeks
* * Fix some race condition in SACK/NR-SACK processing.tuexen2010-04-0315-808/+439
| | | | | | | | * Fix handling of mapping arrays when draining mbufs or processing FORWARD-TSN chunks. * Cleanup code (no duplicate code anymore for SACKs and NR-SACKs). Part of this code was developed together with rrs. MFC after: 2 weeks.
* Add a forward declaration to silence a warning when compiling ia32_genassym.c.bz2010-04-031-0/+1
| | | | | Reviewed by: kib MFC after: 3 days
* Fix some whitespace nits.pjd2010-04-031-7/+5
|
* Add missing mnt_kern_flag flags in 'show mount' output.pjd2010-04-031-1/+5
|
* Bump PKG_INSTALL_VERSION to 20100403.flz2010-04-031-1/+1
|
* Fix pkg_delete, check if the file we're trying to delete is aflz2010-04-031-1/+1
| | | | | | | | symlink before complaining that it doesn't exist. Typical case would be a leftover library symlink that's left over after the actual library has been removed. Reported by: tabthorpe
* g_vfs_open: allow only one mount per device vnodeavg2010-04-031-1/+6
| | | | | | | | | | | | | | | | In other words, deny multiple read-only mounts of the same device. Shared read-only mounts should theoretically be possible, but, unfortunately, can not be implemented correctly using current buffer cache code/interface and results in an eventual system crash. Also, using nullfs seems to be a more efficient way to achieve the same goal. This gets us back to where we were before GEOM and where other BSDs are. Submitted by: pjd (idea for checking for shared mounting) Discussed with: phk, pjd Silence from: fs@, geom@ MFC after: 2 weeks
* vn_stat: take into account va_blocksize when setting st_blksizeavg2010-04-031-3/+2
| | | | | | | | | | | | | | | | | | | As currently st_blksize is always PAGE_SIZE, it is playing safe to not use any smaller value. For some cases this might not be optimal, but at least nothing should get broken. Generally I don't expect this commit to change much for the following reasons (in case of VREG, VDIR): - application I/O and physical I/O are sufficiently decoupled by filesystem code, buffer cache code, cluster and read-ahead logic - not all applications use st_blksize as a hint, some use f_iosize, some use fixed block sizes I expect writes to the middle of files on ZFS to benefit the most from this change. Silence from: fs@ MFC after: 2 weeks
OpenPOWER on IntegriCloud