| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Found by: FlexeLint
|
|
|
|
|
|
| |
strcpy to get private versions, use private versions directly.
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of C strings internally; C strings require a lot of return value
checking that (a) takes a lot of space, and (b) is difficult to get
right. Prior to the advent of compartment support, modeling APIs
for helper functions on snprintf worked fine; with the additional
complexity, the sbuf_printf() API makes a lot more sense.
While doing this, break out the printing of sequential compartment
lists into a helper function, mac_{biba,mls}_compartment_to_string().
This permits the main body of mac_{biba,mls}_element_to_string()
to be concerned only with identifying sequential ranges rather
than rendering.
At a less disruptive moment, we'll push the move from snprintf()-like
interface to sbuf()-like interface up into the MAC Framework layer.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
| |
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
|
|
| |
Don't return(foo(...)) in function returning void.
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
| |
|
|
|
|
|
|
|
| |
Remove breaks after return.
Remove unused variable.
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
|
|
|
|
|
| |
Use ->init() and ->fini() to handle the mutex in geom_disk.c
Remove the g_add_class() function and replace it with a standardized
g_modevent() function.
This adds the basic infrastructure for loading/unloading GEOM classes
|
|
|
|
|
|
|
|
|
|
|
|
| |
only meaningful for fragments. Also don't bother to byte-swap the
ip_id when we do generate it; it is only used at the receiver as a
nonce. I tried several different permutations of this code with no
measurable difference to each other or to the unmodified version, so
I've settled on the one for which gcc seems to generate the best code.
(If anyone cares to microoptimize this differently for an architecture
where it actually matters, feel free.)
Suggested by: Steve Bellovin's paper in IMW'02
|
|
|
|
|
|
|
| |
removing at the same time the need for this to be a "count" config
option.
Found by: FlexeLint
|
| |
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
|
|
| |
Use arrays instead of relying on struct packing.
Identical md5(scsi_ch.o).
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Tested by: Marcel
|
|
|
|
| |
and decoding UUID's in big endian and little endian binary format.
|
|
|
|
|
|
| |
deadlocks with vnode backed md(4) devices because md now uses a
kthread to run the bio requests instead of doing it directly from
the bio down path.
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
should make our beloved friend look less like he has a massive head wound.
|
|
|
|
| |
something with it.
|
|
|
|
| |
loader to shut it up.
|
|
|
|
|
|
|
|
|
| |
switch to it before calling mi_startup(). The bootstack is WAY too small
for running acpica during probe/attach. While here, pass modulep/physfree
to the startup routine, rather than writing to the global variables in
locore.S.
Approved by: re (amd64/*)
|
| |
|
| |
|
|
|
|
| |
Approved by: re (amd64/* blanket)
|
|
|
|
| |
Approved by: re ("safe" amd64 support)
|
|
|
|
|
|
| |
port to amd64 after repocopy.
Approved by: re (amd64/*)
|
|
|
|
|
|
| |
witness.
Approved by: re (safe amd64 support)
|
|
|
|
|
|
|
| |
be installed if an old one does not exist, i.e. only during install, not
during upgrades.
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This machine uses a non-standard scheme to specify the interrupts to
be assigned for devices in PCI slots; instead of giving the INO
or full interrupt number (which is done for the other devices in this
box), the firmware interrupt properties contain intpin numbers, which
have to be swizzled as usual on PCI-PCI bridges; however, the PCI host
bridge nodes have no interrupt map, so we need to guess the
correct INO by slot number of the device or the closest PCI-PCI
bridge leading to it, and the intpin.
To do this, this fix makes the following changes:
- Add a newbus method for sparc64 PCI host bridges to guess
the INO, and glue code in ofw_pci_orb_callback() to invoke it based
on a new quirk entry. The guessing is only done for interrupt numbers
too low to contain any IGN found on e450s.
- Create another new quirk entry was created to prevent mapping of EBus
interrupts at PCI level; the e450 has full INOs in the interrupt
properties of EBus devices, so trying to remap them could cause
problems.
- Set both quirk entries for e450s; remove the no-swizzle entry.
- Determine the psycho half (bus A or B) a driver instance manages
in psycho_attach()
- Implement the new guessing method for psycho, using the slot number,
psycho half and property value (intpin).
Thanks go to the testers, especially Brian Denehy, who tested many kernels
for me until I had found the right workaround.
Tested by: Brian Denehy <B.Denehy@90east.com>, jake, fenner,
Marius Strobl <marius@alchemy.franken.de>,
Marian Dobre <mari@onix.ro>
Approved by: re (scottl)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current name is confusing, because it indicates to
the client that a bus_dmamap_sync() operation is not
necessary when the flag is specified, which is wrong.
The main purpose of this flag is to hint the underlying
architecture that DMA memory should be mapped in a coherent
way, but the architecture can ignore it. But if the
architecture does supports coherent mapping of memory, then
it makes bus_dmamap_sync() calls cheap.
This flag is the same as the one in NetBSD's Bus DMA.
Reviewed by: gibbs, scottl, des (implicitly)
Approved by: re@ (jhb)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
nfs_lock.c. Right now, if we permit a signal to interrupt the sleep,
we will slip the lock and no process on that client, the server, or
any other client will be able to acquire the lock. This can happen,
for example, if a user hits Ctrl-C or Ctrl-T while a process is
waiting for the lock. By removing PCATCH, we prevent that from
happening, at the cost of not permitting a user-requested lock abort:
also nasty. However, a user interface bug might be preferable to a
serious semantic bug, so we go with that for now.
We need to teach the rpc.lockd/kernel protocol how to abort lock
requests, and rpc.lockd how to handle aborted lock requests; patches
for the kernel bit are floating around, but no rpc.lockd bit yet.
Approved by: re (scottl)
|
|
|
|
|
|
|
|
|
| |
mismerged from the MAC tree, and didn't get picked up because warnings
are not normally fatal in per-module builds, only when they are linked
into a kernel (such as LINT).
Reported by: des and the technicolor tinderbox
Approved by: re (scottl)
|