| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fixes and feature adds
- Remove extranious echo that breaks puppet
- Handle restarts of multiple pflog devices correctly
- Add the ability to perform actions on specific pflog devices.
Typo Fix.
PR: 199150
|
|
|
|
| |
urtwn: blink the LED when scanning.
|
|
|
|
|
|
| |
Tidy up battery status information. Remove a trailing white space.
PR: 193671
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
r245508 modified the NFS client's Setattr RPC to
use VA_UTIMES_NULL to indicate whether it should
set the time to the current tod on the server.
This had the side effect of making the NFS client
use the client's timestamp for exclusive create,
starting with FreeBSD9.2.
Unfortunately a bug in some Solaris NFS servers
causes these servers to return NFS_OK to the
Setattr RPC done during exclusive create, but not
actually set the file's mode, leaving the file's
mode == 0.
This patch restores the NFS client's behaviour to
use the server's tod for the exclusive open's
Setattr RPC, to avoid the Solaris server bug and
to restore the pre-FreeBSD9.2 NFS behaviour.
|
|
|
|
|
|
|
|
|
|
|
| |
Add OBJCOPY to the list of external tools
MFC r272815 (by bapt):
Fix typo
This should fix the build troubles some people have been seeing after
the MFC of r280980 (in r281289). Sorry for the breakage.
|
|
|
|
|
|
|
| |
Fix the hand after the immediate reboot after the init binary is unlinked.
MFC r280763:
Fix build (with gcc).
|
|
|
|
|
|
|
|
|
|
| |
When CPU is not busy, those queues are typically empty. When CPU is busy,
then one more extra sorting is the last thing it needs. If specific device
(HDD) really needs sorting, then it will be done later by CAM.
This supposed to fix livelock reported for mirror of two SSDs, when UFS
fires zillion of BIO_DELETE requests, that totally blocks I/O subsystem by
pointless sorting of requests and responses under single mutex lock.
|
|
|
|
|
|
|
|
| |
Simplify string mangling in ifmaybeload().
- Use strlcpy() instead of strcpy().
- Use strlcat() instead of a strlcpy() with a magic number subtracted
from the length.
- Replace strncmp(..., strlen(foo) + 1) with strcmp(...).
|
|
|
|
|
|
| |
Enable bzipfs support in the EFI loader.
- Add bzipfs to the list of supported filesystems in the EFI loader.
- Increase the heap size allocated for the EFI loader from 2MB to 3MB.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The System V ABI for amd64 allows functions to use space in a 128 byte
redzone below the stack pointer for scratch space and requires
interrupt and signal frames to avoid overwriting it. However, EFI uses
the Windows ABI which does not support this. As a result, interrupt
handlers in EFI push their interrupt frames directly on top of the
stack pointer. If the compiler used the red zone in a function in the
EFI loader, then a device interrupt that occurred while that function
was running could trash its local variables. In practice this happens
fairly reliable when using gzipfs as an interrupt during decompression
can trash the local variables in the inflate_table() function
resulting in corrupted output or hangs.
Fix this by disabling the redzone for amd64 EFI binaries. This
requires building not only the loader but any libraries used by the
loader without redzone support.
Thanks to Jilles for pointing me at the redzone once I found the stack
corruption.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow the EFI loader to work with large kernels and/or modules
(for example, a large mfsroot). Note that for EFI the kernel and
modules (as well as other metadata files such as splash screens or
memory disk images) are loaded into a statically-sized staging area.
When the EFI loader exits it copies this staging area down to the
location the kernel expects to run at.
- Add bounds checking to the copy routines to fail attempts to access
memory outside of the staging area. Previously loading a combined
kernel + modules larger than the staging size (32MB) would overflow
the staging area trashing whatever memory was afterwards. Under
Intel's OVMF firmware for qemu this resulted in fatal faults in the
firmware itself. Now the attempt will fail with ENOMEM.
- Allow the staging area size to be configured at compile time via
an EFI_STAGING_SIZE variable in src.conf or on the command line.
It accepts the size of the staging area in MB. The default size
remains 32MB.
|
|
|
|
|
| |
- Align comment for df flags variable in periodic.conf.
- Note default value of df flags variable in periodoc.conf(5).
|
|
|
|
|
| |
Spin the twiddle in dosfs to give visual feedback for disk I/O on
FAT filesystems as is done for other filesystems in the loader.
|
|
|
|
|
| |
Resize receive socket buffers that support autosizing when receiving
TCP data via direct data placement.
|
|
|
|
|
|
| |
Swap device is still reported as enabled, and system still may crash later
if some swapped-out kernel pages were lost with the device, but at least
GEOM and CAM can now release the lost disk, allowing it to be reconnected.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Ensure the cross assembler, linker and objcopy are used for the build32
stage, just like for the regular world stage.
Reviewed by: rodrigc, imp, bapt, emaste
Differential Revision: https://reviews.freebsd.org/D2187
|
|
|
|
| |
Add articles, avoid use of "you", simplify a few sentences.
|
|
|
|
|
|
| |
s/AutoSize/Growfs/ following upstream commit r761.
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
| |
cxgbe(4): there is no need to force an "unimplemented" panic needlessly.
The calls to free_nm_txq and free_nm_rxq are made just a few lines prior
to the panic.
|
|
|
|
|
|
|
|
| |
cxgbe(4): Add a minimal if_cxl module that pulls in the real driver as
a dependency. This ensures "ifconfig cxl<n> ..." does the right thing
even when it's run with no driver loaded.
if_cxl.ko is the tiniest module in /boot/kernel.
|
|
|
|
|
| |
cxgbe(4): allow the SET_FILTER_MODE ioctl to change the mode when it's
safe to do so.
|
|
|
|
| |
Correctly handle __fcntl_compat symbol for the !SYSCALL_COMPAT case.
|
|
|
|
|
|
|
| |
Disable timestamping on devfs read/write operations by default.
MFC r280949:
Refine r280308. Use seconds precision for devfs timestamps by default.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
r279243:
cxgbe(4): request an automatic tx update when a netmap txq idles.
r279244:
cxgbe(4): wait for the hardware to catch up before destroying a netmap txq.
r279245:
cxgbe(4): do not set the netmap rxq interrupts on a hair-trigger.
r279246:
cxgbe(4): set up congestion management for netmap rx queues.
The hw.cxgbe.cong_drop knob controls the response of the chip when
netmap queues are congested.
r279251:
cxgbe(4): allow tx hardware checksumming on the netmap interface.
It is disabled by default but users can set IFCAP_TXCSUM on the
netmap ifnet (ifconfig ncxl0 txcsum) to override netmap and force
the hardware to calculate and insert proper IP and L4 checksums in
outbound frames.
r279691:
cxgbe(4): provide the correct size of freelists associated with netmap
rx queues to the chip. This will fix many problems with native netmap
rx on ncxl/ncxgbe interfaces.
r279700:
cxgbe(4): knobs to experiment with the interrupt coalescing timer for
netmap rx queues, and the "batchiness" of rx updates sent to the chip.
These knobs will probably become per-rxq in the near future and will be
documented only after their final form is decided.
r279701:
cxgbe(4): experimental rx packet sink for netmap queues. This is not
intended for general use.
|
|
|
|
| |
cxgbe(4): Do not call sbuf_trim on an sbuf with a drain function.
|
|
|
|
|
| |
cxgbe(4): fix if_media handling for T520-BT cards. 1Gbps and 100Mbps
are valid for this card.
|
|
|
|
| |
cxgbe(4): adapter_full_init is always a synchronized operation.
|
|
|
|
|
| |
cxgbe(4): a change to the synchronization rules within the the driver.
This is purely cosmetic because the new rules are already followed.
|
|
|
|
| |
cxgbe(4): fix a test made while enabling TOE.
|
|
|
|
|
|
|
|
| |
r277102:
cxgbe/iw_cxgbe: allow any size during the initial MPA exchange.
r277135:
cxgbe/iw_cxgbe: fix whitespace nit in r277102.
|
|
|
|
|
|
|
|
|
| |
r276598:
Add a manual page for cxgbetool. It is incomplete but definitely
better than nothing.
r276607:
Fix all nits reported by mandoc -Tlint.
|
|
|
|
|
|
|
|
| |
r276729:
cxgbe/tom: use vmem(9) as the DDP page pod allocator.
r276775:
cxgbe/tom: allocate page pod addresses instead of ppod#.
|
|
|
|
|
| |
cxgbe/tom: do not engage the TOE's payload chopper for payload < 2 MSS
or for 10Gbps ports.
|
|
|
|
| |
cxgbe(4): fix the description of a strange bunch of counters.
|
|
|
|
| |
Sponsored by: Netflix Inc.
|
|
|
|
|
|
|
|
| |
Fix multiple vulnerabilities of ntp. [SA-15:07]
Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
|
|
|
|
| |
When an mbuf allocation fails in the receive path, the mbuf containing the received packet is not sent to the host network stack and is reused again on the receive ring. Remaining received packets in the ring are not processed in that invocation of bxe_rxeof() and defered to the task thread
|
|
|
|
| |
cxgbe/tom: fix the MSS calculation for IPv6 connections handled by the TOE.
|
|
|
|
| |
cxgbe/tom: log some more details in send_flowc_wr.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
r275539:
cxgbe(4): Allow for different pad and pack boundaries for different
adapters. Set the pack boundary for T5 cards to be the same as the
PCIe max payload size. The chip likes it this way.
In this revision the driver allocate rx buffers that align on both
boundaries. This is not a strict requirement and a followup commit
will switch the driver to a more relaxed allocation strategy.
r275554:
cxgbe(4): allow the driver to use rx buffers that do not end on a pack
boundary.
|
|
|
|
|
| |
Move KTR_CXGBE from t4_tom.h to adapter.h so that the base if_cxgbe
code can use it too.
|
|
|
|
| |
Add a missing comma.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix some bad interaction between cxgbe(4) and lacp lagg(4) that could
leave a port permanently disabled when a copper cable is unplugged and
then plugged right back in.
lacp_linkstate goes looking for the current ifmedia on a link state
change and it could get stale information from cxgbe(4) on a module
unplug followed by replug. The fix is to process module events before
link-state events within the driver, and to always rebuild the ifmedia
list on a module change event (instead of rebuilding it lazily).
Thanks to asomers@ for the problem report and detailed analysis to go
with it.
|
|
|
|
|
|
|
| |
Mention support for 16h family processors, added in r263169.
PR: 198933
Submitted by: isoa@kapsi.fi
|
|
|
|
| |
Restore proper error from oshmctl(2), broken by r280323.
|
|
|
|
| |
Remove useless initialization.
|
|
|
|
|
|
|
|
|
|
| |
Fix thinko/copypaste error.
When checking the length of the mutual secret password the variable for
the secret password was used by mistake. This resulted in ctld never
warning about the length of the mutual secret being wrong even if it was.
Sponsored by: iXsystems
|