| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the removal of NQNFS, but was left in in case it was required for NFSv4.
Since our new NFSv4 client and server can't use it for their
requirements, GC the old mechanism, as well as other unused lease-
related code and interfaces.
Due to its impact on kernel programming and binary interfaces, this
change should not be MFC'd.
Proposed by: jeff
Reviewed by: jeff
Discussed with: rmacklem, zach loafman @ isilon
|
|
|
|
|
|
|
|
|
| |
Check the condition and return ENOENT then.
In nfs_lookup(), respect ENOENT return from cache_lookup() when it is caused
by dvp reclaim.
Reported and tested by: pho
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the mappings without any of read and execution rights, in particular,
the PROT_NONE entries. This makes mlockall(2) work for the process
address space that has such mappings.
Since protection mode of the entry may change between setting
MAP_ENTRY_IN_TRANSITION and final pass over the region that records
the wire status of the entries, allocate new map entry flag
MAP_ENTRY_WIRE_SKIPPED to mark the skipped PROT_NONE entries.
Reported and tested by: Hans Ottevanger <fbsdhackers beasties demon nl>
Reviewed by: alc
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the mapping by the object' file with the protection and mode of
the first loadable segment over the whole region. Then, it maps other
segments at the appropriate addresses inside the region.
On amd64, due to default alignment of the segments being 1Gb, the
subsequent segment mappings leave the holes in the region, that usually
contain mapping of the object' file past eof. Such mappings prevent
wiring of the address space, because the pages cannot be faulted in.
Change the way the mapping of the ELF objects is constructed, by first
mapping PROT_NONE anonymous memory over the whole range, and then
mapping the segments of the object over it. Take advantage of this new
order and allocate .bss by changing the protection of the range instead
of remapping.
Note that we cannot simply keep the holes between segments, because
other mappings may be made there. Among other issues, when the dso is
unloaded, rtld unmaps the whole region, deleting unrelated mappings.
The kernel ELF image activator does put the holes between segments, but
this is not critical for now because kernel loads only executable image
and interpreter, both cannot be unloaded. This will be fixed later, if
needed.
Reported and tested by: Hans Ottevanger <fbsdhackers beasties demon nl>
Suggested and reviewed by: kan, alc
|
|
|
|
|
|
| |
without having to understand all gvinum internals.
- Document the grow command in the manpage and update examples to use the
command where possible.
|
|
|
|
|
|
| |
Fix spacing.
Reviewed by: kan
|
|
|
|
| |
code reuse.
|
|
|
|
| |
make use of it in the gvinum userland code.
|
|
|
|
| |
Reviewed by: rwatson and jeli
|
| |
|
|
|
|
|
|
|
| |
The geom and CAM changes for root_hold are the wrong solution for USB design
quirks.
Requested by: scottl
|
| |
|
|
|
|
|
|
|
| |
older ixgb driver. I will add to other architectures
after this one proves trouble free.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
for the new 82599 adapter family, adds header split, and
many small fixes. The driver should now be added to the
GENERIC kernel.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
adds header split and SCTP support into the igb driver.
Various small improvements and fixes.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: freebsd-current@, freebsd-hackers@
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: freebsd-current@, freebsd-hackers@
MFC after: 1 week
|
|
|
|
|
|
| |
be null if attach work fails before hooking up the eeprom support
Obtained from: madwifi
|
|
|
|
| |
(plain ipfw rules unchanged)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
types of MAC overheads such as preambles, link level retransmissions
and more.
Note- this commit changes the userland/kernel ABI for pipes
(but not for ordinary firewall rules) so you need to rebuild
kernel and /sbin/ipfw to use dummynet features.
Please check the manpage for details on the new feature.
The MFC would be trivial but it breaks the ABI, so it will
be postponed until after 7.2 is released.
Interested users are welcome to apply the patch manually
to their RELENG_7 tree.
Work supported by the European Commission, Projects Onelab and
Onelab2 (contract 224263).
|
| |
|
|
|
|
| |
Suggested by: jhb
|
|
|
|
|
|
|
| |
We typically wire translation to devices with TLB1 entries and
pmap_kextract() does not know about those and returns 0. This
causes false positives (read: all serial ports suddenly become
the console).
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not use Giant for kbdmux(4) locking. This is wrong and apparently
causing more problems than it solves. This will re-open the issue
where interrupt handlers may race with kbdmux(4) in polling mode.
Typical symptoms include (but not limited to) duplicated and/or
missing characters when low level console functions (such as gets)
are used while interrupts are enabled (for example geli password
prompt, mountroot prompt etc.)
MFC after: 3 days
|
|
|
|
| |
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
|
|
|
|
| |
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
|
|
|
|
|
|
|
| |
Most compilers nowadays (including GCC) are smart enough to know what's
going on and generate more efficient code anyway.
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
|
|
|
|
| |
Approved by: julian (mentor)
|
| |
|
|
|
|
|
|
|
| |
frames passed down through the transmit path
o mark ndis requiring 802.3 encap'd frames
Reviewed by: "Paul B. Mahol" <onemda@gmail.com>, thompsa
|
|
|
|
|
|
| |
are more commonly known as BSD partition names.
Discussed with: ivoras@
|
| |
|
|
|
|
|
|
|
|
|
| |
It turns out my handling of SIGTTOU and SIGTTIN didn't entirely comply
to the standards. It is true that in the SIGTTOU case we should not
return EIO when the signal is ignored/blocked, but in the SIGTTIN case
we must.
See also: POSIX issue 7 section 11.1.4
|
|
|
|
|
|
|
|
|
| |
above to avoid referencing undefined terms (humans are not compilers
but still care about these things).
Change some .Sh to .Ss to better reflect the structure of the text.
No new content.
|
| |
|
|
|
|
| |
Submitted by: Grzegorz Bernacki gjb ! semihalf dot com
|
|
|
|
|
|
|
| |
set to a low number. The check for skipping was in the
incorrect place. Which meant we would FR chunks we
should not.
MFC after: 1 Month
|
|
|
|
|
|
| |
help us be able to keep ABI compatibility between
8 and 9.
MFC after: Never
|
|
|
|
|
|
| |
a pointer to the ip header.
-style
-spacing
|
|
|
|
| |
Fill the fsbase and gsbase fields of the mcontext structure on i386.
|
|
|
|
|
| |
Reported by: Andrew Brampton <me@bramp.net>
MFC after: 1 week
|
|
|
|
| |
Reviewed by: brueffer
|
|
|
|
|
|
| |
machine-specific flags to match but ar5523.bin doesn't have.
Pointed by: marcel
|
|
|
|
|
|
|
|
|
| |
(framing, parity, etc), but does not indicate characters
being received. Since no chracters have been received,
ignore the line errors.
PR: 131006
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Maciej Cencora <m.cencora@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
- 1000BaseSX
- 2500BaseSX
While I'm there, correct 1000BaseTX as more standard 1000BaseT.
MFC after: 3 days
|