| Age | Commit message (Collapse) | Author |
|---|
|
side of RFC7911 and the send portion will follow.
The path-id is extracted from the NLRI encoding an put into struct
prefix. To do this the prefix_by_peer() function gets a path-id
argument. If a session is not path-id enabled this argument will
be always 0. If a session is path-id enabled the value is taken
from the NLRI and can be anything, including 0. The value has no
meaning in itself. Still to make sure the decision process is able
to break a tie the path-id is checked as the last step (this is not
part of the RFC but required).
OK benno@
|
|
opened exclusively, and the flags argument is passed to usbd_setup_xfer().
USBD_EXCLUSIVE_USE has the same value as USBD_NO_COPY, which means that
data transferred would not be copied to the buffer where the driver expects
it.
None of these drivers actually used the interrupt data for anything, and
in some the interrupt pipe code was #if 0'd out, so this doesn't change
anything, but fixing this up prevents unwary developers like me from
copying code that doesn't work.
ok mglocker@
|
|
avoids LogLevel=verbose (or greater) messages from ssh appearing
after scp has returned exited and control has returned to the
shell; ok markus@
(this was originally committed as r1.223 along with unrelated stuff that
I rolled back in r1.224)
|
|
|
|
more useful with long paths (that may truncate) and better
matches traditional scp behaviour; spotted by naddy@
ok deraadt@
|
|
avoids LogLevel=verbose (or greater) messages from ssh appearing
after scp has returned exited and control has returned to the
shell; ok markus@
|
|
and make it clear that the config file *modifies* the defaults rather
than *control* them, and that having a config file is optional;
tweak and OK jmc@, OK tim@
|
|
to find the VBT
ok jsg
|
|
actually need, and fewer things that they won't need. In particular don't
rely on default auth/enc settings; SNMPv3 isn't algorithm-agile, it must
be defined on both ends, so relying on a default is going to cause some
problems if it ever does change.
|
|
Practical experience on several machines after updates suggests the snmp
world isn't really ready for hmac-sha2-256, and the HMAC construction doesn't
require collision resistance (which is the weakness of MD5/SHA1; see e.g.
"New proofs for NMAC and HMAC: Security without collision-resistance",
Bellare 2014).
Feedback from martijn@ (who would prefer to keep using the sha2 hmac),
deraadt@, tb@.
|
|
|
|
goetze at dovetail.com, ok djm@ deraadt@
|
|
implicit 'in "$@"' after 'for i'.
|
|
change this and having it in the same hunk as the CVS Id string means
applying changes fails every. single. time.
|
|
scp and sftp like to add -q to the command line passed to ssh which
overrides the LogLevel we set in the config files and suppresses output
to the debug logs so drop any "-q" from the invoked ssh. In the one
case where we actually want to use -q in the banner test, call the ssh
binary directly bypassing the logging wrapper.
|
|
|
|
cases. Make it so.
In passing nuke a single use 'error' variable and move an *errstr
declaration nearer to its friends.
No intentional functional change.
|
|
|
|
|
|
|
|
|
|
Delete ugly and incorrect workaround for a Linux kernel bug.
If a file is temporarily empty, that by no means implies
it might be permanently non-seekable.
Patch from seL4 at disroot dot org on tech@.
OK both Theos: tb@ and deraadt@
|
|
and add the missing .Xr to weekly(8);
no text change
|
|
i wrote this diff more than a year ago, then forgot it
even though millert@ and jung@ OK'ed it back then
|
|
This driver does not need to allocate a DMA segment for the Tx scheduler.
Instead this driver uses the scheduler byte count array which is allocated
per Tx ring. Remove sc->sched_dma and related code inherited from iwm(4).
Patch by zxystd from OpenIntelWireless.
|
|
This tries to reaquire the current lease and if that failes will send
a DHCPDISCOVER message to request any lease.
OK benno
|
|
prompted by jcs@ reporting a protection fault trap in
drm_mode_rmfb_work_fn() while playing a youtube video in firefox on a
kaby lake machine. He later saw the same trace on tiger lake.
The arguments to drm_mode_rmfb_work_fn() are on the stack in
drm_mode_rmfb() with flush_work() called before return.
taskq_barrier() is only a barrier for running not queued tasks.
I suspect the linux functions expect any previously queued work to
complete not just any currently running work. I'm not sure if the
difference matters in practice.
|
|
|
|
|
|
remove unused variable
|
|
expected status replies from the server to what do_download()
was using.
Refactor it to use the same structure and factor out some common
code into helper functions.
|
|
ok markus@
|
|
ok markus@
|
|
over the wire
|
|
suppressing "Retrieving [path]" lines that were emitted to support
the interactive sftp(1) client. ok markus@
|
|
crossloading; ok markus@
|
|
feedback/ok markus@
|
|
from one SFTP server while simultaneously uploading to another.
feedback & ok markus@
|
|
"looks fine" markus@
|
|
|
|
forgotten in earlier commits
|
|
using input from tb@, and OK tb@ on an earlier version
|
|
OK schwarze@
|
|
as intentionally undocumented because it is trivial and unused in the wild;
OK tb@
|
|
This fixes a panic that was reported on misc@ and bugs@ by
Mike <the.lists () mgm51 ! com> and
Anindya Mukherjee <anindya49 () hotmail ! com>
OK jcs@, thanks to mpi@/jcs@ for the pointers!
|
|
code.
'-g' is promoted to be independant of '-i'. This makes it clearer
that there are four mutually exclusive initialization options.
'-i' puts the default MBR on disk, '-g' puts the default GPT on
disk, '-u' updates the MBR boot code on disk and '-A' puts a new
set of GPT partitions on disk without overwriting 'protected'
partitions.
The last initialization option specified is the one executed, so
existing '-i -g' finger memory, etc. continue to work as before.
man page/usage feedback/tweaks from jmc@
|
|
|
|
|
|
so compare in both directions with just -r, which should catch missing files
in either directory.
|
|
spaces, from Anindya Mukherjee. Also a typo fix from Linus Arver.
|
