Age | Commit message (Collapse) | Author |
|
|
|
|
|
As usual with the fp suffix, the former wraps the latter with a file BIO.
There is no reason for this function to be in a separate file.
|
|
(sorry, otto, for not spotting in the updated diff)
|
|
|
|
From Ville Syrjala
726825297dd6aaa2d91daf7c1c2fd030859cc6cb in linux-6.1.y/6.1.24
76b767d4d1cd052e455cf18e06929e8b2b70101d in mainline linux
|
|
From Ville Syrjala
64244a900ddff4abd4c894dcfa9ea7df898ad1eb in linux-6.1.y/6.1.24
05ca98523481aa687c5a8dce8939fec539632153 in mainline linux
|
|
From Imre Deak
1297278ce23977853afeac7bfb65e42450a722dd in linux-6.1.y/6.1.24
eb50912ec931913e70640cecf75cb993fd26995f in mainline linux
|
|
From Imre Deak
0c64d72fd3f21ac9d0da186809394d9593090ce7 in linux-6.1.y/6.1.24
e761cc20946a0094df71cb31a565a6a0d03bd8be in mainline linux
|
|
From Tim Huang
62de38c8201d853b130fc54ddbfab748180053e2 in linux-6.1.y/6.1.24
e11c775030c5585370fda43035204bb5fa23b139 in mainline linux
|
|
From Alex Deucher
73ca74fc7ab6c1679c3b2720579c0c20b73a9764 in linux-6.1.y/6.1.24
2a7798ea7390fd78f191c9e9bf68f5581d3b4a02 in mainline linux
|
|
From Roman Li
245525543f48cd9eabd2964d8931043e9e3c31cf in linux-6.1.y/6.1.24
3f6752b4de41896c7f1609b1585db2080e8150d8 in mainline linux
|
|
From Min Li
240b1502708858b5e3f10b6dc5ca3f148a322fef in linux-6.1.y/6.1.24
dc30c011469165d57af9adac5baff7d767d20e5c in mainline linux
|
|
From Tvrtko Ursulin
4e29fb89f771316caed9e4d166213b10dd49eb2e in linux-6.1.y/6.1.24
dc3421560a67361442f33ec962fc6dd48895a0df in mainline linux
|
|
|
|
spotted by brynet
|
|
endbr64 (f3 0f 1e fa) is placed at valid targets of an indirect jmp or
call. A nop on older machines. When IBT is enabled, an indirect jmp or
call with no endbr will trigger a control protection trap.
IBT is present on Intel Tiger Lake (Core gen 11) and later.
with and ok deraadt@
|
|
This is simpler than clearing the cet_u bits in the kernel.
ok guenther, kettenis
|
|
include endbr64 macros. That's not going to work, so use the simple method
of -Dendbr64= to remove them from the instruction stream.
ok kettenis guenther
|
|
use GENTRY() instead. Also add two endbr64 which cannot be supplied by
macros
ok guenther
|
|
The IDTVEC() and KIDTVEC() macros also get a endbr64, and therefore we need
to change the way that vectors are aliased with a new IDTVEC_ALIAS() macro.
with guenther, jsg
|
|
-fcf-protection=none, regardless of what the compiler default is.
-fcf-protection=branch puts endbr64 instructions on functions which could
be reached indirectly.
ok guenther kettenis
|
|
|
|
cq_shadow is a private copy of the running clock interrupt passed to
cl_func() during the dispatch loop. It resembles the real clockintr
object, though the two are distinct (hence "shadow"). A private copy
is useful for two reasons:
1. Scheduling operations performed on cq_shadow (advance, cancel,
schedule) are recorded as requests with the CLST_SHADOW_PENDING
flag and are normally performed on the real clockintr when cl_func()
returns. However, if an outside thread performs a scheduling
operation on the real clockintr while cl_func() is running, the
CLST_IGNORE_SHADOW flag is set and any scheduling operations
requested by the running clock interrupt are ignored.
The upshot of this arrangement is that outside scheduling operations
have priority over those requested by the running clock interrupt.
Because there is no race, periodic clock interrupts can now be safely
stopped without employing the serialization mechanisms needed to safely
stop periodic timeouts or tasks.
2. &cq->cq_shadow is a unique address, so most clockintr_* API calls
made while cl_func() is running now don't need to enter/leave
cq_mtx: the API can recognize when it is being called in the midst
of clockintr_dispatch().
Tested by mlarkin@. With input from dlg@.
In particular, dlg@ expressed some design concerns but then stopped
responding. I have changes planned to address some of the concerns.
I think if we hit a wall with the current clockintr design we could
change the allocation scheme without too much suffering. I don't
anticipate there being more than ~20 distinct clock interrupts.
|
|
the install media would grow too much, so use the same strategy as we
for stack protector and other things: disable them, just on the install
media
ok kettenis
|
|
except for bootblocks. This way we have built-in leak detecction
always (if enable by malloc flags). See man pages for details.
|
|
malloc (leak) dump fucntion. ok semarie@
|
|
|
|
sk_OPENSSL_STRING_pop_free() is much more explicit and isn't that much
more complicated. x509_util.c can also use it directly...
No binary change
|
|
|
|
|
|
|
|
ok jsg@
|
|
ok tb@
|
|
ok tb@
|
|
While here, use KECCAK_BYTE_WIDTH instead of hardcoding the value.
|
|
ok deraadt@
|
|
Comment incorrectly mentioned returning sectors when this function
returns bytes; the logic in virtio.c computes the number of 512
byte sectors after calling virtio_raw_init.
While here, adjust the formatting of return's to match the rest of vmd.
No functional change.
|
|
Some mild tidying of fd closing in the vmm process in prep for
landing parts of my fork+exec diff.
With input from guenther@ on the nuances of if/when EINTR may happen
in a call to close(2).
ok mlarkin@
|
|
bindings are still preliminary I don't exepect any substantial changes
that would affect the driver. Hopefully the bindings will end up
officially approved before OpenBSD 7.4 gets released.
ok patrick@
|
|
|
|
In addition, ext_cmp() was already prototyped earlier...
|
|
|
|
|
|
|
|
There is no point in having this in a separate internal header.
discussed with jsing
|
|
implemented. This leads to hangs when we run "ttyflags -a" in /etc/rc.
Add the same probe that we have in the ISA version of the driver to make
sure the port is actually there.
ok patrick@
|
|
ioctls. Everything we need from them is handled by wsdisplay(4) already,
but we need to handle them here to signal that we actually implement
burner support.
ok tb@, tobhe@
|
|
in a new pm_guarded member of struct pmap and using this member to add
the bits to the PTEs
ok deraadt@
|
|
PT_CONTINUE ptrace(2) request. Otherwise we would trap if userland was
interrupted at a point where it is doing an indirect branch that has set
the bits but before it has executed the BTI instruction at the branch
target.
The PT_SETREGS request may need similar treatment, at least when the
PC is changed. But Linux doesn't do this and debuggers might want full
control over the BTYPE bits. So leave this alone for now.
ok guenther@
|