| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
| |
which broke the correct handling of the BIOCGSEESENT flag in the bpf
listener.
PR: kern/56441
Submitted by: <vys at renet.ru>
MFC after: 3 days
|
|
|
|
|
|
|
| |
for a larger number of chained port modules.
PR: kern/55018
Submitted by: Cyrill Shevchuk <cyrill at cyrills.net>
|
|
|
|
|
|
|
|
| |
when responding to TCP SYN packets with TCP_MD5 enabled and set.
PR: kern/82963
Submitted by: <demizu at dd.iij4u.or.jp>
MFC after: 3 days
|
|
|
|
|
|
|
| |
'do { ... } while (0)' macros.
PR: kern/83088
Sumbitted by: <antoine.brodin at laposte.net>
|
|
|
|
|
|
| |
This also fixes a few races that was present in the timeout/detach code.
Sponsored by: pair.com
|
| |
|
| |
|
|
|
|
|
|
| |
to rl_stop() accessing already freed "struct ifnet".
Fixed LOR between rl mutex and some ACPI mutex in rl_detach().
|
|
|
|
| |
already freed struct ifnet.
|
|
|
|
|
|
|
| |
IPv6 opcodes which are behind #if(n)def INET6 now.
PR: kern/85826
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
| |
risky because the "current time" is supposed to be fed to the card during
initialization, and the current time is supposed to be put into each command
that is sent to the card. Hopefully either the card doesn't actually care
about the timestamps, or it doesn't care about the absolute values so long
and the relative values are consistent. Not an MFC candidate until more
thorough testing can be done.
|
|
|
|
|
|
|
| |
While I'm here add KASSERT(9) to notify failure of SYSUNINIT handler.
Reported by: Ben Kaduk < minimarmot AT gmail DOT com >
Tested by: Ben Kaduk < minimarmot AT gmail DOT com >
|
| |
|
|
|
|
|
|
| |
o Use pccard_cis_scan
o use pccard_attr_write_1
o Update comments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Attach AX88x90's MII bus to system, and require its presence.
o Reorg the mii code a little, and move more of it into pccard attachment.
o Eliminate ed_pccard_{read,write}_attrmem in favor of a more appropriate
function in the pccard layer.
o Update comments to reflect knowledge gained.
o Update how re recognize a NE-2000 ROM. I found a couple of different
datasheets that define the structure of the PROM data, so the code's
old heuristics have been removed, and comments updated to reflect the
structure.
o Eliminate work around for EC2T. It is no longer needed, and was wrong
headed since the EC2T has a Winbound 82C926C in it, not a AX88x90.
o Add copyright to if_ed_pccard.c, since I believe I've re-written more than
3/4 of it.
# With these changes, all of my 20-odd ed based cards work, except for the
# NetGear FA-410, and I'm pretty sure that's a MII/PHY problem.
|
|
|
|
|
| |
o Move to new pccard_cis_scan convenience function.
o Remove compat layer goo.
|
|
|
|
| |
use version.
|
| |
|
|
|
|
|
| |
with edX at pciY. This removes 8*22 bytes from the strings. Not a
huge win, but a cheap one.
|
|
|
|
|
|
|
| |
attach to. These cards are combo cards (in that they have a modem
inside of them), but not true MFC cards. Full support of these cards
will have to wait until we can pick the config to use and for the PFC
support that I have brewing.
|
|
|
|
| |
memory, the CCR and a tweak to cis_scan.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fifo_kqfilter() VOP implementations, since they in theory are used
only on open file descriptors, in which case the ioctls are via
fifo_ioctl_f() and kqueue requests are via fifo_kqfilter_f().
Generate warnings if they are entered for now. These printf()
calls should become panic() calls.
Annotate and re-implement fifo_ioctl_f(): don't arbitrarily
forward ioctls to the socket layer, only forward the ones we
explicitly support for fifos. In the case of FIONREAD, don't
forward the request to the write socket on a read-write fifo, or
the read result is overwritten. Annotate a nasty case for the
undefined POSIX O_RDWR on fifos, in which failure of the second
ioctl will result in the socket pair being in an inconsistent
state.
Assert copyright as I find myself rewriting non-trivial parts of
fifofs.
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
be held when entering a kqueue filter for fifos via a socket buffer
event: as such, assert the lock unconditionally rather than acquiring
it conditionall.
MFC after: 3 days
|
|
|
|
| |
This should fix LOR(in fact it's not LOR) in device attach.
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) fifo_kqfilter() is not actually ever used, it likely should be GC'd.
2) fifo_kqfilter_f() doesn't implement EVFILT_VNODE, so detecting events
on the underlying vnode for a fifo no longer works (it did in 4.x).
Likely, fifo_kqfilter_f() should forward the request to the VFS using
fp->f_vnode, which would work once fifo_kqfilter() was detached from
the vnode operation vector (removing the fifo override).
Discussed with: phk
|
| |
|
|
|
|
| |
- Add '-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3' to CFLAGS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
used when a read filter is requested on a write-only fifo descriptor, or
a write filter is requested on a read-only fifo descriptor. This
permits the filters to be registered, but never raises the event, which
causes kqueue behavior for fifos to more closely match similar semantics
for poll and select, which permit testing for the condition even though
the condition will never be raised, and is consistent with POSIX's notion
that a fifo has identical semantics to a one-way IPC channel created
using pipe() on most operating systems.
The fifo regression test suite can now run to completion on HEAD without
errors.
MFC after: 3 days
|
|
|
|
|
|
| |
is requested on a network interface file descriptor that is non-applicable.
MFC after: 3 days
|
|
|
|
|
|
| |
kqueue filter type is requested on a vnode.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove an assertion in sound.c, it's not needed (and causes a panic now).
From the conversation via mail between glebius and Ariff:
---snip---
> Well, but which mutex protects now? Do we own anything else
> in pcm_chnalloc()? I see some queue(4) macros in pcm_chnalloc(),
> they should be protected, shouldn't they?
Queue insertion/removal occur during
1) driver loading (which is pretty much single thread /
sequential) or unloading (mutex protected, bail out if there is
any channel with refcount > 0 or busy).
2) vchan_create()/destroy(), (which is *sigh* quite complicated), but
somehow protected by 'master'/parent channel mutex. Other
thread cannot add/remove vchan (or even continue traversing
that queue) unless it can acquire parent channel mutex.
---snip---
Fix the locking in dsp.c to prevent a LOR (AFAIK not on the LOR page).
Submitted by: Ariff Abdullah <skywizard@MyBSD.org.my>
Tested with: INVARIANTS[1] and DIAGNOSTICS[2]
Tested by: netchild [1,2], David Reid <david@jetnet.co.uk> [1]
|
|
|
|
|
|
|
| |
apply to the fifo (i.e., not EVFILT_READ or EVFILT_WRITE), reject
it as EINVAL, not by returning 1 (EPERM).
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
'buffers' pending NMIs from multiple interrupting PMCs and delivers
them serially.
Reported by: Olivier Crameri <olivier.crameri@epfl.ch>
MFC after: 3 days
|
|
|
|
|
| |
Approved by: anholt (mentor)
Discussed on: arch
|
|
|
|
|
|
| |
to userland program instead of letting it wait until end of days.
PR: kern/85907
|
| |
|
| |
|
|
|
|
|
|
| |
according to POSIX, not to mention the fact that it doesn't make sense
(and hence isn't really implemented). This causes the fifo_misc
regression test to succeed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file descriptor. Otherwise, the read end of a fifo might return that it
is writable (which it isn't).
Only poll the fifo for write events if the fifo attached to a writable
file descriptor. Otherwise, the write end of a fifo might return that
it is readable (which it isn't).
In the event that a file is FREAD|FWRITE (which is allowed by POSIX, but
has undefined behavior), we poll for both.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
to poll the write socket for, the fifo polling code proceeded to poll
for the complete set of events. Use 'levents' instead of 'events' as
the argument to poll, and only poll the write socket if there is
interest in write events.
MFC after: 3 days
|
|
|
|
|
|
| |
write socket.
MFC after: 3 days
|
|
|
|
|
|
|
| |
while sleeping to allocate fifo state: due to using the vnode lock to
serialize access to a fifo during open, it shouldn't happen (tm).
MFC after: 3 days
|
|
|
|
|
|
|
| |
by calling uipc_connect2() to connect two socket endpoints to create a
fifo, call soconnect2().
MFC after: 3 days
|
|
|
|
| |
by handling all the cookie stuff.
|