| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
but should be called with the topology lock held and returns with the
topology lock held and empty event queue.
Approved by: phk (sometime ago)
|
|
|
|
| |
Noticed by: pjd
|
|
|
|
|
| |
DIRTY flag can be removed in idle process. Use consumer's acw field
instead to avoid opening consumer twice.
|
|
|
|
|
| |
it isn't used for anything anywhere and the vnode_pager would explode
if we attempted to.
|
|
|
|
|
|
| |
check if provider is open for writing.
This fixes panic when device is open only for writing and we send write
request.
|
|
|
|
| |
Eliminate use of vn_todev() while here.
|
|
|
|
|
| |
It was only used for the highly dangerous "export all vnodes with a sysctl"
function.
|
| |
|
|
|
|
|
| |
start with, so let it die in peace. While there, remove Multia-class
as 486-like performance will not buy us much when 6.x arrives.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
the change in the default behavior may break existing, working setups.
Requested by: brooks
|
|
|
|
| |
stability anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
transfer timeouts that typically cause a transfer to be completed
twice, resulting in panics and page faults:
o A transfer completion interrupt could arrive while an abort_task
event was set up, so the transfer would be aborted after it had
completed. This is very easy to reproduce. Fix this by setting
the transfer status to USBD_TIMEOUT before scheduling the
abort_task so that the transfer completion code will ignore it.
o The transfer completion code could execute concurrently with the
timeout callout, leaving the callout blocked (e.g. waiting for
Giant) while the transfer completion code runs. In this case,
callout_stop() does not prevent the callout from running, so
again the timeout code would run after the transfer was complete.
Handle this case by checking the return value from callout_stop(),
and ignoring the transfer if the callout could not be removed.
o Finally, protect against a timeout callout occurring while a
transfer is being aborted by another process. Here we arrange
for the timeout processing to ignore the transfer, and use
callout_drain() to ensure that the callout has really gone before
completing the transfer.
This was tested by repeatedly performing USB transfers with a timeout
set to approximately the same as the normal transfer completion
time. In the PR below, apparently this occurred by accident with a
particular printer and the default timeout.
PR: kern/71491
|
|
|
|
| |
port X' message.
|
|
|
|
|
|
|
|
| |
This also gives us ability to close PR.
PR: kern/42352
Approved by: julian (mentor)
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: OGAWA Takaya
MFC after: 1 day
|
|
|
|
|
|
|
|
| |
not --line-bufferring.
PR: docs/72985
Submitted by: John Engelhart <johne@zang.com>
MFC after: 1 week
|
|
|
|
|
| |
For setjmp() and longjmp(), put the signal mask where it's supposed to be,
instead of in the space reserved for fp regs.
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
| |
should fix the problems introduced several hours ago.
|
|
|
|
| |
Submitted by: Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
|
|
|
|
| |
Submitted by: Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
|
|
|
|
| |
These can also be used for prototypes in the pagers.
|
| |
|
|
|
|
| |
Reminded by: ru
|
|
|
|
|
|
| |
changes associated with adding System V IPC support. This will prevent
old modules from being used with the new kernel, and new modules from
being used with the old kernel.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These can be used to pass extra options to the mdmfs(8) utility,
to customize the finer details of the md file system creation
(i.e. to turn on/off softupdates, to specify a default owner for md
filesystem, etc).
Use these two new flags to mount tmpmfs and varmfs without
softupdates, since it doesn't make much sense to use SU on
malloc-backed file systems.
Reviewed by: mtm
Inspired by: J. D. Bronson, jbronson at wixb dot com
|
|
|
|
|
| |
Bug report by: <james@towardex.com>
MFC after: 2 weeks
|
|
|
|
| |
1.256 -> 1.261 ja_JP.eucJP/hardware/common/dev.sgml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
appropriate for different tag requirements. With the former global pool,
bounce pages might get allocated that are appropriate for one tag, but not
appropriate for another, but the system had no way to distinguish between them.
Now zones with distinct attributes are created to hold pages, and each tag
that requires bouncing is associated with a zone. New zones are created as
needed if no existing zones can meet the requirements of the tag. Stats for
each zone are tracked via the hw.busdma sysctl node.
This should help drivers that are failing with mysterious data corruption.
MFC After: 1 week
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
changes, start on a new line. Insertion of a filename will keep the
diff limited to the block of filenames that have the same first letter
instead of creating a huge diff. While here, move remote.c after the
remote-*.c files and move tui.c after the tui-*.c files. This matches
the order of ls(1) and makes it easier to compare object files created
by a stock gdb(1) build with the list of files we have here.
This is a non-functional change only.
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
|
|
| |
switching. Don't initialize variables in their declaration. Reduce stack
usage for device names. Minor style cleanups.
MFC after: 1 week
|
|
|
|
|
|
| |
Noticed by: trhodes
Pointy hat: kensmith
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
| |
visible when <sys/resource.h> is included.
|
| |
|
|
|
|
| |
won't boot a pre-5.1 development amd64 kernel. That's no big loss though.
|
| |
|
|
|
|
| |
MFC after: 3 days
|