| Commit message (Collapse) | Author | Files | Lines |
|
|
|
(Especially adding IF_DROP() after IFQ_ENQUEUE() was completely wrong because
IFQ_ENQUEUE() already does it. Oops.)
After this revert, the situation becomes:
- if_snd.ifq_drops is incremented in either IFQ_ENQUEUE() or IF_DROP(), but
it is not shown to userland, and
- if_data.ifi_oqdrops is shown to userland, but it is not incremented by
anyone.
|
|
|
|
OK deraadt@
|
|
|
|
|
|
from comet (freebsd 116952), via richard
|
|
development of tame? option CD9660 and mount_cd9660 are already
absent, so remove the cd(4) driver
ok miod
|
|
ok benno
|
|
carefully.
|
|
|
|
mpi@ prefers checking IFQ_ENQUEUE() error, and this matches that.
OK dlg@
|
|
mpi@ plans to clean-up IF_DROP()'s, but fix consistent use of it for now.
OK dlg@
|
|
|
|
- tmppath for when mktemp() operates in /tmp proper
- cpath+wpath for use of $TMPDIR
based on log-message from previous commit
ok deraadt@
|
|
OK mpi@ dlg@
|
|
mpi@ questioned usefulness of if_snd.ifq_drops, but this is what exists now.
This area is going to be readily polished.
OK dlg@
|
|
OK mpi@ dlg@
|
|
enter the fork+execve codepath. That allows use of "stdio getpw rpath"!
Use of -exec methods have been discouraged for years anyways, with
-print0/xargs -0 now considered safer practice.
ok guenther millert
|
|
Necessary bumps in Ports will be handled by sthen@.
OK mpi@ dlg@
|
|
uses can tame "stdio wpath rpath cpath tmppath". tmppath for when
mktemp() operates in /tmp proper, but cpath+wpath for use of $TMPDIR.
ok sthen millert
|
|
this function could only return 0 or 1, and 1 on error.
avoid to deref an uninitialised variable if rtget() return an error.
ok millert@ benno@ deraadt@
|
|
|
|
fairly easy to audit by running nm and noticing nothing beyond base
stdio except for fopen/freopen. Then review all callpaths to those
functions, and place the tame() calls.
ok sthen
|
|
stdin, an additional tame "stdio" is easy.
same diff from sthen
|
|
to handle the stdin case without rpath, but it looks a bit invasive.
ok sthen
|
|
at a time. The newstate task now always transitions to the most
recently requested state, rather than hopping along with every request.
This allows us get rid of the silly newstate generation counter, and
we can now task_del() a pending transition when the interface goes down.
While several issues with this driver remain, I believe this change
does not introduce new problems.
Tested by myself, jasper@, and zhuk@
|
|
This is slightly refactored version of the diff by jmatthew@
that makes use of a single per-trunk task but retains per-port
mbuf queues.
Running LACP frame processing in a task context allows a simple
way to synchronize changes to the trunk ports and trunk itself
performed from the ioctl, timeout and task contexts with a kernel
lock.
OK mpi
|
|
NUMBOOT arch is left: Vax.
|
|
|
|
|
|
checking for truncation every time we touch the string, simply allocate
a memory chunk large enough to store the full path.
|
|
process which involves fork+execve....
ok doug
|
|
with mode "w", as root, since "w" implies O_CREAT. That will create
the raw file in /dev if it does not yet exist (due to a lie in utmp).
It should use "r+", to open it for for O_RDWR only.
Oh man this reminds me of 1988, how old is this bug?
ok doug
|
|
is stdin, then we can drop directly to tame "stdio"
ok doug
|
|
fchmod's them, and possibly renames them.
ok doug
|
|
|
|
diff from Yuuichi Someya
|
|
getpw/gr type functions allowed in that set.
ok doug
|
|
very early on, but next() can open one quite late.
ok doug
|
|
|
|
operated on switch to tame "stdio". Reformat a very ugly code block
without braces to squeeze the tame calls in.
ok doug
|
|
|
|
|
|
after file from argv. If it is discovered to be reading from stdin only,
go to tame "stdio"
ok doug
|
|
20151005171301+1.09Z to be treated as a valid time.
ok beck@
|
|
opening files, but no... a file could indicate nested import of another
file, so rpath is needed.
ok doug
|
|
or if it has bugs. The previous commits by schwarze indicate the latter
case was very true until recently...
ok doug
|
|
foreign-data pipeline, and happens to contain a string handling bug, i do
not want it being controlled to open a socket.
ok doug
|
|
success could be because our getcwd() is backed by a system call, unlike
historical practice. Didn't think it through competely, but this could
burn someone else later, if they try to port this code to another system.
Anyways, good enough for us.
all cases tested by doug
|