Add libubsan

(christos)

conditionalize

(christos)

add ubsan

(christos)

add ubsan to the build

(christos)

revert, everything coredumps with this change.

(christos)

PR/50773: Rin Okuyama: Fix single stepping on dynamically linked binaries
by skipping dynamic linker calls (from OpenBSD)

(christos)

sanitizer for all.

(christos)

Asan is back

(christos)

Add bsd_signal as required by POSIX (from GSoC 2016, Charles Cui)

(christos)

new ntp

(christos)

resolve conflicts

(christos)

Fix compilation on non-x86

(christos)

add extents.

(christos)

ext4 extents support

(christos)

ext4 extents glue

(christos)

Add ext4 extent support from GSoC 2016 (Hrishikesh Goyal), from the FreeBSD
ext2 code.

(christos)

Fix previous to better match readline behavior (Ingo Schwarze)

(christos)

fix sets.

(christos)

Fix ILP32 build.

(christos)

From Ingo Schwarze:

In libedit, the only way how H_ENTER can fail is memory exhaustion,
too, and of course it is handled gracefully, returning -1 from
history().  So of course, we will continue to handle it gracefully
in add_history() as well, but we are free to decide what to do with
the library state in this case because GNU just dies...

I think the most reasonable course of action is to simply not change
the library state in any way when add_history() fails due to memory
exhaustion, but just return.

If H_ENTER does not fail, we know that the history now contains at
least one entry, so there is no need any longer to check the H_GETSIZE
return value.  And we can of course always set current_history_valid.

While testing these changes, i noticed three problems so closely
related that i'd like to fix them in the same diff.

1. libedit has the wrong prototype for add_history().
    GNU readline-6.3 defines it as void add_history(const char *).
    Of course, that is very stupid - no way to report problems to
    the caller!  But the whole point of a compatibility mode is
    being compatible, so we should ultimately change this.
    Of course, changing the prototype of a public symbol requires
    a libedit major bump.  I don't want to do that casually.
    Rather, i will take a note and change the prototype the next
    time we need a libedit major bump for more important reasons.
    For now, let's just always return 0.

2. While *implicitely* pushing an old entry off the history
    increments history_base in GNU readline, testing reveals that
    *explicitly* deleting one does not.  Again, this is not
    documented, but it applies to both remove_history() and
    stifle_history().  So delete history_base manipulation
    from stifle_history(), which also allows to simplify the
    code and delete two automatic variables.

3. GNU readline add_history(NULL) crashes with a segfault.
    There is nothing wrong with having a public interface
    behave that way.  Many standard interfaces do, including
    strlen(3).  Such crashes can even be useful to catch
    buggy application programs.
    In libedit/readline.c rev. 1.104, Christos made add_history()
    silently ignore this coding error, according to the commit
    message to hide a bug in nslookup(1).  That change was never
    merged to OpenBSD.  I strongly disagree with this change.
    If nslookup(1) is still broken, that program needs to be
    fixed instead.  In any case, delete the bogus check; hiding
    bugs is dangerous.

(christos)

mention hostzerobroadcast default to "no".

(christos)

Use NULL instead of 0.

(christos)

Use NULL instead of 0 (Pedro Giffuni)

(christos)

Add ubsan (not enabled, not tested, compiling)
Update tsan (not enable, not tested, not compiling)
Merge common infrastructure.
XXX: Perhaps the common code should be made into a separate library?
Or always require asan?

(christos)

Put the sanitizer libraries before everything else, since it needs to be
the first shared object.

(christos)

put back asan

(christos)

Put back asan now it works.

(christos)

deal with rename lossage

(christos)

Don't intercept things we don't have.

(christos)

Handle wrapping the same way as FreeBSD does.

(christos)

missing space

(christos)

use the default offsets since gcc hardcodes them (TARGET_ASAN_SHADOW_OFFSET ->
ix86_asan_shadow_offset)

(christos)

use the correct array size.

(christos)

zero pad syscall.

(christos)

more flags.

(christos)

Ignore the first dlpi entry which is ourselves on NetBSD instead of having
a NULL name as on linux.

(christos)

Avoid locking issues when copying out requires taking a fault and we are
finding out our own maps, by allocating a buffer and copying out after
we collected the information.

(christos)

Symbolic printing for mmap

(christos)

Add more alignments

(christos)

- hack BlockingMutex
- add NetBSD procmaps
- remove old unused source

(christos)

Add procmaps for NetBSD

(christos)

Update sources and flags (compiles but missing stuff)

(christos)

First steps to port this to NetBSD (compiles now but missing stuff)

(christos)

revert weak change. next time point to an example of what breaks in the
commit message.

(christos)

Add an ElfW() macro like linux.

(christos)

remove the right history entry (Ingo Schwarze)

(christos)

Handle PIC linking for tests

(christos)

Make sure that all messages end in '\n' in make_message_rcsvalid() and
compensate for it in add_rcs_file().

(christos)

Don't make crunch binaries PIE

(christos)

Don't build PIE binaries for install media

(christos)

npftest needs to disable mprotect because it uses bpfjit

(christos)

Fix mprotect for the helper.

(christos)

Skip the mprotect_exec test if PaX MPROTECT restrictions are enabled.

(christos)

make hostzerobroadcast default to "no".

(christos)

fix compilation without PAX_MPROTECT

(christos)

new bind

(christos)

merge conflicts

(christos)

Give 0,1,2 for security.pax.mprotect.ptrace and make it default to 1
as documented in sysctl(7):
0 - ptrace does not affect mprotect
1 - (default) mprotect is disabled for processes that start executing from
    the debugger (being traced)
2 - mprotect restrictions are relaxed for traced processes

(christos)

Document security.pax.mprotect.ptrace

(christos)

Apply patch https://github.com/acpica/acpica/commit/\
    c450c13615f7af0673230041da4216b3de5bc4d3.patch

This patch fixes 2 issues in AccessWidth/BitOffset support and adds
comments to justify the BitOffset/BitWidth style macro usages. Lv Zheng.

This patch introduces ACPI_IS_ALIGNED() macro. Lv Zheng.

The old register descriptors are translated in AcpiTbInitGenericAddress()
with AccessWidth being filled with 0. This breaks code in
AcpiHwGetAccessBitWidth() when the registers are 16-bit IO ports and their
BitWidth fields are filled with 16. The rapid fix is meant to make code
written for AcpiHwGetAccessBitWidth() regression safer before the issue is
correctly fixed from AcpiTbInitGenericAddress(). Reported by
John Baldwin <jhb@freebsd.org>, Fixed by Lv Zheng <lv.zheng@intel.com>,
Tested by Jung-uk Kim <jkim@freebsd.org>.

(christos)

Introduce security.pax.mprotect.ptrace sysctl which can be used to bypass
mprotect settings so that debuggers can write to the text segment of traced
processes so that they can insert breakpoints. Turned off by default.
Ok: chuq (for now)

(christos)

randomize the location of the rtld.

(christos)

abstract read code to a single function (Ingo Schwarze)

(christos)

Give up and use TOOL_SED again.

(christos)

Fix SED issue differently.

(christos)

Export the variables so that they propagate via sets.subr -> make -> mkvars.mk

(christos)

Put the name of the dynamic linker in allocated memory, so that it becomes
part of the core file link-map, so that gdb can find it.

(christos)

This should be SED not TOOL_SED since this is what is set from the ${SETSENV}
command in the Makefile!

(christos)

el_map.alt can't be NULL here (Ingo Schwarze)

(christos)

remove debug read (Ingo Schwarze)

(christos)

Fix armv3 segv compiling mDNS.c, from:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62254
    https://gcc.gnu.org/ml/gcc-patches/2016-02/msg01095.html

(christos)

From Ingo Schwarze:

Reduce obfuscation of errno handling. There is only one purpose
non-local errno handling is needed for:  Inside el_wgets(), several
functions call down indirectly to el_wgetc(), many of them via the
dispatch table.  When el_wgetc() fails, it does properly report
failure, but then various cleanup is done which may clobber errno.
But when returning due to failure, el_wgets() wants to have errno
set to the reason of the original read failure, not to the reason
of some subsequent failure of some cleanup operation.  So el_wgetc()
needs to save errno, and if it's non-zero, el_wgets() needs to
restore it on failure.

This core logic is currently obscured by the fact that el_errno
is set and inspected at some additional places where it isn't needed.
Besides, since el_wgetc() and and el_wgets() are both in read.c,
el_errno does not need to be in struct editline, it can and should
be local to read.c in struct el_read_t.

Let's look at what can be simplified.

1. keymacro_get() abuses el_errno instead of having a proper
    error return code.  Adding that error return code is easy
    because node_trav() already detects the condition and an
    adequate code is already defined.  Returning it, testing
    for it in read_getcmd(), and returning with error from there
    removes the need to inspect el_errno from el_wgets() after
    calling read_getcmd().
    Note that resetting lastchar and cursor and clearing buffer[0]
    is irrelevant.  The code returns from el_wgets() right afterwards.
    Outside el_wgets(), these variables are no longer relevant.
    When el_wgets() is called the next time, it will call ch_reset()
    anyway, resetting the two pointers.  And as long as lastchar
    points to the beginning of the buffer, the contents of the
    buffer won't be used for anything.

2. read_getcmd() doesn't need to set el_errno again after el_wgetc()
    failure since el_wgetc() already did so.  While here, remove
    the silly "if EOF or error" comments from the el_wgetc()
    return value tests.  It's a public interface documented in a
    manual, so people working on the implementation can obviously
    be expected to know how it works.  It's a case of

      count++;  /* Increment count. */

3. In the two code paths of el_wgets() that lead up to "goto noedit",
    there is no need to save the errno because nothing that might
    change it happens before returning.

For clarity, since el_wgets() is the function restoring the errno,
also move initializing it to the same function.

Finally, note that restoring errno when the saved value is zero is
wrong.  No library code is ever allowed to clear a previously set
value of errno.  Only application programs are allowed to do that,
and even they usually don't need to do so, except when using certain
ill-designed interfaces like strtol(3).

I tested that the behaviour remains sane in the following cases,
all during execution of el_wgets(3) and with a signal handler
for USR1 installed without SA_RESTART.

* Enter some text and maybe move around a bit.
  Then send a USR1 signal.
  The signal gets processed, then read_char() resumes reading.
  Send another USR1 signal.
  Now el_wgets() sets errno=EINTR and returns -1.

* Press Ctrl-V to activate ed-quoted-insert.
  Then send a USR1 signal.
  The signal gets processed, then read_char() resumes reading.
  Send another USR1 signal.
  ed_quoted_insert() returns ed_end_of_file(), i.e. CC_EOF,
  and el_wgets() returns 0.

* Press a key starting a keyboard macro.
  Then send a USR1 signal.
  The signal gets processed, then read_char() resumes reading.
  Send another USR1 signal.
  Now el_wgets() sets errno=EINTR and returns -1.

* Press : to enter builtin command mode.
  Start typing a command.
  Then send a USR1 signal.
  The signal gets processed, then read_char() resumes reading.
  Send another USR1 signal.
  Now c_gets() returns -1, ed_command() beeps and returns CC_REFRESH,
  and el_wgets() resumes operation as it should.

I also tested with "el_set(el, EL_EDITMODE, 0)", and it returns
the right value and sets errno correctly.

(christos)

Read and load the aux vector from a core file

(christos)

Add a note for the auxv array so we can find our load location from a
core file of a PIE binary.

(christos)

documentation improvements (Ingo Schwarze)

(christos)

Stop the read module from poking the el_chared.c_macro data structure
currently belonging to the chared module.  The read module does so
from three of its functions, while no other module uses the macro
data, not even the chared module itself.  That's quite logical
because macros are a feature of input handling, all of which is
done by the read module, and none by the chared module.  So move
the data into the read modules's own opaque data structure, struct
el_read_t.

That simplifies internal interfaces in several respects: The
semi-public chared.h has one fewer struct, one fewer #define, and
one fewer member in struct el_chared_t; all three move to one single
C file, read.c, and are now module-local.  And the internal interface
function ch_reset() needs one fewer argument, making the code of many
functions in various modules more readable.

The price is one additional internal interface function, read_end(),
10 lines long including comments, called publicly from exactly one
place: el_end() in el.c.  That's hardly an increase in complexity
since most other modules already have their *_end() function, read.c
was the odd one out not having one.

From Ingo Schwarze

(christos)

reduce #ifdef mess caused by PaX

(christos)

Account for the VA hole differently (simpler)

(christos)

Mention MPROTECT issues

(christos)

put back _PATH_WHATIS, it is used.

(christos)

switch evbarm to gdb-7.10.1

(christos)

Switch evbarm to gcc-5.3 and turn on PIE.

(christos)

Add various security options; enables PaX ASLR/MPROTECT

(christos)

Fix the prototype used by EL_GETCFN, mention the associated typedef
name, document the return values, expand the list of affected
functions, warn against using EL_GETCFN, and clarify some wording
and notation. (Ingo Schwarze)

(christos)

PIE in the face!

(christos)

gcc can't compute the large initializer in rpi_release_mem,
so disable stack protector.

(christos)

Turn on PaX ASLR/MPROTECT

(christos)

i386 is PIE now since I am turning PaX ASLR/MPROTECT on.

(christos)

fix for ILP32.

(christos)

Fix infinite recursion when building i386 -fPIE in
src/external/mit/xorg/lib/libxcb/xkb.

https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=231599

PR debug/67355
* var-tracking.c (reverse_op): Don't add dummy zero to reverse
  ops that simplify back to the original value.
* alias.c (refs_newer_value_p): Cut off recursion for
  expressions containing the original value.

(christos)

We don't want PIE!

(christos)

Turn on PIE for sparc64 so we can use ASLR effectively.

(christos)

Turn on ASLR for sparc64

(christos)

lose one more bit of ALSR to account for rounding in the VA hole.

(christos)

Add my list of things to do for 8. To be expanded.

(christos)

mention my last coda work

(christos)

reflect reality (through my ping glasses)

(christos)

Add RCSID's

(christos)

Clamt the PAX_ASLR random value to the max bits we have for VA.

(christos)

Hook to clamp the random value for mmap for machies that don't have enough
VA bits.

(christos)

Adjust to new freetype-2.6.3

(christos)

Adjust to new freetype structure.

(christos)

Adjust to 2.6.3.

(christos)

resolve conflicts; move include files back where the distribution has them.

(christos)

remove stray debugging.

(christos)

Bail out if the string does not look like a timezone (is empty or does not
start with a letter or a number). tzparse("") or tzparse(".45") don't fail.

(christos)

Turn on MPROTECT on GENERIC and both MPROTECT and ASLR on XEN*

(christos)

only print debugging info if we are actually going to change the permission.

(christos)

- make pax aslr stack eat up to 1/8 of the max stack space insted of 1/4
  and reduce the length of the randomization bits since this is unused.
- call the pax aslr stack function sooner so we don't need to re-adjust the
  stack size.
- adjust the stack max resource limit to account for the maximum space that
  can be lost by aslr
- tidy up debugging printfs

(christos)

clamp getrlimit the same way we clamp setrlimit

(christos)

From Bastian Maerkisch, via Igno Schwarze:

Even though section "2.3.3 Information About the History List"
of the history(3) info(1) manual only says

  -- Function: int where_history (void)
    Returns the offset of the current history element.

which maybe isn't completely clear, a plausible implementation
is that the offset returned is the same offset that can be used
for history_set_pos(), i.e. that it is 0 for the oldest entry
and increases with time, and that's how the GNU implementation
behaves indeed.

The libedit implementation, on the other hand, returns 1 for the
newest entry and increases going back in time.

(christos)

We now use cpu_intr_p() all the time.

(christos)

From scole_mail:
So here is a patch to get basic ski console output working.  The ski
simulator was decoding the wrong registers in ssccnputc() due to
automagically inlined ssc() which contains a "break" simulated system
call.

The ski loader "skiload" has almost exactly the same inline assembly
call for ssc(), but for whatever reason, (maybe ssc() and
ski_cons_putchar() are in different files?), the ssc() function didn't
get inlined and I/O worked fine.

(christos)

Avoid taking locks during interrupts and explain why we are doing it this way.

(christos)

s/protected/libedit_private/g

(christos)

Instead of compiling all the source files together in one big file, use
protected visibility to achieve the same effect.

(christos)

Elide gcc warning about intermediate const casts caused by visibility change.

(christos)

GNU readline(3) regards history chronologically, that is, from the
perspective of the dawn of time, so "next" means "newer" and "previous"
means "older".  Libedit, by contrast, uses reverse chronology and
regards history from the perspective of the present, such that "next"
means "longer ago" and "previous" means "not so long ago".

The following patch fixes previous_history() and next_history()
as proposed by Bastian Maerkisch.

But there is a related problem demonstrated by Bastian's regression
tests that his patch did not fix:  next_history() can advance not
only to the newest entry, but beyond it, which core libedit cannot
do.  So that feature must be implemented locally in readline.c.

With that, the last of Bastians tests is fixed, test_movement_direction().

This patch also improves libedit documentation to more clearly state
what "previous" and "next" mean.  GNU readline documentation is
just as unclear, but we can't easily fix that since libedit doesn't
include its own readline.3 manual.

(Ingo Schwarze)

(christos)

The libedit implementation of history_get() also differs from the GNU
implementation:  libedit goes to the entry with the given number
stored in the HistEvent structure, while GNU subtracts history_base,
then advances that many entries from the oldest one.  If entries were
removed in between, GNU advances further than libedit.

The call sequence H_CURR, H_DELDATA, H_CURR, H_NEXT_EVDATA looks
weird, as if part of that must somehow be redundant.  But actually,
the user interface is so counter-intuitive that every single step
is really required.

- The first H_CURR is needed to be able to go back after an error.
- The H_DELDATA is needed to move the cursor.  Even though it takes
  a pointer to ev, that structure is not filled in when the call
  succeeds.  H_DELDATA only moves the cursor, it doesn't tell us
  the new event number.
- Consequently, the second H_CURR is required to get ev.num filled
  in.  But it doesn't return the data because ev has no field for
  that.
- So even though the cursor is already positioned correctly,
  H_NEXT_EVDATA is needed as the final step merely to get the data.

(Ingo Schwarze)

(christos)

Account for the CRC len (Jean-Jacques.Puig)

(christos)

Don't increment the reference count only when it was 0...
From Jean-Jacques.Puig

(christos)

In stiffle_history(), trim excessive entries from the history and advance
history_base like the GNU implementation does. (from Bastian Maerkisch)

(christos)

Fix stack allocation; limit delta to a quarter of the stack size. This should
get rid of the random aborts.

(christos)

Enable DEBUG_EXEC, if we have DEBUG (since it only fires on errors) and
disable the super verbose printing by protecting it against TRACE_EXEC.

(christos)

Catch up with other networking changes (John D. Baker)

(christos)

Move all the randomization inside kern_pax.c so we can control it directly.
Add debugging flags to be able to set the random number externally.

(christos)

fix logic (Ingo Schwarze)

(christos)

- don't require the lock if we are polling (early autoconf)
- unfold a line

(christos)

misc cleanups.

(christos)

mention libmalloc hack

(christos)

new acpica

(christos)

adjust to new acpica

(christos)

merge new acpica

(christos)

limit to gcc, requested by joerg.

(christos)

fix compilation for ppc.

(christos)

fix compilation

(christos)

prevent gcc from combining memset+malloc -> calloc inside calloc so that
we end up calling ourselves recursively.

(christos)

http://w1.fi/security/2016-1/0004-Reject-SET_CRED-commands-with-newline-characters-in-.patch
Many of the global configuration parameters are written as strings
without filtering and if there is an embedded newline character in the
value, unexpected configuration file data might be written.

This fixes an issue where wpa_supplicant could have updated the
configuration file global parameter with arbitrary data from the control
interface or D-Bus interface. While those interfaces are supposed to be
accessible only for trusted users/applications, it may be possible that
an untrusted user has access to a management software component that
does not validate the value of a parameter before passing it to
wpa_supplicant.

This could allow such an untrusted user to inject almost arbitrary data
into the configuration file. Such configuration file could result in
wpa_supplicant trying to load a library (e.g., opensc_engine_path,
pkcs11_engine_path, pkcs11_module_path, load_dynamic_eap) from user
controlled location when starting again. This would allow code from that
library to be executed under the wpa_supplicant process privileges.

(christos)

http://w1.fi/security/2016-1/0004-Reject-SET_CRED-commands-with-newline-characters-in-.patch
Most of the cred block parameters are written as strings without
filtering and if there is an embedded newline character in the value,
unexpected configuration file data might be written.

This fixes an issue where wpa_supplicant could have updated the
configuration file cred parameter with arbitrary data from the control
interface or D-Bus interface. While those interfaces are supposed to be
accessible only for trusted users/applications, it may be possible that
an untrusted user has access to a management software component that
does not validate the credential value before passing it to
wpa_supplicant.

This could allow such an untrusted user to inject almost arbitrary data
into the configuration file. Such configuration file could result in
wpa_supplicant trying to load a library (e.g., opensc_engine_path,
pkcs11_engine_path, pkcs11_module_path, load_dynamic_eap) from user
controlled location when starting again. This would allow code from that
library to be executed under the wpa_supplicant process privileges.

(christos)

http://w1.fi/security/2016-1/0003-Remove-newlines-from-wpa_supplicant-config-network-o.patch
Spurious newlines output while writing the config file can corrupt the
wpa_supplicant configuration. Avoid writing these for the network block
parameters. This is a generic filter that cover cases that may not have
been explicitly addressed with a more specific commit to avoid control
characters in the psk parameter.

(christos)

http://w1.fi/security/2016-1/0002-Reject-psk-parameter-set-with-invalid-passphrase-cha.patch
WPA/WPA2-Personal passphrase is not allowed to include control
characters. Reject a passphrase configuration attempt if that passphrase
includes an invalid passphrase.

This fixes an issue where wpa_supplicant could have updated the
configuration file psk parameter with arbitrary data from the control
interface or D-Bus interface. While those interfaces are supposed to be
accessible only for trusted users/applications, it may be possible that
an untrusted user has access to a management software component that
does not validate the passphrase value before passing it to
wpa_supplicant.

This could allow such an untrusted user to inject up to 63 characters of
almost arbitrary data into the configuration file. Such configuration
file could result in wpa_supplicant trying to load a library (e.g.,
opensc_engine_path, pkcs11_engine_path, pkcs11_module_path,
load_dynamic_eap) from user controlled location when starting again.
This would allow code from that library to be executed under the
wpa_supplicant process privileges.

(christos)

http://w1.fi/security/2016-1/0001-WPS-Reject-a-Credential-with-invalid-passphrase.patch
WPA/WPA2-Personal passphrase is not allowed to include control
characters. Reject a Credential received from a WPS Registrar both as
STA (Credential) and AP (AP Settings) if the credential is for WPAPSK or
WPA2PSK authentication type and includes an invalid passphrase.

This fixes an issue where hostapd or wpa_supplicant could have updated
the configuration file PSK/passphrase parameter with arbitrary data from
an external device (Registrar) that may not be fully trusted. Should
such data include a newline character, the resulting configuration file
could become invalid and fail to be parsed.

(christos)

new openssl

(christos)

merge conflicts

(christos)

add missing forward declaration for the STATIC= case.

(christos)

minor nits

(christos)

search for the proper variable in the sysroot case.

(christos)

move scsipi_strvis -> libkern:strnvisx()
change the prototype to match userland
fix sizes of strings passed to it

(christos)

Make it look more like rt2560.c

(christos)

eliminate static buffer with custom resizing code.

(christos)

fix typos from Pedro Giffuni @FreeBSD

(christos)

Add more MLINKS, sort

(christos)

Add wide versions of histedit functions
Remove dups

(christos)

Add more explicit xrefs

(christos)

More redirect tests, in particular, tests for redirects to/from
file descriptors outside the 0..9 range, and complex fd
reassignments.  Also test that the shell can cope with the
value of ulimit -n changing (downwards, up is harmless)
(Freom kre@)

(christos)

Fix handing of user file descriptors outside the 0..9 range.
Also, move (most of) the shell's internal use fd's to much
higher values (depending upon what ulimit -n allows) so they
are less likely to clash with user supplied fd numbers.  A future
patch will (hopefully) avoid this problem completely by dynamically
moving the shell's internal fds around as needed. (From kre@)

(christos)

merge conflicts

(christos)

new ntpd

(christos)

use "" so ${TEST_SH} is expanded.

(christos)

Provide the correct system Makefile path to the tools make. This is needed
because although the arch-specific make wrapper sets $MAKEFLAGS to include
the proper system Makefile path, configure clears $MAKEFLAGS before it invokes
$MAKE to figure out which dependency style to use. This made the build fail
during the gcc build.

(christos)

move section around.

(christos)

use variables that could be unused.

(christos)

mention the PR

(christos)

remove in %s\n", __func__ debugging

(christos)

Moved hack to ufs_lookup.c

(christos)

Split ufs_direnter futher and turn off tree-vrp for the broken function.

(christos)

For struct ifnet if_transmit.

(christos)

- merge the options descriptions, sort them.
- fix wrusage name.

(christos)

new editline.7 man page.

(christos)

new man page from Ingo Schwarze.

(christos)

Initialize patbuf (Ingo Schwarze)

(christos)

Pass the proper device_t to the attach hook.

(christos)

include stdio.h for NULL

(christos)

remove incorrect comment

(christos)

Simplify

(christos)

Fix tyop

(christos)

Fix error message.

(christos)

Introduce dt_bootfile() and use it to avoid hard-coded kernel values. Fixes
dtrace hang for kernels not named netbsd.

(christos)

We need a flag for WCONTINUED so that we can reset it... Fixes bash issue.

(christos)

- Adjust to the correct wait6 semantics (returns pid)
- Avoid race in setrlimit(2)

(christos)

Add 80211n ht frame.

(christos)

Add new firmware code.

(christos)

add rt2860

(christos)

Sync with OpenBSD

(christos)

Make RT 2860 for the if_ral_pci.c driver compile.
This work was done by Jeff Rizzo

(christos)

regen

(christos)

more ral devices from OpenBSD

(christos)

Sync with OpenBSD (add rt2860). Handle 32/64 memory bars,
some power management, more device matches.

(christos)

Add rt2860 now that it compiles.

(christos)

provide an empty DPRINTF

(christos)

Extend the "a" partition hack to also mean the first partition on the raid,
for non-disklabel based raidframe disks that need root.

(christos)

Add dkwedge_find_by_parent()

(christos)

Unmodified OpenBSD sources (except Ids)

(christos)

set the return value to the pid if we found one (from kre@)

(christos)

CID 1358680: Set umask before mkstemp

(christos)

CID 1358679: Fix memory leak.
XXX: pullup 7

(christos)

CID 1358678: Don't pass -1 to fdopen(3)

(christos)

CID 1358677: (Negative returns) tuck in poll_fd assignment in eloop_open()

(christos)

CID 1358676: Forward NULL.

(christos)

CID 1358675: Wrong variable test

(christos)