Link [ NetBSD | NetBSD OpenGrok source search | PR fulltext-search | Summary of daily snapshot builds | history of daily build result | pkgsrc commit viewer ]


   
        usage: [branch:branch] [user:user] [path@revision] keyword [... [-excludekeyword [...]]] (e.g. branch:MAIN sys/arch/arm, if_wm.c@1.234 )




switch to index mode

recent branches: MAIN (3h)  netbsd-8 (5d)  netbsd-10 (6d)  netbsd-9 (12d)  thorpej-ifq (176d)  thorpej-altq-separation (178d) 

2024-05-10 17:51:58 UTC Now

2018-12-10 19:29:41 UTC MAIN commitmail json YAML

make UFS_WAPBL_JLOCK_ASSERT() #ifdef DIAGNOSTIC, same as the underlying
function KASSERT(), so that it actually does something; fix code using
it to actually pass correct params, so that it compiles

remove UFS_WAPBL_JUNLOCK_ASSERT(), as that is inherently racy (it's
okay on those places if the rwlock is held by other lwp); depend
on the RW_ASSERT()/LOCKDEBUG inside rw_enter() to catch the case
with wapbl rwlock held by current lwp

(jdolecek)

2018-12-10 19:21:56 UTC MAIN commitmail json YAML

clarify how rw_{write,read,lock}_held() work; rw_write_held() actually
returns non-zero only if current lwp is the owner, the other two don't care
about owner; also warn that functions are not atomic, and thus should only
ever be used to assert that the lock is held

(jdolecek)

2018-12-10 17:21:21 UTC netbsd-7 commitmail json YAML

2018-12-10 17:20:03 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #1663):

bin/sh/parser.c: revision 1.152 (via patch)

PR bin/53712

Avoid crash from redirect on null compound command.

(martin)

2018-12-10 17:17:08 UTC netbsd-8 commitmail json YAML

2018-12-10 17:16:11 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by hannken in ticket #1133):

sys/dev/vnd.c: revision 1.270

Operation handle_with_strategy() also needs the
fstrans_start_lazy() / fstrans_done() bracket.

PR kern/53624 (dom0 freeze on domU exit)

(martin)

2018-12-10 16:28:52 UTC MAIN commitmail json YAML

need <sys/endian.h> (or arpa/inet.h) for ntohl() used in macros.

(christos)

2018-12-10 15:22:35 UTC MAIN commitmail json YAML

Operation handle_with_strategy() also needs the
fstrans_start_lazy() / fstrans_done() bracket.

PR kern/53624 (dom0 freeze on domU exit)

(hannken)

2018-12-10 15:08:23 UTC MAIN commitmail json YAML

2018-12-10 14:46:25 UTC MAIN commitmail json YAML

2018-12-10 14:32:04 UTC MAIN commitmail json YAML

do not abuse aprint_error for runtime error messages

(jakllsch)

2018-12-10 14:16:28 UTC MAIN commitmail json YAML

adjust for new QinHeng USB ID constants

(jakllsch)

2018-12-10 14:15:01 UTC MAIN commitmail json YAML

2018-12-10 14:14:20 UTC MAIN commitmail json YAML

rework QinHeng Electronics / WinChipHead IDs

(jakllsch)

2018-12-10 08:52:21 UTC netbsd-8 commitmail json YAML

Corrent CHANGES entry for 1129 (it's mfii(4) not mpii(4)).
Pointed out by Stephen Borrill

(bouyer)

2018-12-10 07:24:49 UTC MAIN commitmail json YAML

Improve error handling, doesn't matter a lot, but still.

(maxv)

2018-12-10 06:23:54 UTC MAIN commitmail json YAML

call pci_intr_release() when pci_intr_establish_xname() fails; I got confused
by the opposite conditionals compared to other drivers

found by Masanobu SAITOH

(jdolecek)

2018-12-10 03:58:30 UTC MAIN commitmail json YAML

Describe how unaccounted changes are detected without Star Trek references, for
everyone in 2018.

Thanks to maya & gdt

(sevan)

2018-12-10 00:31:45 UTC MAIN commitmail json YAML

Make i2c_acquire_bus() / i2c_release_bus() real symbols.

(thorpej)

2018-12-10 00:29:47 UTC MAIN commitmail json YAML

Remove incorrect printout of CH340/CH341 part.

CH341 and CH340 can't be differentiated by the chip's USB firmware version.

(jakllsch)

2018-12-10 00:22:14 UTC MAIN commitmail json YAML

Don't accumulate RX data into packets on CH341.

(jakllsch)

2018-12-10 00:03:11 UTC MAIN commitmail json YAML

Note the instance of the driver in register access trace debug messages.

(jakllsch)

2018-12-09 23:18:41 UTC MAIN commitmail json YAML

New wpa_supplicant out.

(maya)

2018-12-09 23:05:02 UTC MAIN commitmail json YAML

Handle the case when a CPU is assigned to a set it is already a member of.
Previously this would trigger an assertion failure.

(mlelstv)

2018-12-09 21:39:48 UTC MAIN commitmail json YAML

2018-12-09 20:45:37 UTC MAIN commitmail json YAML

for direct map case, avoid PGO_NOBLOCKALLOC when writing, it makes
genfs_getpages() return unallocated pages using the zero page and
PG_RDONLY; the old code relied on fault logic to get it allocated, which
the direct case can't rely on

instead just allocate the blocks right away; pass PGO_JOURNALLOCKED
so that code wouldn't try to take wapbl lock, this code path is called
with it already held

this should fix KASSERT() due to PG_RDONLY on write with wapbl

towards resolution of PR kern/53124

(jdolecek)

2018-12-09 20:33:04 UTC MAIN commitmail json YAML

update comment - PGO_JOURNALLOCKED now supported for 'get' too

(jdolecek)

2018-12-09 20:32:37 UTC MAIN commitmail json YAML

support flag PGO_JOURNALLOCKED also for genfs_getpages()

(jdolecek)

2018-12-09 20:29:53 UTC MAIN commitmail json YAML

2018-12-09 19:21:17 UTC MAIN commitmail json YAML

try to detach on shutdown; for now the only practical reason is to test that
the driver detach paths work

(jdolecek)

2018-12-09 19:16:10 UTC MAIN commitmail json YAML

convert to pci_intr_alloc() to possibly allow MSI/MSI-X; has no effect
on my system, where the device only supports INTx

(jdolecek)

2018-12-09 19:03:42 UTC MAIN commitmail json YAML

2018-12-09 18:01:01 UTC MAIN commitmail json YAML

2018-12-09 17:52:48 UTC MAIN commitmail json YAML

Address of packed member might not be aligned.

(christos)

2018-12-09 17:33:38 UTC MAIN commitmail json YAML

comment out unused.

(christos)

2018-12-09 16:00:40 UTC MAIN commitmail json YAML

sparc64 doesn't have a scalar bus_space_handle_t, so cope with this.
Also, add a comment about why we're using the dummy / nil space handle
in the first place.

(thorpej)

2018-12-09 15:08:06 UTC MAIN commitmail json YAML

2018-12-09 11:52:11 UTC MAIN commitmail json YAML

remove 'NOT WORKING' for ena(4) - while it was not yet confirmed working
on x86, it already is confirmed working on aarm64 so chances are high
it will work for x86 too

(jdolecek)

2018-12-09 11:49:07 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

XXX due to 2008-01-17 '10 gigabit Chelsio cards now compile and work, although
XXX not very well yet' commit this looks like having worked in past, but since
XXX ~2010 received only mechanical updates, and currently it's unreferenced
XXX and uncompilable - does it make sense to keep the driver around?

(jdolecek)

2018-12-09 11:22:35 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

(jdolecek)

2018-12-09 11:14:02 UTC MAIN commitmail json YAML

2018-12-09 11:12:58 UTC MAIN commitmail json YAML

make compile on 64-bit archs after acpi_mem ar_length was changed
from uint32_t to bus_size_t in rev. 1.77 of acpivar.h

(jdolecek)

2018-12-09 10:38:54 UTC MAIN commitmail json YAML

put back the intr establish to ath_pci_resume() to avoid possibility of
functionality change, but add XXX comment that it shouldn't be necessary

(jdolecek)

2018-12-09 10:06:56 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

upon code inspection, remove intr re-establish from ath_pci_resume() -
not needed to re-establish interrupt there, no other driver does this,
and very likely it would actually fail nowadays

(jdolecek)

2018-12-09 00:45:18 UTC MAIN commitmail json YAML

remove XXXKALSR that became MI.

(mrg)

2018-12-08 23:24:02 UTC MAIN commitmail json YAML

Add engines infrastructure, not hooked to the build:
1. sets needs to be fixed
2. need to decide if I am going to add engine.so.MAJOR or use engine.so
  like OpenSSL wants
3. padlock is MD (x86) needs asm to be added, and conditionally built

(christos)

2018-12-08 22:38:06 UTC MAIN commitmail json YAML

2018-12-08 22:35:45 UTC MAIN commitmail json YAML

src/crypto/external/bsd/openssl/dist/CHANGES@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/Configure@1.22 / diff / nxr@1.22
src/crypto/external/bsd/openssl/dist/NEWS@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/README@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/apps/ca.c@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/apps/ocsp.c@1.17 / diff / nxr@1.17
src/crypto/external/bsd/openssl/dist/apps/openssl.cnf@1.7 / diff / nxr@1.7
src/crypto/external/bsd/openssl/dist/apps/s_server.c@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/apps/speed.c@1.16 / diff / nxr@1.16
src/crypto/external/bsd/openssl/dist/crypto/bio/bio_lib.c@1.6 / diff / nxr@1.6
src/crypto/external/bsd/openssl/dist/crypto/bio/bss_log.c@1.10 / diff / nxr@1.10
src/crypto/external/bsd/openssl/dist/crypto/bn/asm/x86_64-gcc.c@1.10 / diff / nxr@1.10
src/crypto/external/bsd/openssl/dist/crypto/bn/bn_exp.c@1.18 / diff / nxr@1.18
src/crypto/external/bsd/openssl/dist/crypto/bn/bn_lib.c@1.10 / diff / nxr@1.10
src/crypto/external/bsd/openssl/dist/crypto/cryptlib.c@1.13 / diff / nxr@1.13
src/crypto/external/bsd/openssl/dist/crypto/ec/ec_ameth.c@1.8 / diff / nxr@1.8
src/crypto/external/bsd/openssl/dist/crypto/engine/eng_devcrypto.c@1.3 / diff / nxr@1.3
src/crypto/external/bsd/openssl/dist/crypto/evp/e_aes.c@1.17 / diff / nxr@1.17
src/crypto/external/bsd/openssl/dist/crypto/rand/rand_unix.c@1.10 / diff / nxr@1.10
src/crypto/external/bsd/openssl/dist/crypto/rand/randfile.c@1.11 / diff / nxr@1.11
      :
(more 21 files)
Merge conflicts

(christos)

2018-12-08 21:14:37 UTC MAIN commitmail json YAML

2018-12-08 17:46:14 UTC MAIN commitmail json YAML

2018-12-08 17:07:27 UTC MAIN commitmail json YAML

2018-12-08 15:31:30 UTC MAIN commitmail json YAML

support multi-vector MSI-X

tested and confirmed working by Masanobu SAITOH on C3000

(jdolecek)

2018-12-08 15:04:40 UTC MAIN commitmail json YAML

2018-12-08 15:02:06 UTC MAIN commitmail json YAML

acpimcfg_configure_bus_cb can support 16-bit addresses now

(jmcneill)

2018-12-08 14:57:11 UTC MAIN commitmail json YAML

Don't call callout_halt() if it's not initialzied.

(msaitoh)

2018-12-08 14:55:53 UTC MAIN commitmail json YAML

2018-12-08 13:31:32 UTC MAIN commitmail json YAML

Don't try to handle interrupts for a detached device. Should fix
panic on shutdown reported by Stefan Hertenberger on current-users.

(bouyer)

2018-12-08 12:27:57 UTC netbsd-8 commitmail json YAML

2018-12-08 12:24:18 UTC netbsd-8 commitmail json YAML

Apply patch, requested by tsutsui in ticket #1132:

Different solution for the fix in

sys/compat/linux/common/linux_socket.c rev 1.140

The solution in -current could not be directly used as it required a kernel
version bump and broke the ABI. Work around it differently here.

Fixes linux emulation of sendto(2), PR 53103.

(martin)

2018-12-08 12:18:37 UTC MAIN commitmail json YAML

2018-12-08 12:17:14 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #1131):

sys/dev/pci/mpiireg.h: revision 1.2
sys/dev/pci/mfii.c: revision 1.3
share/man/man4/mpii.4: revision 1.3
share/man/man4/mpii.4: revision 1.4
sys/dev/pci/mpii.c: revision 1.15
sys/dev/pci/mpii.c: revision 1.16
sys/dev/pci/mpii.c: revision 1.17
sys/dev/pci/mpii.c: revision 1.18

Update the mpii(4) driver to the latest OpenBSD version.

This adds support for the SAS3xxx LSI controllers, and this also makes the
driver MP-safe.

adjust mfii.c for changes in mpiireg.h

Tested with a
mpii0: SMC2008-IR, firmware 9.0.0.0 IR, MPI 2.0
Update for the new mpii(4) driver, mostly from OpenBSD.

Also tell the scsi layer that we are MPSAFE

Remove trailing whitespace

NULL-terminate mpii_devices[], this is the end condition of the loop
in mpii_match(). Noticed by Mike Pumford

There's no sensors for physical disks so don't try to detach them.

(martin)

2018-12-08 12:10:22 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #1130):

sys/dev/pci/if_bge.c: revision 1.320
sys/dev/pci/if_bgevar.h: revision 1.24
sys/dev/pci/if_bge.c: revision 1.317
sys/dev/pci/if_bgereg.h: revision 1.94

More TSO4 fixes, from the freebsd driver:
- the chip doens't want the lenght of options, but the complete lenght of
  ip headers (ip + tcp + options). Fix this for the BGE_IS_5717_PLUS()
  and BGE_IS_5705_PLUS() cases; FreeBSD doens't cover the last case so
  leave it as is for now. This fixes checksum failures for heavy transfers.
- It looks like the transmit engine hangs if the TCP segment crosses a 4GB
  boundary. FreeBSD fixes it by mapping everything below 4GB; instead
  try detect when this happens and do the bounce only when needed.

With these fixes I could transfers 3GB images over ftp at gigabit speed
(112MB/s with wget) without problems. Tested on a
bge0 at pci4 dev 0 function 0: Broadcom BCM5720 Gigabit Ethernet
bge0: APE firmware NCSI 1.4.22.0
bge0: interrupting at msi1 vec 0
bge0: HW config 002b1194, 00006014, 0002aa38, 00000000 0000000c
bge0: ASIC BCM5720 A0 (0x5720000), Ethernet address d0:94:66:8b:9c:18
bge0: setting short Tx thresholds
brgphy0 at bge0 phy 1: BCM5720C 1000BASE-T media interface, rev. 0

-

Don't destroy the dma maps if we're not disabling the adapter, avoids
a KASSERT() when bus_dmamap_destroy() is called from interrupt
context via bge_watchdog()

Set IFF_OACTIVE only when bge_encap() fails on adapter ressource shortage.
Otherwise we may set IFF_OACTIVE while no transmit is in progress, and
nothing will clear it.

If bus_dmamap_load_mbuf() fails with EFBIG, m_defrag() the chain and retry.
Refine the check for the 4GB boundary workaround (a fragment should also
not cross the boundary), and do it only for TSO.

If bge_encap() fails and didn't set IFF_OACTIVE, drop the packet.

Bring in more hardware bug workarounds from freebsd.

With these it seems that a BCM5720 A0 can survive a few hours of internet
load with TSO4 enabled.

(martin)

2018-12-08 06:53:11 UTC MAIN commitmail json YAML

Add machdep.cpu.frequency.available node to support estd.

While the RPI can run at many intermediate clock frequencies,
this is sufficient for estd and is known to work with every
firmware revision.

(mlelstv)

2018-12-08 01:47:22 UTC MAIN commitmail json YAML

2018-12-08 01:28:27 UTC MAIN commitmail json YAML

Add a draft manual for ztest(1), based on the comments from zfstest.c (WIP).

(sevan)

2018-12-07 22:22:12 UTC MAIN commitmail json YAML

add optional hook for intr establish when active port is attached, export
ahci_intr_port() in form suitable for interrupt hanlder, and probe for GHC
MRSM flag as courtesy for use by the intr hook

towards multi-vector MSI/MSI-X support

(jdolecek)

2018-12-07 21:28:03 UTC MAIN commitmail json YAML

save some notes from my two years old hacking on ext3/ext4 support with
our ext2fs

(jdolecek)

2018-12-07 19:41:30 UTC netbsd-8 commitmail json YAML

Annotate ticket #1129 for furhter fixes

(martin)

2018-12-07 19:38:54 UTC netbsd-8 commitmail json YAML

Fixup pullups from ticket #1129:

sys/arch/amd64/conf/XEN3_DOM0 rev 1.159
src/sys/arch/i386/conf/XEN3PAE_DOM0 rev 1.8 (via patch)

Add mffii(4)

(martin)

2018-12-07 19:01:11 UTC MAIN commitmail json YAML

Add speeds B500000 to B4000000 in increments of 500000.

Motivated by picocom checking for the existance of these at compile
time, and therefor previously not being able able to use picocom to
access the consoles of modern Rockchip SoCs (for example RK3399) running
at B1500000.

(jakllsch)

2018-12-07 18:46:28 UTC MAIN commitmail json YAML

add simple stack overflow checker for debugging

(ryo)

2018-12-07 18:45:13 UTC MAIN commitmail json YAML

reindent "standard speeds" in preparation for 7-digit bauds

(jakllsch)

2018-12-07 18:27:03 UTC MAIN commitmail json YAML

modifying curlwp->l_md_ktf, curlwp->l_md_cpacr, and curlwp should be protected by a critical section.

(ryo)

2018-12-07 17:58:29 UTC MAIN commitmail json YAML

2018-12-07 17:57:22 UTC MAIN commitmail json YAML

Add new entry in TODO.sanitizers for NetBSD tar(1) enhancement request

Added:
- NetBSD tar: handle character escaping in file names (\\ \), needed in
  check-lld (lld::reproduce-backslash.s)

(kamil)

2018-12-07 17:56:42 UTC MAIN commitmail json YAML

fix a paste-o in a panic message

(jakllsch)

2018-12-07 17:13:56 UTC netbsd-8 commitmail json YAML

2018-12-07 17:11:38 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #1129):

sys/arch/amd64/conf/XEN3_DOM0: revision 1.159
sys/arch/amd64/conf/GENERIC: revision 1.508
sys/arch/i386/conf/ALL: revision 1.458
sys/dev/ic/mfi.c: revision 1.60
sys/dev/pci/mpiireg.h: revision 1.1
distrib/sets/lists/man/mi: revision 1.1628
sys/dev/pci/mfii.c: revision 1.1,1.2 (adapted)
sys/arch/i386/conf/GENERIC: revision 1.1194
sys/dev/pci/mpii.c: revision 1.13
sys/dev/ic/mfireg.h: revision 1.9
share/man/man4/mfii.4: revision 1.1
share/man/man4/Makefile: revision 1.673 (patch)
sys/dev/pci/files.pci: revision 1.410
share/man/man4/mfii.4: revision 1.2
sys/arch/amd64/conf/ALL: revision 1.108
sys/arch/i386/conf/XEN3PAE_DOM0: revision 1.8 (patch, in XEN3_DOM0)

Add some definitions from OpenBSD, needed by the upcoming mfii driver.
No functionnal change.

-

Move registers definitions to a separate file, needed for the upcomning mpii
driver. No functionnal change.

-

Add mpii(4), a driver for LSI Megaraid Fusion controllers.
Ported from OpenBSD. This driver is MP-safe.

Note that the earlier fusion controllers (Megaraid 2208, codenamed Thunderbold)
are also supported by mfi(4). mpii will take precedence if both drivers
are enabled.

Tested on a
mfii0 at pci6 dev 0 function 0: "PERC H740P Adapter ", firmware 50.3.0-1512, 819
2MB cache
mfii0: interrupting at ioapic2 pin 2
scsibus0 at mfii0: 64 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <DELL, PERC H740P Adp, 5.03> disk fixed
sd0: fabricating a geometry
sd0: 99 GB, 102399 cyl, 64 head, 32 sec, 512 bytes/sect x 209714688 sectors
sd0: tagged queueing
sd1 at scsibus0 target 1 lun 0: <DELL, PERC H740P Adp, 5.03> disk fixed
sd1: fabricating a geometry
sd1: 22254 GB, 22788608 cyl, 64 head, 32 sec, 512 bytes/sect x 46671069696 sectors
sd1: fabricating a geometry

It supports bioctl(8) ioctls, as well as sensors for the BBU and logical
drives.

Sponsored by LIP6.

-

Add my name in copyright list

-

add a man page for the new mpii, mostly from OpenBSD.

-

Sort SEE ALSO. Fix date. Whitespace fixes.

(martin)

2018-12-07 16:36:30 UTC MAIN commitmail json YAML

Add some ZFS related acronyms.
While here, replace spaces with a tab for ZFS entry.

(sevan)

2018-12-07 15:47:11 UTC MAIN commitmail json YAML

Add an option to have a static kernel memory layout. This option is
disabled by default - that is to say, KASLR remains enabled by default.

(maxv)

2018-12-07 14:59:19 UTC MAIN commitmail json YAML

interlock isn't taken when cleaning up.

(mlelstv)

2018-12-07 14:47:24 UTC MAIN commitmail json YAML

inet6: match NS nonce to any interface

This allows the same address to exist on many interfaces on the same
prefix, matching the inet behaviour.

(roy)

2018-12-07 13:28:54 UTC netbsd-8 commitmail json YAML

2018-12-07 13:27:19 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1128):

sys/dev/pci/pcivar.h: revision 1.113
sys/dev/pci/pci.c: revision 1.153

  Save control registers in PCI-X, PCIe, MSI and MSI-X capability area when
suspend and restore them when resume. For PCIe capabilities register, it's
required to check the existence of each register to not to write the next area.

  This change fixes a stability of suspend/resume.

(martin)

2018-12-07 13:23:49 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #1127):

bin/sh/var.h: revision 1.38 (via patch)
bin/sh/var.c: revision 1.72
bin/sh/sh.1: revision 1.211 (via patch)

Alter a design botch when magic (self modifying) variables
were added to sh ... in other shells, setting such a variable
(for most of them) causes it to lose its special properties,
and act the same as any other variable.  I had assumed that
was just implementor laziness...  I was wrong.

From now on the NetBSD shell will act like the others, and if vars
like HOSTNAME (and SECONDS, etc) are used as variables in a script
or whatever, they will act just like normal variables (and unless
this happens when they have been made local, or as a variable-assignment
as a prefix to a command, the special properties they would have had
otherwise are lost for the remainder of the life of the (sub-)shell
in which the variables were set).

Importing a value from the environment counts as setting the
value for this purpose (so if HOSTNAME is set in the environment,
the value there will be the value $HOSTNAME expands to).
The two exceptions to this are LINENO and RANDOM.  RANDOM
needs to be able to be set to (re-)set its seed.  LINENO needs to
be able to be set (at least in the "local" command) to achieve
the desired functionality.  It is unlikely that any (sane) script
is going to want to use those two as normal vars however.

While here, fix a minor bug in popping local vars (fn return) that need
to notify the shell of changes in value (like PATH).
Change sh(1) to reflect this alteration.  Also add doc of the
(forgotten) magic var EUSER (which has been there since the others
were added), and add a few more vars (which are documented
in other places in sh(1) - like ENV) into the defined or used
variable list (as well as wherever else they appear).

XXX pullup -8

(martin)

2018-12-07 13:14:42 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #1126):

bin/sh/alias.c: revision 1.19

Fix the worst of the bugs in alias processing.  This has been in sh
since this code was first imported (May 1994) (ie: before 4.4-Lite)

There is (much) more coming soon (the big ugly comment is going away).

This one has been separated out, as it can easily cause sh
core dumps, so needs:
XXX pullup-8

(the other changes to aliases probably will not get that.)

(martin)

2018-12-07 13:12:02 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #1125):

bin/sh/redir.c: revision 1.61

Fix the <> redirection operator, which has been broken since it was
first implemented in response to PR bin/4966  (PR Feb 1998, fix Feb 1999).

The file named should not be truncated.

No other shell truncates the file (<> was added to FreeBSD sh in Oct 2000,
and did not include O_TRUNC) and POSIX certainly does not suggest that
should happen (just that the file is to be created if it does not exist.)

Bug pointed out in off-list e-mail by Martijn Dekker

(martin)

2018-12-07 13:09:14 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by sevan in ticket #1124):

usr.bin/vmstat/vmstat.1: revision 1.21
usr.bin/vmstat/vmstat.1: revision 1.22

Suggest kernhist(9) which is required for vmstat -u and -U
Drop Pp before Bl while here.

-

Document vmstat -w -1 is accepted.
via FreeBSD.

(martin)

2018-12-07 09:36:26 UTC MAIN commitmail json YAML

- defflag PPB_USEINTR
- Print "interrupting at "

(msaitoh)

2018-12-07 09:29:01 UTC MAIN commitmail json YAML

tests: check error messages strictly

(ozaki-r)

2018-12-07 09:28:31 UTC MAIN commitmail json YAML

tests: reduce repeated phrases... (NFC)

(ozaki-r)

2018-12-07 09:11:04 UTC MAIN commitmail json YAML

ipsecif(4) should not increment drop counter by errors not related to if_snd. Pointed out by ozaki-r@n.o, thanks.

(knakahara)

2018-12-07 08:52:43 UTC MAIN commitmail json YAML

No functional change. OK'd by nonaka:
- Use correct macro.
- Don't use magic number.

(msaitoh)

2018-12-07 08:28:44 UTC MAIN commitmail json YAML

xHCI uses BAR0 to map memory space. If a chip has MSI-X capability and it
points to BAR0, reserve the space. Almost the same as nvme_pci.c.

XXX Is it possible to make a nice API?

(msaitoh)

2018-12-07 05:09:39 UTC MAIN commitmail json YAML

ipsecif(4) support input drop packet counter.

(knakahara)

2018-12-06 19:17:13 UTC MAIN commitmail json YAML

Summary: Align softfloat float128 with libgcc.

While libgcc adapts its float128 data structure to the endianness of
the architecture, the softfloat code in libc didn't.  With both of
them handling the same values, softfloat must follow the toolchain.

OK: riastradh

(tih)

2018-12-06 19:15:35 UTC MAIN commitmail json YAML

Document the source of load average figures.

(sevan)

2018-12-06 19:01:53 UTC MAIN commitmail json YAML

Add a statement about uptime's relation to w(1).

(sevan)

2018-12-06 18:36:06 UTC MAIN commitmail json YAML

Expose CACHE_LINE_SIZE (and COHERENCY_UNIT) so that fstat can work

(skrll)

2018-12-06 17:44:28 UTC MAIN commitmail json YAML

Simplify, use _pi instead of modulos, no real functional change.

(maxv)

2018-12-06 17:26:18 UTC MAIN commitmail json YAML

Fix inconsistency, these are indexes and not types, no real functional
change.

(maxv)

2018-12-06 14:22:48 UTC MAIN commitmail json YAML

Add BUAG, DCIM (2x), and SDP

(ginsbach)

2018-12-06 13:51:43 UTC MAIN commitmail json YAML

Typo fix (Geoff Wing)

(christos)

2018-12-06 13:25:02 UTC MAIN commitmail json YAML

Apply FreeBSD ix-3.3.6.tar.gz's change to NetBSD. Tested on C3000 and X550-T1,
but not tested on Xeon D:
- Add firmware recovery mode for X550, X550A(Xeon D) and X550EM (C3000):
  - FreeBSD always set IXGBE_FEATURE_RECOVERY_MODE without checking the
    NVM image version. We compare it against 2.0 to not to make new callout and
    not to call extra atomic operations.
  - In some FreeBSD's sysctl functions, atomic_load_acq_int() is called
    before a null pointer check. We call it after null pointer check.
  - Before calling atomic_load_acq_uint(), check adapter->feat_en flags
    to save atomic operation call.
  - We don't check recovery_mode in ixgbe_set_sysctl_value() because this
    function doesn't touch any hardware register.
  - NetBSD don't have FreeBSD's atomic_load_acq_int()-like function, so do it
    with membar_sync(). Thanks riastradh@ for the advice.
- FreeBSD's ix-3.3.6 changed ixgbe_enable_aim from TRUE to FALSE, but we will
  keep it as TRUE because we have already fixed some bugs.
- Remove IXGBE_DEV_ID_82599_LS(0x154f) support again. I don't know why. This
  was added in ix-3.2.18.tar.gz(NetBSD: ixgbe_82599.c rev. 1.20) and removed in
  ix-3.3.6.tar.gz.
- On X550EMU, use ixgbe_identify_sfp_module_X550em() instead of
  ixgbe_identify_module_generic(). ixgbe_identify_sfp_module_X550em() has
  extra check (e.g. exclude 1G copper).
- if_sriov.c's change doesn't affect to NetBSD because we don't support
  SR-IOV PF function.

(msaitoh)

2018-12-06 10:00:40 UTC MAIN commitmail json YAML

We have component names as counted strings (cn_nameptr, cn_namelen) but
ZFS expects a null-terminated name.

Always create a copy with PNBUF_GET()/strlcpy()/PNBUF_PUT().

For LOOKUP use a small buffer on stack and allocate/free compomnent names
longer than 30 chars.

(hannken)

2018-12-06 09:58:52 UTC MAIN commitmail json YAML

Add missing ZFS_OBJ_HOLD_ENTER() / ZFS_OBJ_HOLD_EXIT() to zfs_zget_cleaner().

(hannken)

2018-12-06 06:29:56 UTC MAIN commitmail json YAML

Correct handling of minval > maxval in strtonum(3)

The original implementation in OpenBSD returns "invalid" and avoids reading
the input string. The replaced behavior was interpreting the input string
ignoring the invalid arguments.

(kamil)

2018-12-06 01:42:20 UTC MAIN commitmail json YAML

2018-12-05 23:42:23 UTC MAIN commitmail json YAML

Document vmstat -w -1 is accepted.
via FreeBSD.

(sevan)

2018-12-05 22:42:55 UTC MAIN commitmail json YAML

Add CPU performance counter support

(jmcneill)

2018-12-05 22:42:27 UTC MAIN commitmail json YAML

Add needs-flag to tprof_armv8.c

(jmcneill)

2018-12-05 22:25:38 UTC MAIN commitmail json YAML

evert previous, linux build problem confirmed fixed by
update to mkinit.sh (to 1.10).

Or more correctly, revert & fix - turns out that there was an off by one
(failure to adjust for other changes -- in a value printed by debug mode
trace output).

NFC.

(kre)

2018-12-05 21:43:33 UTC MAIN commitmail json YAML

2018-12-05 21:15:20 UTC MAIN commitmail json YAML

Remove trailing whitespace. Remove comma for better readability.

(wiz)

2018-12-05 19:56:49 UTC MAIN commitmail json YAML

no more need for get_expose_address() here.

(christos)

2018-12-05 18:16:51 UTC MAIN commitmail json YAML

As discussed in tech-kern:

- make sysctl kern.expose_address tri-state:
0: no access
1: access to processes with open /dev/kmem
2: access to everyone
  defaults:
0: KASLR kernels
1: non-KASLR kernels

- improve efficiency by calling get_expose_address() per sysctl, not per
  process.

- don't expose addresses for linux procfs

- welcome to 8.99.27, changes to fill_*proc ABI

(christos)

2018-12-05 14:45:59 UTC MAIN commitmail json YAML

Remove trailing whitespace.

(wiz)

2018-12-05 14:44:54 UTC MAIN commitmail json YAML

Add some performance related acronyms from Brendan Gregg's USE Method: Rosetta
Stone of Performance Checklists along with alternatives from IBM documentation
(CPC)
http://www.brendangregg.com/USEmethod/use-rosetta.html

(sevan)

2018-12-05 10:38:22 UTC MAIN commitmail json YAML

There's no sensors for physical disks so don't try to detach them.

(bouyer)

2018-12-05 10:35:14 UTC MAIN commitmail json YAML

Suggest kernhist(9) which is required for vmstat -u and -U
Drop Pp before Bl while here.

(sevan)

2018-12-05 09:34:46 UTC MAIN commitmail json YAML

build fix for M68020,M68030. gcc complains about the local typedef that
isn't used.

(mlelstv)

2018-12-05 09:20:18 UTC MAIN commitmail json YAML

Use printf, rather than echo (via echo redefined as a function that
uses printf for simplicity).

This script runs using the build host's shell, and echo, and so must
deal with all of the absurdity that different versions of echo dumb
upon us.

This is the underlying cause of the linux build failure that gson@ reported.

(kre)

2018-12-05 06:51:16 UTC MAIN commitmail json YAML

note atactl auto vendor (micron) support.

(mrg)

2018-12-05 06:49:54 UTC MAIN commitmail json YAML

"smart status" already obtains the ata parameters to check if smart
is actually supported, so we can attempt to guess a vendor smart
table from the model name.  add basic support for all the micron /
crucial disk names i could find, and add a couple more micron
specific values.

XXX: probably should add regex support for matching, and probably
    should be more restrictive with the current matches.

(mrg)

2018-12-05 05:52:23 UTC MAIN commitmail json YAML

It's WSATTR_UNDERLINE, not WS_UNDERLINE.

(mlelstv)

2018-12-05 03:14:28 UTC MAIN commitmail json YAML

NFC (except that it should, I am guessing, fix compilation on
some versions of liux) - DEBUG mode change:  Delete a (relatively new)
trace point (temporarily anyway) which mkinit (a script run using the
host's /bin/sh) apparently cannot handle correctly on (some release of)
linux (it is fine with the NetBSD shell).

I don't know which linux version has a shell with this problem
(or whether it is a mkinit issue that only works by fluke on NetBSD)

Problem reported by gson@

(kre)

2018-12-05 02:48:05 UTC MAIN commitmail json YAML

Oops, this is 2018, not 2017 ... cut&paste  (affects just copyright notice)

(kre)

2018-12-05 02:45:06 UTC MAIN commitmail json YAML

Add a new test program to test the "intermediate" shell built in
utilities.  That is, not the low level ones that look like syntax,
but aren't: break/continue/return; not those which are really
just external programs that are built in for efficiency (printf,
test, and kill - though kill really needs to be built in) - those
should all have separate test programs (there is a test here for the
built-in echo, as that is an entirely different thing to /bin/echo);
and also not those for which there are other tests because of the
nature of the built-in (like exit, wait, shift, ...).  Lastly not
"times" either as that just seems to be too hard to test rationally.

There is a test (well, framework) for ulimit and there's also t_ulimit.sh
one of those should go, but I am not yet sure which is the best way
to reconcile things.

Note: many (in fact) most of the test cases added here are either
entirely empty (no tests at all, beyond testing that the built-in is
in fact a shell built-in) or only very rudimentary tests - assistance
in fleshing those out would be welcome (the boilerplate is all here,
all that is needed is some actual tests to run...)

(kre)

2018-12-04 22:06:37 UTC MAIN commitmail json YAML

Stop mangling __func__ for C++11 and newer

Drop local logic between GCC 2.4 and GCC 2.6 that used __PRETTY_FUNCTION__.
This caused __func__ to be redefined for all C++ programs and use a
different behavior than intended by the compiler (Clang and GCC).
__PRETTY_FUNCTION__ prints all the prototype not just function name,
contrary to __FUNCTION__ and __func__.

__func__ is now an integral part of C99 and C++11, shipped by a compiler.

This change aligns the behavior of C++ programs using __func__ to other
Operating Systems. The difference caused unnecessary fallout in regression
test suites in projects (LLVM, fish, ...).

(kamil)

2018-12-04 21:16:54 UTC MAIN commitmail json YAML

inet6: remove needless ifa_release.

(roy)

2018-12-04 21:01:48 UTC MAIN commitmail json YAML

inet6: use one function for nd6_dad_input

Having different ones for NA and NS is a bit wasteful.

(roy)

2018-12-04 20:46:56 UTC MAIN commitmail json YAML

inet6: simplify NA DaD checking

(roy)

2018-12-04 19:54:02 UTC MAIN commitmail json YAML

NULL-terminate mpii_devices[], this is the end condition of the loop
in mpii_match(). Noticed by Mike Pumford

(bouyer)

2018-12-04 19:34:27 UTC MAIN commitmail json YAML

disable MSI-X for time being since it's not working; allow only MSI
and INTx which both are confirmed working

(jdolecek)

2018-12-04 19:27:22 UTC MAIN commitmail json YAML

Hypothetically speaking, if one were to want to compile a

'no options MULTIPROCESSOR'

kernel, these files may trip up the build.

Fix them by moving around the #defines as originally intended.

No Functional Changes.

(cherry)

2018-12-04 19:22:42 UTC MAIN commitmail json YAML

Stop panic()ing on a UP system.

The reason for the panic is that the cpu_attach() doesn't run to
completion because it thinks it's run past maxcpus (which in the case
of UP), is 1.

This is because on x86 at least, mi_cpu_attach() is called *before*
configure() (and thus the cpu_match()/cpu_attach() pair). Thus ncpu
has already been incremented by the time MD cpu_attach() is called.

Fix this.

(cherry)

2018-12-04 19:18:44 UTC netbsd-7-0 commitmail json YAML

2018-12-04 19:18:12 UTC netbsd-7-0 commitmail json YAML

Pull up following revision(s) (requested by maxv in ticket #1662):

sys/arch/amd64/amd64/machdep.c: revision 1.321

Fix stack info leak. There is a big padding in struct sigframe_siginfo.

[  224.006287] kleak: Possible leak in copyout: [len=920, leaked=92]
[  224.016977] #0 0xffffffff80224d0a in kleak_note <netbsd>
[  224.026268] #1 0xffffffff80224d8a in kleak_copyout <netbsd>
[  224.026268] #2 0xffffffff802224b5 in sendsig_siginfo <netbsd>
[  224.036261] #3 0xffffffff80b51564 in sendsig <netbsd>
[  224.046475] #4 0xffffffff80b51282 in postsig <netbsd>
[  224.046475] #5 0xffffffff80b2fc5d in lwp_userret <netbsd>
[  224.056273] #6 0xffffffff8025a951 in mi_userret <netbsd>
[  224.066277] #7 0xffffffff8025ab89 in syscall <netbsd>

(martin)

2018-12-04 19:17:46 UTC netbsd-7-1 commitmail json YAML

2018-12-04 19:17:24 UTC netbsd-7-1 commitmail json YAML

Pull up following revision(s) (requested by maxv in ticket #1662):

sys/arch/amd64/amd64/machdep.c: revision 1.321

Fix stack info leak. There is a big padding in struct sigframe_siginfo.

[  224.006287] kleak: Possible leak in copyout: [len=920, leaked=92]
[  224.016977] #0 0xffffffff80224d0a in kleak_note <netbsd>
[  224.026268] #1 0xffffffff80224d8a in kleak_copyout <netbsd>
[  224.026268] #2 0xffffffff802224b5 in sendsig_siginfo <netbsd>
[  224.036261] #3 0xffffffff80b51564 in sendsig <netbsd>
[  224.046475] #4 0xffffffff80b51282 in postsig <netbsd>
[  224.046475] #5 0xffffffff80b2fc5d in lwp_userret <netbsd>
[  224.056273] #6 0xffffffff8025a951 in mi_userret <netbsd>
[  224.066277] #7 0xffffffff8025ab89 in syscall <netbsd>

(martin)

2018-12-04 19:17:00 UTC netbsd-7 commitmail json YAML

2018-12-04 19:16:27 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by maxv in ticket #1662):

sys/arch/amd64/amd64/machdep.c: revision 1.321

Fix stack info leak. There is a big padding in struct sigframe_siginfo.

[  224.006287] kleak: Possible leak in copyout: [len=920, leaked=92]
[  224.016977] #0 0xffffffff80224d0a in kleak_note <netbsd>
[  224.026268] #1 0xffffffff80224d8a in kleak_copyout <netbsd>
[  224.026268] #2 0xffffffff802224b5 in sendsig_siginfo <netbsd>
[  224.036261] #3 0xffffffff80b51564 in sendsig <netbsd>
[  224.046475] #4 0xffffffff80b51282 in postsig <netbsd>
[  224.046475] #5 0xffffffff80b2fc5d in lwp_userret <netbsd>
[  224.056273] #6 0xffffffff8025a951 in mi_userret <netbsd>
[  224.066277] #7 0xffffffff8025ab89 in syscall <netbsd>

(martin)

2018-12-04 18:39:03 UTC MAIN commitmail json YAML

Update TODO.sanitizers

Reflect with reality the fts(3) entry as handling compar callback is the
only feature still missing.

Add a new entry for utime(3), we expect to allow changing actime regardless
of noatime mount property.

(kamil)

2018-12-04 16:53:45 UTC MAIN commitmail json YAML

2018-12-04 14:03:30 UTC MAIN commitmail json YAML

Alter a design botch when magic (self modifying) variables
were added to sh ... in other shells, setting such a variable
(for most of them) causes it to lose its special properties,
and act the same as any other variable.  I had assumed that
was just implementor laziness...  I was wrong.

From now on the NetBSD shell will act like the others, and if vars
like HOSTNAME (and SECONDS, etc) are used as variables in a script
or whatever, they will act just like normal variables (and unless
this happens when they have been made local, or as a variable-assignment
as a prefix to a command, the special properties they would have had
otherwise are lost for the remainder of the life of the (sub-)shell
in which the variables were set).

Importing a value from the environment counts as setting the
value for this purpose (so if HOSTNAME is set in the environment,
the value there will be the value $HOSTNAME expands to).

The two exceptions to this are LINENO and RANDOM.  RANDOM
needs to be able to be set to (re-)set its seed.  LINENO needs to
be able to be set (at least in the "local" command) to achieve
the desired functionality.  It is unlikely that any (sane) script
is going to want to use those two as normal vars however.

While here, fix a minor bug in popping local vars (fn return) that need
to notify the shell of changes in value (like PATH).

Change sh(1) to reflect this alteration.  Also add doc of the
(forgotten) magic var EUSER (which has been there since the others
were added), and add a few more vars (which are documented
in other places in sh(1) - like ENV) into the defined or used
variable list (as well as wherever else they appear).

XXX pullup -8

(kre)

2018-12-04 12:23:43 UTC MAIN commitmail json YAML

inet6: remove unused dad ns/na counters

The current DaD code triggers when either an NS or NA is directly
received, so the counters themselves do nothing of use.

(roy)

2018-12-04 12:07:53 UTC netbsd-8 commitmail json YAML

2018-12-04 12:04:02 UTC netbsd-8 commitmail json YAML

2018-12-04 12:02:12 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #1123):

sys/dev/pci/pcidevs: revision 1.1356

Add 2 Symbios products, from OpenBSD

(martin)

2018-12-04 12:00:42 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by mlelstv in ticket #1122):

sys/dev/ld.c: revision 1.105

take kernel lock for ioctl calls when backend isn't tagged MPSAFE.

(martin)

2018-12-04 11:58:11 UTC netbsd-8 commitmail json YAML

Pull up the following, requested by msaitoh in ticket #1121:

usr.sbin/acpitool/acpidump/acpi.c 1.30-1.37, 1.39 via patch
usr.sbin/acpitool/acpidump/acpidump.8 1.11-1.13 via patch

- Add ACPI LPIT (Low Power Idle Table) from FreeBSD r336185.
- Decode DMAR's ANDD (ACPI Name Space).
- Add X2APIC_MODE flag of DMAR.
- Remove extra newline in SPMI table.
- FACS is optional if the HW_REDUCED_ACPI flag is set in the FADT.
- Print SPCR's Interface Type and ARMH GIC Interrupt Type.
- Decode Generic Timer Description Table(GTDT).
- Don't print PM_TMR_BLK if the value is 0.
- Don't print X_PM_TMR_BLK if the address value is 0.
- Decode CSRT (Core System Resources Table).

(martin)

2018-12-04 11:52:57 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1120):

usr.sbin/cpuctl/arch/i386.c: revision 1.85
usr.sbin/cpuctl/arch/i386.c: revision 1.86
usr.sbin/cpuctl/arch/i386.c: revision 1.87
usr.sbin/cpuctl/arch/i386.c: revision 1.88
usr.sbin/cpuctl/arch/i386.c: revision 1.89
usr.sbin/cpuctl/arch/i386.c: revision 1.90
sys/arch/x86/include/specialreg.h: revision 1.132
sys/arch/x86/include/specialreg.h: revision 1.133
sys/arch/x86/include/specialreg.h: revision 1.134
sys/arch/x86/include/specialreg.h: revision 1.135
sys/arch/x86/include/specialreg.h: revision 1.136
sys/arch/x86/x86/cpu_topology.c: revision 1.14

  Add MAWAU (for BND{LD,ST}X instruction) from the latest Intel SDM.

  Whitespace fix. No functional change.

Modify comment. No functional change:
- AMD also has CPUID 0x06 and 0x0d.
- PCOMMIT was obsoleted.
- Use ci_feat_val[7] as CPUID 7 %edx to match x86/cpu.h
- AMD also has CPUID 6.
- Remove unused code for coretemp.
- Consistently use descs[] instead of data[].
- AMD also reports CPUID 7's highest subleaf. Print it.
- Use macro.
  Add Intel CPUID Extended Topology Enumeration Fn0000000b definitions.
  Decode package, core and SMT id if CPUID 0x0b is available on Intel processor.

If the value is different from the kernel value, we should fix the kernel code.

TODO: Use 0x1f if it's available.

  Add Intel/AMD MONITOR/MWAIT leaf.
  Decode Intel/AMD MONITOR/MWAIT leaf.

  Add Intel CPUID Architectural Performance Monitoring leaf Fn0000000a.

  Print Intel CPUID Architectural Performance Monitoring leaf Fn0000000a.

(martin)

2018-12-04 11:44:13 UTC netbsd-8 commitmail json YAML

2018-12-04 11:35:00 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1119):

sys/dev/pci/pcidevs: revision 1.1350
sys/dev/pci/pcidevs: revision 1.1351
sys/dev/pci/pcidevs: revision 1.1352
sys/dev/pci/pcidevs: revision 1.1353
sys/dev/pci/pcidevs: revision 1.1354
sys/dev/pci/pcidevs: revision 1.1355
sys/dev/pci/pcidevs: revision 1.1345
sys/dev/pci/pcidevs: revision 1.1346
sys/dev/pci/pcidevs: revision 1.1347
sys/dev/pci/pcidevs: revision 1.1349

  Add some Intel devices. Some of them are found in Core i7-8550U.

  Add Toshiba's XG4 and XG5 NVMe SSD.

- Add C62x to the descriptions of Intel C620 series devices.
- Add 0xa1ca for Intel C629 LPC or eSPI.

Add AMD Seattle Host Bridge and PCIE root port devices

Add two otehr I2C devices of Intel.

"s/ are are / are /" in comment. No functional change.

Add some Intel 100 series and C230 series devices.

Add a whole bunch of Cavium ThunderX devices

Add Rockchip vendor ID and a device. Requested by jak@
From OpenBSD

Add Amazon.com UART, NVMe, and ENA PCI IDs.

(martin)

2018-12-04 11:29:41 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1118):

sys/dev/pci/pci_subr.c: revision 1.210
sys/dev/pci/pci_subr.c: revision 1.207
sys/dev/pci/pcireg.h: revision 1.143
sys/dev/pci/pci_subr.c: revision 1.208
sys/dev/pci/pcireg.h: revision 1.144
sys/dev/pci/pci_subr.c: revision 1.209
sys/dev/pci/pcireg.h: revision 1.145
sys/dev/pci/pcireg.h: revision 1.146

  Decode PCI Enhanced Allocation.

  The register offset of the mask and pending register is depend on the 64bit
address capable bit, so fix the definition of PCI MSI vector mask and pending
register. This problem was not a real bug because PCI_MSI{MASK,PENDING} were
not used from anywhere.

  The downstream port of PCIe switch is not a root port, so don't print
root port related register. For example, Intel 63xxESB controller's
downstream port device was printed by pcictl(8) with this bug:

-----------------------------
PCI configuration registers:
  Common header:
    0x00: 0x35108086 0x00100147 0x06040001 0x00010010
    Vendor Name: Intel (0x8086)
    Device Name: 63xxESB PCI Express Downstream Port #1 (0x3510)
(snip)
  Capability register at 0x44      <=============
    type: 0x10 (PCI Express)
  Capability register at 0x60      <============= 0x60 - 0x44 = 0x1c
    type: 0x05 (MSI)
  Capability register at 0x70
    type: 0x01 (Power Management)
  Capability register at 0x80
    type: 0x0d (Subsystem vendor ID)
(snip)
  PCI Message Signaled Interrupt
    Message Control register: 0x0080
      MSI Enabled: off
      Multiple Message Capable: no (1 vector)
      Multiple Message Enabled: off (1 vector)
      64 Bit Address Capable: on
      Per-Vector Masking Capable: off
      Extended Message Data Capable: off
      Extended Message Data Enable: off
    Message Address (lower) register: 0x00000000
    Message Address (upper) register: 0x00000000
    Message Data register: 0x0000
(snip)
  PCI Express Capabilities Register
(snip)
    Root Control Register: 0x7005 <=== 0x7005 is the first two byte
      SERR on Correctable Error Enable: on  of the MSI capability structure
      SERR on Non-Fatal Error Enable: off
      SERR on Fatal Error Enable: on
      PME Interrupt Enable: off
      CRS Software Visibility Enable: off
    Root Capability Register: 0x0080
      CRS Software Visibility: off
    Root Status Register: 0x00000000
      PME Requester ID: 0x0000
      PME was asserted: off
      another PME is pending: off
  Device-dependent header:
    0x40: 0x00c00000 0x00616010 0x00000001 0x00005026  |  |<- PCIe      |
    0x50: 0x0203f441 0x10010020 0x00000000 0x004803c0  |              ->|
    0x60: 0x00807005 0x00000000 0x00000000 0x00000000  |<-    MSI    ->|
    0x70: 0xc8028001 0x00000100 0x00000000 0x00000000  |<-    PM      ->|
    0x80: 0x0000000d 0x00000000 0x00000000 0x00000000  |<- subsystem ID  |
--------------------------------------

  Add new macro PCIE_HAS_ROOTREGS(pcie_devtype) and use it. No functional
change.

  Add new PCIE_HAS_LINKREGS(pcie_devtype) and use it. No functional change.

(martin)

2018-12-04 11:21:33 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1117):

sys/dev/pci/if_wmreg.h: revision 1.109
sys/dev/pci/if_wm.c: revision 1.597
sys/dev/pci/if_wm.c: revision 1.598
sys/dev/mii/inbmphyreg.h: revision 1.12
sys/dev/pci/if_wm.c: revision 1.600
sys/dev/pci/if_wm.c: revision 1.601
sys/dev/pci/if_wm.c: revision 1.602

- Add new wm_gmii_{hv,i82544}_{read,write}reg_locked() and use them in
  wm_gmii_{hv,i82544}_{read,write}reg(). *_locked() functions are not
  mii(4) API functions, so it's not required to keep the mii API. Change
  the PHY register type from int to uint16_t. It also change the usage of
  return value. It returns zero on success and non-zero on error.
- Check the return value of *_locked() function and treat it.
- Use *writereg_locked() function to reduce race condition in
  wm_init_lcd_from_nvm().
- Add comment.
- Control TX/RX descriptor snooping control bits on ICH8 and newer.
  Only on ICH8, No-snoop bits are opposite polarity. On my Thinkpad X61,
  the default value of this bits are all zero, so this commit changes
  the snoop function enable on the machine. I tested with some other
  PCH machines and those bits are all zero (enable snoop by default),
  so this commit won't affect to some machines.
- Disable relax ordering on 82546GB(Device ID 0x1099 and 0x10b5) or >= ICH8.
  Same as other OSes.
- Add wm_oem_bits_config_ich8lan() to control LPLU and GbE setting base on
  the NVM's info.
- Modify wm_enable_wakeup() to reduce difference against FreeBSD and Linux.
  This modification affects to ICH8 and newer devices. I217 Rapid Start
  Technology support have not written yet (it's TODO).
- Add wm_k1_workaround_lv() from FreeBSD. It's PCH2 specific:
    Workaround to set the K1 beacon duration for 82579 parts in 10Mbps.
    Disable K1 for 1000 and 100 speeds.
- Make wm_link_stall_workaround_hv() and move an 82578 specific code into it.
  Don't apply the workaround if BMCR_LOOP bit is set. Same as FreeBSD.
- Add comment. Modify comment.
  Fix comment. No functional change.

(martin)

2018-12-04 11:16:33 UTC netbsd-8 commitmail json YAML

2018-12-04 11:15:21 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1116):

sys/dev/mii/miidevs: revision 1.130
sys/dev/mii/miidevs: revision 1.131

Sort OUI by number. No functional change.

- Add ASIX Ax88x9x
- Add description for DP83846A.

(martin)

2018-12-04 10:10:15 UTC MAIN commitmail json YAML

* Increase the default scaling of the two finger scroll to make it
  less sensitive
* Fix range check for hw.synaptics.scale_z so it can be set with sysctl

(blymn)

2018-12-04 09:47:26 UTC MAIN commitmail json YAML

Supply a missing \ ... this missing has meant that these tests
have not been testing everything they should have been testing.
Never mind, they still all succeed.

(kre)

2018-12-04 09:32:50 UTC MAIN commitmail json YAML

Fix failing background test check file.

(blymn)

2018-12-04 09:27:59 UTC MAIN commitmail json YAML

rasops reused wscons attribute bits for internal control.
- make upper 4 attribute bits available for such use
- use wscons flag names instead of literal constants.

(mlelstv)

2018-12-04 08:02:14 UTC MAIN commitmail json YAML

Remove trailing whitespace

(wiz)

2018-12-04 08:01:35 UTC MAIN commitmail json YAML

2018-12-04 02:52:42 UTC MAIN commitmail json YAML

use html tables for directory index.
from "Rajeev V. Pillai" <rajeev_v_pillai@yahoo.com>

call this bozohttpd 20181204.

(mrg)

2018-12-04 01:35:15 UTC MAIN commitmail json YAML

Remove duplicate ;'s. No binary changes intended.

(rin)

2018-12-04 00:26:15 UTC MAIN commitmail json YAML

avoid sign extension in % handling (and printing 0xFFFFFF before
wanted values.)  from Rajeev V. Pillai.

(mrg)

2018-12-04 00:18:05 UTC MAIN commitmail json YAML

soo_fcntl is identical to fnullop_fcntl, use the latter

ok kamil mrg

(maya)

2018-12-03 23:23:30 UTC MAIN commitmail json YAML

Also tell the scsi layer that we are MPSAFE

(bouyer)

2018-12-03 22:41:56 UTC MAIN commitmail json YAML

Update for the new mpii(4) driver, mostly from OpenBSD.

(bouyer)

2018-12-03 22:34:36 UTC MAIN commitmail json YAML

Update the mpii(4) driver to the latest OpenBSD version.
This adds support for the SAS3xxx LSI controllers, and this also makes the
driver MP-safe.
adjust mfii.c for changes in mpiireg.h

Tested with a
mpii0: SMC2008-IR, firmware 9.0.0.0 IR, MPI 2.0

(bouyer)

2018-12-03 20:00:16 UTC MAIN commitmail json YAML

fix typo in comment, NFC

(jdolecek)

2018-12-03 19:51:09 UTC MAIN commitmail json YAML

Allow isa_machdep.c to compile in the case of no ioapic support.

(cherry)

2018-12-03 19:46:43 UTC MAIN commitmail json YAML

Do not assume that all uses of efi are pci aware.

Allow efi.c to compile in the case where pci is not enabled.

(cherry)

2018-12-03 19:15:35 UTC MAIN commitmail json YAML

Head is binutils 2.31

(christos)

2018-12-03 18:24:18 UTC MAIN commitmail json YAML

2018-12-03 18:23:02 UTC MAIN commitmail json YAML

Add 2 Symbios products, from OpenBSD

(bouyer)

2018-12-03 17:03:44 UTC MAIN commitmail json YAML

Note these tools use kvm(3) and not procfs as in Solaris.

(sevan)

2018-12-03 10:53:29 UTC MAIN commitmail json YAML

Make pendingsigs forward declaration match the definition.

(martin)

2018-12-03 06:43:19 UTC MAIN commitmail json YAML

Cleanup traps a bit - attempt to handle weird uses in traps, such
as traps that issue break/continue/return to cause the loop/function
executing when the trap occurred to break/continue/return, and
generating the correct exit code from the shell including when a
signal is caught, but the trap handler for it exits.

All that from FreeBSD.

Also make
T=$(trap)
work as it is supposed to (also trap -p).

For now this is handled by the same technique as $(jobs) - rather
than clearing the traps in subshells, just mark them invalid, and
then whenever they're invalid, clear them before executing anything
other than the special blessed "trap" command.  Eventually we will
handle these using non-subshell command substitution instead (not
creating a subshell environ when the commands in a command-sub alter
nothing in the environment).

(kre)

2018-12-03 06:42:25 UTC MAIN commitmail json YAML

Fix "export -x" (and its consequences) to behave as originally
intended (and as documented) rather than how it has been behaving
(which was not very rational.)  Since it is unlikely that anyone
is using this, the change should be mostly invisible.

While here, a couple of other minor cleanups:
. One call of geteuid() is enough in choose_ps1()
. Fix a typo in a comment
. Improve appearance (whitspace changes) in find_var()

(kre)

2018-12-03 06:41:30 UTC MAIN commitmail json YAML

Yet another foray into the mysterious world of $@ -- this time
to fix the (unusual) idiom "${1+$@}"  (the quotes are part of it).
This seems to have broken about 5 or 6 years ago (somewhere
between -6 and -7), I believe.

Note this is not the same as "$@" and also not the same as ${1+"$@"}
(much more common idioms) which both worked.

Also attempt to deal with "" more correctly, especially when it
appears adjacent to "$@" (or one of the similar constructs.)

This stuff is still all as ugly and hackish (and fragile) as is
possible to imagine, but in an effort to allow some of the weirdness
to eventually go away, the parser output has been made more
regular and all quoted (parts of) words always now start with
CTLQUOTEMARK and end with CTLQUOTEEND regardless of where the
quotes appear.

This allows us to tell the difference between """$@" and "$@"
which was impossible before - yet they are required to generate
different output when there are no args (when "$@" simply vanishes).

Needless to say that change had ramifications all over the place.
To simplify any similar change in the future, there are some new
macros that can generally be used to detect the "noise" data when
processing words, rather than open coding that every time (which
meant that there would *always* be one which missed getting
updated...)

Several other bugs (of my making, and older ones) are also fixed.

The aim is that (aside from anything that is detecting the cases
that were broken before - which were all unlikely uses of sh
syntax) these changes should have no external visible impact.

Sure...

(kre)

2018-12-03 06:40:26 UTC MAIN commitmail json YAML

Revamp aliases - as dumb an idea as they are, if we're going
to have them, they should work as documented, not cause core
dumps, reference after free, incorrect replacements, failing
to implement alias after alias, ...

The big comment that ended:
  This is a good idea ------- ***NOT***
and the hack it was describing are gone.

Note that most of this was from original CVS version 1.1
code (ie: came from the original import, even before 4.4-Lite
was merged.  That is, May 1994.  And no-one in 24.5 years
noticed (or at least complained about)  all the bugs (or at
least, most of them)).

With these changes, aliases ought to work (if you can call it
that) as they are expected to by POSIX.  Now if only we could
get POSIX to delete them (or make them optional)...

Changes partly inspired by similar changes made by FreeBSD,
(as was the previous change to alias.c, forgot ack in commit
log for that one, apologies) but done a little differently,
and perhaps with a slightly better outcome.

(kre)

2018-12-03 05:22:03 UTC MAIN commitmail json YAML

Define macro before using it. This macro is used as a compile time
"plugin" mechanism to use various platform specific enumeration
functions. It is currently separately defined for 'native' and XEN,
but the mechanism is not exported globally as it should be.

XXX: fix this.

(cherry)

2018-12-03 04:39:44 UTC MAIN commitmail json YAML

Some counters are not per queue but per traffic class. Make new evcnt group
"ixgM tcN" (N = 0..7) and move those counters into it. We are using only
traffic class 0, so we will see only tc0's counter are updated.

(msaitoh)

2018-12-03 02:38:30 UTC MAIN commitmail json YAML

When forking a child shell, arrange for errors/exit to always unwind
to the main handler, rather than wherever the parent shell would go.

nb: not needed for vfork(), after vfork() we never go that path - which
is good or we'd be corrupting the parent's handler.

This allows the child to always exit (when it should) rather than being
caught up doing something else (and while it would eventually exit, the
status would be incorrect in some cases).

One test is:
sh -c 'trap "(! :) && echo BUG || echo nobug" EXIT'
from Martijn Dekker

Fix from FreeBSD (missed earlier).

XXX - 2b part of the 48875 pullup to -8

(kre)

2018-12-03 00:12:22 UTC MAIN commitmail json YAML

KASLR is in files.kern now.

(christos)

2018-12-03 00:11:39 UTC MAIN commitmail json YAML

2018-12-03 00:11:02 UTC MAIN commitmail json YAML

Expose addresses depending on the KASLR setting (from mrg@). Restores the
status quo of exposing kernel addresses if there is no KASLR.

(christos)

2018-12-02 21:00:13 UTC MAIN commitmail json YAML

Introduce KLEAK, a new feature that can detect kernel information leaks.

It works by tainting memory sources with marker values, letting the data
travel through the kernel, and scanning the kernel<->user frontier for
these marker values. Combined with compiler instrumentation and rotation
of the markers, it is able to yield relevant results with little effort.

We taint the pools and the stack, and scan copyout/copyoutstr. KLEAK is
supported on amd64 only for now, but it is not complicated to add more
architectures (just a matter of having the address of .text, and a stack
unwinder).

A userland tool is provided, that allows to execute a command in rounds
and monitor the leaks generated all the while.

KLEAK already detected directly 12 kernel info leaks, and prompted changes
that in total fixed 25+ leaks.

Based on an idea developed jointly with Thomas Barabosch (of Fraunhofer
FKIE).

(maxv)

2018-12-02 20:54:44 UTC MAIN commitmail json YAML

Switch to __builtin___clear_cache() in userspace.

aarch64_sync_icache() doesn't exist because there no libarm equivalent
on aarch64.

(alnsn)

2018-12-02 18:12:29 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

(jdolecek)

2018-12-02 17:02:04 UTC MAIN commitmail json YAML

Don't destroy the dma maps if we're not disabling the adapter, avoids
a KASSERT() when bus_dmamap_destroy() is called from interrupt
context via bge_watchdog()
Set IFF_OACTIVE only when bge_encap() fails on adapter ressource shortage.
Otherwise we may set IFF_OACTIVE while no transmit is in progress, and
nothing will clear it.
If bus_dmamap_load_mbuf() fails with EFBIG, m_defrag() the chain and retry.
Refine the check for the 4GB boundary workaround (a fragment should also
not cross the boundary), and do it only for TSO.
If bge_encap() fails and didn't set IFF_OACTIVE, drop the packet.
Bring in more hardware bug workarounds from freebsd.

With these it seems that a BCM5720 A0 can survive a few hours of internet
load with TSO4 enabled.

(bouyer)

2018-12-02 16:58:13 UTC MAIN commitmail json YAML

2018-12-02 16:49:24 UTC MAIN commitmail json YAML

2018-12-02 15:43:05 UTC MAIN commitmail json YAML

Fix variable escaping in dev_exists()

(jmcneill)

2018-12-02 13:22:28 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

(jdolecek)

2018-12-02 13:17:19 UTC MAIN commitmail json YAML

use pci_intr_establish_xname()

(jdolecek)

2018-12-02 10:51:07 UTC MAIN commitmail json YAML

2018-12-02 10:27:58 UTC MAIN commitmail json YAML

Fix the worst of the bugs in alias processing.  This has been in sh
since this code was first imported (May 1994) (ie: before 4.4-Lite)

There is (much) more coming soon (the big ugly comment is going away).

This one has been separated out, as it can easily cause sh
core dumps, so needs:

XXX pullup-8

(the other changes to aliases probably will not get that.)

(kre)