| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
the named file.
Approved by: marcel (mentor)
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
|
| |
command properly. Without this change, mfi(4) always sends 10 byte READ
and WRITE commands, which will cause data corruption when device is
larger than 2^32 sectors.
PR: kern/173291
Submitted by: Steven Hartland <steven.hartland multiplay.co.uk>
Reviewed by: mav
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
- Sort entries in SYNOPSIS.
- Start sentence on a new line.
- Remove redundant textdump dump description.
Submitted by: bde
|
|
|
|
|
|
|
|
|
| |
the previous diradd had already finished it could have been reclaimed
already. This would only happen under heavy dependency pressure.
Reported by: Andrey Zonov <zont@FreeBSD.org>
Discussed with: mckusick
MFC after: 1 week
|
|
|
|
| |
Submitted by: Eric van Gyzen <eric@vangyzen.net>
|
|
|
|
| |
Noticed by: pjd
|
|
|
|
| |
Submitted by: jimharris
|
|
|
|
|
| |
The commands F_SETLK_REMOTE, F_DUPFD_CLOEXEC and F_DUP2FD_CLOEXEC were not
decoded.
|
| |
|
|
|
|
|
|
|
| |
we're not set up to deal with that.
X-MFC: 242479
MFC after: 1 week
|
|
|
|
|
|
| |
we're not set up to deal with that.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
was still possible to open for write from the lower filesystem. There
is a symmetric situation where the binary could already has file
descriptors opened for write, but it can be executed from the nullfs
overlay.
Handle the issue by passing one v_writecount reference to the lower
vnode if nullfs vnode has non-zero v_writecount. Note that only one
write reference can be donated, since nullfs only keeps one use
reference on the lower vnode. Always use the lower vnode v_writecount
for the checks.
Introduce the VOP_GET_WRITECOUNT to read v_writecount, which is
currently always bypassed to the lower vnode, and VOP_ADD_WRITECOUNT
to manipulate the v_writecount value, which manages a single bypass
reference to the lower vnode. Caling the VOPs instead of directly
accessing v_writecount provide the fix described in the previous
paragraph.
Tested by: pho
MFC after: 3 weeks
|
|
|
|
|
|
| |
- Remove NGM_ATM_CARRIER_CHANGE, which was removed in r118175.
Submitted by: Mamontov Roman <mr.xanto gmail.com>
|
|
|
|
|
|
|
| |
provide this information along with messages documentation,
like this done in manual pages for other netgraph nodes.
Submitted by: Mamontov Roman <mr.xanto gmail.com>
|
|
|
|
|
|
|
| |
This caused -std=c++0x not to be passed to the build by default.
Pointy hat to: dim
MFC after: 3 days
|
|
|
|
|
|
| |
Update to use the latest version of the PCI IDs Repository.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
all supported debugging bits.
- If DRM_DEBUG_DEFAULT_ON isn't defined, then initialize drm_debug_flag
to zero.
DRM_DEBUG_DEFAULT_ON is defined when module is build with -DDEBUG_DRM
or if kernel config has 'options DEBUG_DRM'.
Reviewed by: kib
|
|
|
|
| |
platforms.
|
|
|
|
| |
potentially referencing already-freed memory.
|
|
|
|
|
|
|
|
|
| |
Instead, add protocol specific mbuf flags M_IP_NEXTHOP and
M_IP6_NEXTHOP. Use them to indicate that the mbuf's chain
contains the PACKET_TAG_IPFORWARD tag. And do a tag lookup
only when this flag is set.
Suggested by: andre
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
floppies.
Its unlikely that anyone actually uses these or cares about these
anymore, since we support other floppy types and this change doesn't
hurt - just add it.
PR: conf/40777
Submitted by: Antti Kantee <pooka@cubical.fi>
Arrival-Date: Fri Jul 19 08:50:02 PDT 2002
Approved by: cperciva (implicit)
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
their curcpu variants.
Discussed with: mav, davide
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
only applies to non-PCIe systems. If PCIe is in target mode, it will simply
and gracefully fail to attach of its own accord.
|
|
|
|
|
|
|
|
|
| |
Add software mixer table for FastTrack Ultra.
Only set volume controls which are valid at startup for standard
USB audio devices, so that settings like treble and bass use
the reset defaults.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
exist. Fix that.
PR: conf/71994
Submitted by: Mikael Eklund <rma@ludd.ltu.se>
Reviewed by: crees
Reviewed by: jilles
Approved by: cperciva (implicit)
MFC after: 3 days
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
| |
config options.
Approved by: joel
|
|
|
|
|
|
|
|
|
| |
state of crashdump target devices.
This will be used to add a "-l" (ell) flag to dumpon(8) to list the
currently configured dumpdev.
Reviewed by: phk
|
|
|
|
|
|
|
|
|
| |
PCM API doesn't support showing all the knobs. Make sure all the USB audio
mixer nodes are freed at detach. Before this patch USB audio would leak
some memory at detach. Print out buffer sizes in number of samples at attach.
Fix setting of volume controls when the number of channels is greater than two.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the call to pmap_remove_all() within vm_page_cache() is usually redundant.
This change eliminates that call to pmap_remove_all() and introduces a
call to pmap_remove_all() before vm_page_cache() in the one place where
it didn't already exist.
When iterating over a paging queue, if the object containing the current
page has a zero reference count, then the page can't have any managed
mappings. So, a call to pmap_remove_all() is pointless.
Change a panic() call in vm_page_cache() to a KASSERT().
MFC after: 6 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
%gs, when supported. Note that WRFSBASE and WRGSBASE are not very
useful on FreeBSD right now, because a return from the kernel mode to
userspace reloads the bases specified by the sysarch(2) syscall, most
likely.
Enable the Supervisor Mode Execution Prevention (SMEP) when
supported. Since the loader(8) performs hand-off to the kernel with
the page tables which contradict the SMEP, postpone enabling the SMEP
on BSP until pmap switched for the proper kernel tables.
Debugged with the help from: avg
Tested by: avg, Michael Moll <kvedulv@kvedulv.de>
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
introduced with the IvyBridge CPUs. Provide the definitions for new
bits in CR3 and CR4 registers.
Tested by: avg, Michael Moll <kvedulv@kvedulv.de>
MFC after: 2 weeks
|
|
|
|
| |
Submitted by: Giovanni Trematerra <gianni at freebsd DOT org>
|
|
|
|
|
|
| |
- Allow larger sort memory on 64-bit platforms
Submitted by: Oleg Moskalenko <oleg.moskalenko@citrix.com>
|
|
|
|
| |
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
removed in r99417. bge(4) controllers can do TCP checksum offload
for IP fragmented datagrams but unlike ti(4), it lacks UDP checksum
offloading for IP fragmented datagrams. The problem was bge(4)
blindly requested TCP/UDP checksum for IP fragmented datagrams such
that it resulted in corrupted UDP datagrams before r99417.
Remove remaining code for TCP checksum offloading for IP fragmented
datagrams which should have been removed in r99417.
|
|
|
|
|
|
|
|
|
|
|
|
| |
datagrams. Traditionally upper stack fragmented packets without
computing TCP/UDP checksum and these datagrams were passed to
driver. But there are chances that other packets slip into the
interface queue in SMP world. If this happens firmware running on
MIPS 4000 processor in the controller would see mixed packets and
it shall send out corrupted packets.
While I'm here simplify checksum offloading setup.
MFC After: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow textdumps to be called explicitly from DDB.
If "dump" is called in DDB and textdumps are enabled then abort the
dump and tell the user to turn off textdumps.
Add options TEXTDUMP_PREFERRED to turn textdumps on by default.
Add options TEXTDUMP_VERBOSE to be a bit more verbose while textdumping.
Reviewed by: rwatson
MFC after: 2 weeks
|