IABSD.fr/src
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
d84d1dff | 2025-05-03 08:39:33 | CTASSERT that internal pub/priv keys match the sizes exposed in mlkem.h This will need reworking (especially deduplicating) anyway, but it doesn't hurt now. From Kenjiro Nakayama | |
|
88da34c4 | 2025-05-03 08:37:28 | Verify that the selected key share is indeed group 29 From Kenjiro Nakayama | |
|
3cbf0e89 | 2025-05-03 08:34:55 | mlkem_unittest: check return value of decap() From Kenjiro Nakayama | |
|
b20b0386 | 2025-05-03 08:34:07 | mlkem_tests: add an empty line for consistency | |
 |
49b8b489 | 2025-05-03 05:26:23 | the argument name for -s was internally inconsistent. to fix it, i used "socket", like for bgpctl(8); ok dlg | |
 |
f7b96dac | 2025-05-03 00:17:00 | remove some debugging via printf add a closefrom() near the start ok dlg@ | |
|
cb563479 | 2025-05-02 23:50:18 | pledge; ok dlg@ | |
 |
5403d912 | 2025-05-02 18:44:25 | sync | |
|
0ab49d10 | 2025-05-02 18:44:03 | sync | |
|
0e444de8 | 2025-05-02 15:57:54 | sync | |
|
ddfb282a | 2025-05-02 15:35:26 | start placing new keys | |
 |
020c3892 | 2025-05-02 13:36:55 | The previous fix was flawed. We should only copy the minimum size of either EXT2_DINODE_SIZE or sizeof(dino). OK miod@ | |
 |
eca5c1b5 | 2025-05-02 13:35:59 | Add RK3528 support. ok patrick@ | |
 |
30d594ba | 2025-05-02 11:51:00 | cut some unneeded words ok dlg@ | |
 |
c3a83f5e | 2025-05-02 11:05:54 | improve docs around pkg_add -U, which is a modifier around installing a package/s, not around updating, despite various recommendations on a third-party "handbook" site (which has other bad advice too) and repeated on forums etc. ok jmc | |
|
9ad4325d | 2025-05-02 10:58:51 | 802.11AB -> 802.1AB | |
 |
0d2e4037 | 2025-05-02 10:44:20 | Fail early in VOP_READDIR if the vnode is not a VDIR. OK miod@ dlg@ tedu@ deraadt@ rsadowski@ | |
|
1649d3d8 | 2025-05-02 10:24:58 | spelling | |
 |
85862fa3 | 2025-05-02 10:19:09 | Wiring pages require a write lock. Found the hardway by naddy@. | |
|
9d9c9610 | 2025-05-02 10:14:46 | change some casts to constant suffixes ok bluhm@ | |
|
3c8ee0a7 | 2025-05-02 09:57:36 | avoid uninitialised var in ether_frm_send() error path found by smatch, ok deraadt@ dlg@ | |
 |
89551080 | 2025-05-02 09:56:01 | lldpd will try and run as the _lldpd user, not _lldp. | |
|
fd9fd692 | 2025-05-02 09:46:00 | allocate a uid/gid for lldpd to run with as an _lldpd user the net/lldpd port also uses _lldpd, and will now share with base. depending on which appears first (base or port _lldpd) determines which uid/gid will be used. neither base or port lldpds store anything on disk, the user and group are only used to drop privileges to and run as. discussed with and ok sthen@ deraadt@ | |
|
6dacfa3f | 2025-05-02 06:15:59 | add lldp(8), a command line tool for interacting with lldpd(8). lldp can fetch LLDP packets from lldpd and then pulls them apart and displays them. by default it shows a brief summary of the lldp neighbor ports and systems on all interfaces, but you can request verbose info and/or info only from specific local interfaces. now that i've done the easy part (implementing AF_FRAME and lldpd) it would be nice to get some help with the hard stuff (pretty printing strings in c). ok djm@ deraadt@ general enthusiasm from many | |
|
0a394c10 | 2025-05-02 06:12:53 | lldpd(8): a daemon that acts as an LLDP agent on Ethernet interfaces. lldpd uses the recently added AF_FRAME Ethernet sockets to listen for LLDP packets on all Ethernet interfaces in the system, and stores them so a lldp(8) client connecting to the control socket can fetch and display the packets. AF_FRAME means we can avoid BPF for receiving LLDP packets, which has a couple of benefits. firstly, BPF needs to look at all packets entering an interface so it can filter for the ones you're interested in, which is annoying for low packet/data rate protocols like LLDP. AF_FRAME is handled late in ether_input, and only after other protocols (like ip) are handled, so it's lower overhad compared to BPF listeners. secondly, attaching a BPF filter to new interfaces relies on having access to and the privileges to open /dev/bpf, while AF_FRAME provides a wildcard listener that is able to receive LLDP from all interfaces on a single socket, like how binding to on 0.0.0.0 with an AF_INET socket let's you receive packets for all the IPs on your system from a single socket. lldp can create and configure this socket when it starts up just use it from then on. this means lldpd is simpler and needs fewer privileges to operate than if it went the BPF route. at the moment lldpd only handles LLDP packet reception on all interfaces, you can't disable reception on interfaces yet. it also doesn't transmit LLDP packets (yet). there is no intention of implementing any protocol other than LLDP in this daemon either. ok djm@ deraadt@ general enthusiasm from many | |
|
1b042add | 2025-05-02 05:57:02 | common definitions for lldp protocol bits. | |
|
87a500d8 | 2025-05-02 05:04:38 | collect memory utilisation stats for struct rusage to report. i originally wanted to report the current memory sizes like what you see in top via struct kinfo_proc, but kettenis@ pointed me at how to do it as per the documentation and everyone's existing expectations. ok claudio@ who has been running this for months now. dedicated to tedu@ who loves it when i touch sys/proc.h. | |
|
7d4a6d53 | 2025-05-02 03:38:05 | handle NULL for the option data mbufs in the ethernet setsockopt handling setsockopt doesnt have to provide an optval, which appears to end up as a NULL mbuf. Reported-by: syzbot+bd55ef234c2340a5ceb0@syzkaller.appspotmail.com | |
|
993a129b | 2025-05-02 00:51:09 | record which timeouts are running so timeout_barrier can do less work. timeout_barrier (and timeout_del_barrier()) were naive and had to assume that the specified timeout could be running, and therefore unconditionally inserted a barrier task in the queue. however, it's possible that timeouts weren't running, so timeout_barrier also had to schedule the contexts that run the timeout queues to force the barrier task to be completed quickly. in practice timeout_barrier ended up generating a massive amount of work to provide guarantees for something that's only true a tiny (but critically important) fraction of the time. to mitigate this, the queue runners now keep track of which timeout they're running so timeout_barrier can check against it. if the specified timeout is not running, then the barrier isn't necessary and timeout_barrier can return early. there is a chance that the check timeout_barrier does will produce false positives if the timeout that produced the work that is running has been recycled and now has timeout_barrier called against it. the worst that will happen in this situation is we'll run the barrier task for no benefit. however, that is far better than the current situation where we schedule the barrier all the time and are now suffering for it. because timeout_barrier now knows if a context is running timeouts, it no longer has to wake up or schedule the context to run the barrier. it can assume it will be picked up because all these contexts loop until they run out of work. this also adds CIRCQ_INSERT_HEAD so we can put the barrier at the top of the todo list and get it run sooner. this means the timeout{_del}_barrier caller will wait less. ok mpi@ mvs@ visa@ | |
 |
9e51cf64 | 2025-05-01 15:05:05 | Show file path in error messages Reporting failure without telling which file amongst those passed on the command line is bogus does not really help. OK millert | |
|
c960bee9 | 2025-05-01 12:28:40 | RK3528 support. ok patrick@, jsg@ | |
 |
cabbd2e7 | 2025-05-01 11:19:46 | The egress group is automatically added to any interface that has a default route pointing to it. However, not all default routes are usable for traffic. Both blackhole and reject routes are unreachable, so do not add those to the egress group. found the hard way by tb@, debugged by myself and claudio@ OK tb@ claudio@ | |
|
dde7d5e3 | 2025-05-01 10:18:51 | Drop peeringdb support, they haven't been running a whois service for a while and suggest using GUI or HTTP API to retrieve information about an ASN, which is out of scope for whois(1). ok job@ | |
|
4a539f7d | 2025-05-01 07:27:11 | More space around .Dl + a typo on top | |
 |
54c41a8e | 2025-05-01 07:12:00 | Add an option variation-selector-always-wide to instruct tmux not to always interpret VS16 as a wide character and assume the terminal does likewise. This is behaviour seen in a number of newer terminals' Unicode 14 support but not in older terminals; it seems to be a little contentious and is currently difficult to detect. Probably in the long run tmux should pick a behaviour, look at a (new) terminfo(5) capability to tell it what the terminal will do, and emulate as required, but at this point I'm not sure that is worth it for something where support is mixed, seems to be in flux, and that mostly only matters for emojis. GitHub issues 3923 and 4475 and others before that. | |
|
903376cb | 2025-05-01 06:59:32 | Don't map 256 to white-on-white either, and tidy code a bit. | |
|
ee03ca45 | 2025-05-01 06:58:21 | check that P_TIMEOUTRAN is also not set going into sleep_finish. | |
|
17c73a2a | 2025-05-01 01:43:10 | avoid sleeping and therefore SCHED_LOCK while holding timeout_mutex. this was necessary back in kern_timeout.c r1.50 to avoid deadlocks, but was lost when TIMEOUT_MPSAFE was introduced in r1.96. we've gotten away with it for the last year or so, but it feels like a trap for the future. ok tedu@ mpi@ | |
|
b108d39a | 2025-05-01 01:16:42 | remove flag setting from wakeup_proc(). only endtsleep() sets flags via wakeup_proc, but it sets it's own flags later. we can use the return value from wakeup_proc and the existing flag setting to get the same effect. ok tedu@ claudio@ mpi@ visa@ | |
|
aa7052e7 | 2025-05-01 01:10:08 | refactor some code in pf_test to test the pf_state pointer fewer times. there should be no functional change with this diff. note that pf_state structs always have valid references to pf_state_keys until the pf_state itself is destroyed after pf.c r1.1157. this means we don't have to test if the st->key[PF_SK_STACK] pointers are valid anymore, we can just use them. ok sashan@ | |
|
fe009f23 | 2025-05-01 00:35:23 | lhash: add missing spaces before assignment operator | |
|
6c2f84fc | 2025-05-01 00:32:38 | enable af_frame. this paves the way for lldp support in base. ok deraadt@ djm@ general enthusiasm from others | |
 |
16e894ce | 2025-04-30 18:38:20 | Do not allow readdir and readdirplus NFS operations on non-directory vnodes; reported by Claes M Nyberg to bugs@, ok claudio@ | |
|
8e2d8607 | 2025-04-30 13:50:50 | tlsext: stop sending SNI before ALPN in clients All supported releases of LibreSSL ensure that the corresponding callbacks are called in a predefined order rather than honoring the order in which a client sends its extensions. Therefore the ALPN callback for apache-httpd's virtual host setups can rely on SNI information being available and we no longer need to work around this on hte client side. Cuts the amount of code needed for tlsext randomization in half. ok jsing | |
|
45861874 | 2025-04-30 13:44:54 | tlsexttest: remove check that clients receive SNI before ALPN The next commit will remove the kludge for compatibility of Apache with older libressl, so remove the corresponding regress coverage and only check that PSK is the last extension. | |
 |
3c7e053c | 2025-04-30 12:35:37 | m88k: Use MI soft interrupt code Tested by and OK miod@ aoyama@ | |
|
32be5392 | 2025-04-30 12:30:54 | sh: Use MI soft interrupt code Feedback and OK miod@ | |
 |
88a96892 | 2025-04-30 09:40:37 | Move vmm(4) extern declarations from .c to vmm.h header file. from hshoexer@; OK kettenis@ dv@ mlarkin@ | |
|
aadb1b15 | 2025-04-30 05:26:15 | make writing known_hosts lines more atomic, by writing the entire line in one operation and using unbuffered stdio. Usually writes to this file are serialised on the "Are you sure you want to continue connecting?" prompt, but if host key checking is disabled and connections were being made with high concurrency then interleaved writes might have been possible. feedback/ok deraadt@ millert@ | |
|
332698a8 | 2025-04-30 05:23:15 | fix a out-of-bounds read if the known_hosts file is truncated after the hostname. Reported by the OpenAI Security Research Team ok deraadt@ | |
|
63effc54 | 2025-04-30 03:54:09 | mop up P-192/Group 25 remnants based on an initial diff by markus | |
|
4ad49911 | 2025-04-30 03:53:21 | mop up P-192/Group 25 remnants based on an initial diff by markus | |
|
b6c91c45 | 2025-04-30 03:51:42 | mop up P-192/Group 25 remnants based on an initial diff by markus | |
|
3f24670b | 2025-04-30 00:45:08 | avoid timeout_del_barrier when cancelling the timeout in sleep_finish. because of src/sys/kern/kern_timeout.c r.1.101, timeout_del_barrier now unconditionally calls timeout_barrier. timeout_barrier now unconditionally queues a timeout and tries to "wake up" the context that services the queue of pending timeouts, which in this case is the softclock interrupt. unfortunately softclock isn't MPSAFE, so it tries to take the kernel lock, which is often already held by another part of the system. bluhm@ has a network stress test which manages to produce this contention almost 100% of the time, and the performance is terrible because of it. sleep_finish is currently relying on timeout_del_barrier to ensure that the endtsleep handler has finished running. this diff changes it so sleep_finish tracks where endtsleep is up to itself, which avoids the timeout barrier, which in turn avoids the kernel lock contention. this comment added to the code explains it further: /* * There are three situations to handle when cancelling the * p_sleep_to timeout: * * 1. The timeout has not fired yet * 2. The timeout is running * 3. The timeout has run * * If timeout_del succeeds then the timeout won't run and * situation 1 is dealt with. * * If timeout_del does not remove the timeout, then we're * handling 2 or 3, but it won't tell us which one. Instead, * the P_TIMEOUTRAN flag is used to figure out when we move * from 2 to 3. endtsleep() (the p_sleep_to handler) sets the * flag when it's finished running, so we spin waiting for * it. * * We spin instead of sleeping because endtsleep() takes * the sched lock to do all it's work. If we wanted to go * to sleep to wait for endtsleep to run, we'd also have to * take the sched lock, so we'd be spinning against it anyway. */ ok visa@ claudio@ mpi@ tested by bluhm@ i forgot this as part of src/sys/kern/kern_synch.c r1.221 | |
|
629d3ef5 | 2025-04-30 00:26:02 | avoid timeout_del_barrier when cancelling the timeout in sleep_finish. because of src/sys/kern/kern_timeout.c r.1.101, timeout_del_barrier now unconditionally calls timeout_barrier. timeout_barrier now unconditionally queues a timeout and tries to "wake up" the context that services the queue of pending timeouts, which in this case is the softclock interrupt. unfortunately softclock isn't MPSAFE, so it tries to take the kernel lock, which is often already held by another part of the system. bluhm@ has a network stress test which manages to produce this contention almost 100% of the time, and the performance is terrible because of it. sleep_finish is currently relying on timeout_del_barrier to ensure that the endtsleep handler has finished running. this diff changes it so sleep_finish tracks where endtsleep is up to itself, which avoids the timeout barrier, which in turn avoids the kernel lock contention. this comment added to the code explains it further: /* * There are three situations to handle when cancelling the * p_sleep_to timeout: * * 1. The timeout has not fired yet * 2. The timeout is running * 3. The timeout has run * * If timeout_del succeeds then the timeout won't run and * situation 1 is dealt with. * * If timeout_del does not remove the timeout, then we're * handling 2 or 3, but it won't tell us which one. Instead, * the P_TIMEOUTRAN flag is used to figure out when we move * from 2 to 3. endtsleep() (the p_sleep_to handler) sets the * flag when it's finished running, so we spin waiting for * it. * * We spin instead of sleeping because endtsleep() takes * the sched lock to do all it's work. If we wanted to go * to sleep to wait for endtsleep to run, we'd also have to * take the sched lock, so we'd be spinning against it anyway. */ ok visa@ claudio@ mpi@ tested by bluhm@ | |
|
4a6e8021 | 2025-04-29 20:31:42 | Remove dead flag from TCP SYN cache. The TCP SYN cache timer uses SCF_DEAD flag to detect closed listen socket. Note that syn_cache_rm() is setting sc_inplisten to NULL in the same atomic section where SCF_DEAD is set. Also syn_cache_timer() uses the SYN cache mutex to check sc_inplisten and SCF_DEAD together. Eliminate SCF_DEAD and rely on existing pointer to listen socket. OK mvs@ | |
|
8ad05e6c | 2025-04-29 20:19:48 | Remove useless parentheses. spotted by dv@ | |
|
f2a019ad | 2025-04-29 18:35:51 | Sprinkle some -n to route commands to avoid DNS lookups. Running these regress tests should also work with a broken network. | |
|
eacfe1d9 | 2025-04-29 17:44:00 | remove references to fs.posix.setuid; ok tedu | |
|
dd3d2b7b | 2025-04-29 14:53:22 | In TCP software LRO remove potential ethernet padding. With some network interfaces the RX mbuf returned from the driver may contain ethernet padding. My tests did not see this behavior with ixl(4) hardware. But inserting ethernet padding into a TCP stream would be completely wrong, so adding a sanity check anyway. Remove content of the mbuf that is behind the TCP payload. OK jan@ | |
 |
38a4e071 | 2025-04-29 13:45:01 | Add Qualcomm CRD ok patrick@ kettenis@ | |
|
b1cd6c14 | 2025-04-29 13:40:26 | Fix leak of peerid.id_buf ok markus@ | |
|
a128edeb | 2025-04-29 13:21:52 | vmm(4) must not use 0 as minimum ASID for AMD SEV. If SEV-ES is not supported by CPU, vmm(4) could end up using 0 as minimum ASID. In this case, 1 has to be used. regression found and tested by Jesper Wallin; fixed with hshoexer@ | |
|
aada0332 | 2025-04-29 13:12:51 | allocate pf states and state keys on cache lines. the idea is to try and avoid false aliasing of pf states as we become more parallel in the future. i also want this as a reminder to stop wasting my time optimising for memory usage. i've been running this for years without issue. ok sashan@ (in mar 2023). he agrees that if it sucks we can pull it out. | |
|
785f620a | 2025-04-29 09:05:54 | In uvm_anonget() relock busied anon w/ the correct lock type (possibly shared). Should have been part of previous commit to unlock the upper part of the fault handler. Prevents an assertion when running the fault handler in parallel. | |
|
cb667d7c | 2025-04-29 08:16:56 | mop up more CTL_FS remnants ok mlarkin | |
 |
2da3dbd6 | 2025-04-29 03:48:10 | remove obsolete rsz keyword. ok job | |
|
3952e21b | 2025-04-29 03:45:27 | adjust column width by scanning the proc array. ok job | |
|
3f9d9c64 | 2025-04-29 02:24:32 | remove the rest of the CTL_FS posix setuid sysctl | |
|
a0a0c593 | 2025-04-29 01:48:04 | sync | |
|
642ec8ab | 2025-04-28 21:12:35 | Comment socket lock in TCP SYN cache fields. TCP SYN cache has been switched from net lock to socket lock a while ago. Adjust forgotten comments for locking in struct syn_cache. OK mvs@ | |
|
40051425 | 2025-04-28 18:56:25 | Stop advising to remove files on update The following only make sense on for pkg_delete(1), yet pkg_add(1) prints them as well, which is confusing at best and trips up way too many people: "You should also run ..." (often "rm -rf /something/important*") "You should also remove ..." No longer print those when -u is used. There may be some commands "i like it" ian kirill OK phessler kmos | |
|
fc8da380 | 2025-04-28 17:42:42 | EC_GROUP_check.3: rephrase a sentence to avoid a word repetition | |
|
487be35a | 2025-04-28 17:41:55 | EC_GROUP_new_by_curve_name.3: escape a - in code. | |
|
9ea506eb | 2025-04-28 16:18:25 | vmm(4) sets minimum ASID for AMD SEV. With AMD SEV-ES vmm(4) has to respect a "minimum ASID" when running both SEV-ES and non-SEV-ES guests. The minimum ASID value is configured in the BIOS. Non-SEV-ES guests will have to use ASIDs starting at that value while SEV-ES enabled VMs use ASIDs starting at 1. Setting the minimum ASID in the BIOS to 1, disables SEV-ES. Introduce vmm_alloc_asid() to be used by SVM base VMs. No change for VMX based VMs. from hshoexer@ | |
|
9be89971 | 2025-04-28 16:07:24 | sync | |
|
5ea32238 | 2025-04-28 13:35:39 | On resume, pms_change_state() should be run inside DVACT_WAKEUP because it could potentially sleep. ok bru, in snaps for a few days. | |
|
79854f7e | 2025-04-28 13:27:20 | alpha: Use MI soft interrupt code Tested by and OK miod@ | |
|
445fa840 | 2025-04-28 05:26:12 | sync | |
|
26a39d0b | 2025-04-28 02:02:08 | drm/amd/display: Temporarily disable hostvm on DCN31 From Aurabindo Pillai 29b2d6f53c78b54ec1e50d35d8fad24e0c66e323 in linux-6.12.y/6.12.25 ba93dddfc92084a1e28ea447ec4f8315f3d8d3fd in mainline linux | |
|
dc8cb5bc | 2025-04-28 02:00:41 | drm/amdgpu: fix warning of drm_mm_clean From ZhenGuo Yin 7f21bfd6fc16c5ed73b541a6d15b6c753b4e6b5f in linux-6.12.y/6.12.25 e7afa85a0d0eba5bf2c0a446ff622ebdbc9812d6 in mainline linux | |
|
04b071d9 | 2025-04-28 01:58:05 | drm/amd/display: Add HP Probook 445 and 465 to the quirk list for eDP on DP1 From Mario Limonciello e97bf44115e887a91f59017279ae86fb5a49d936 in linux-6.12.y/6.12.25 139e99d58e373bd11f085766e681d21d34d0b097 in mainline linux | |
|
716cd312 | 2025-04-28 01:55:59 | drm/amd/display: Protect FPU in dml2_init()/dml21_init() From Huacai Chen a5c9107a3e01375292ec20b2dc270bd7e6d0201e in linux-6.12.y/6.12.25 afcdf51d97cd58dd7a2e0aa8acbaea5108fa6826 in mainline linux | |
|
6d6049cc | 2025-04-28 01:54:31 | drm/amd/display: Do not enable Replay and PSR while VRR is on in amdgpu_dm_commit_planes() From Tom Chung 9cb744fbee3884cbcc2f80c92c9f7d6d13c37a24 in linux-6.12.y/6.12.25 69a46ce1f15b4391c128d581f6936750f9bfa052 in mainline linux | |
|
d6b18b39 | 2025-04-28 01:52:39 | drm/amdgpu: immediately use GTT for new allocations From Christian Koenig a53d959fe660341788cb8dbc3ac3330d90a09ecf in linux-6.12.y/6.12.25 a755906fb2b8370c43e91ba437ae1b3e228e8b02 in mainline linux | |
|
379f162b | 2025-04-28 01:50:57 | drm/i915/gvt: fix unterminated-string-initialization warning From Jani Nikula 4b171d4cbfffca02df349ed8405e93ff3b01e36a in linux-6.12.y/6.12.25 2e43ae7dd71cd9bb0d1bce1d3306bf77523feb81 in mainline linux | |
|
e1c0f0cc | 2025-04-28 01:49:40 | drm/amdgpu/dma_buf: fix page_link check From Matthew Auld 91b646a0b2cbd1d6d1b0be49ae780b6d2ea6011c in linux-6.12.y/6.12.25 c0dd8a9253fadfb8e5357217d085f1989da4ef0a in mainline linux | |
|
aa95b3e9 | 2025-04-28 01:48:32 | drm/amdgpu/mes11: optimize MES pipe FW version fetching From Alex Deucher 228e98e2021cef1b4f5f0d8614b4371e05d9098d in linux-6.12.y/6.12.25 b71a2bb0ce07f40f92f59ed7f283068e41b10075 in mainline linux | |
|
bcf3c865 | 2025-04-28 01:46:29 | drm/amd/display: Protect FPU in dml21_copy() From Huacai Chen 596284026c5bc4d002c812a699ec961c1d7dd472 in linux-6.12.y/6.12.25 4408b59eeacfea777aae397177f49748cadde5ce in mainline linux | |
|
502d4a67 | 2025-04-28 01:44:13 | drm/amd/display: Protect FPU in dml2_validate()/dml21_validate() From Huacai Chen 74d6fba60f05ca6b298702233b6e6cc7629eeb5a in linux-6.12.y/6.12.25 366e77cd4923c3aa45341e15dcaf3377af9b042f in mainline linux | |
|
9cd84a2b | 2025-04-28 01:41:39 | drm/amd/display: Add HP Elitebook 645 to the quirk list for eDP on DP1 From Mario Limonciello fe19e04cd96f625b0ab3aff598f13fceb5eec0d5 in linux-6.12.y/6.12.25 1c5fdef30ed120613e769a3bd2a144cfd4c688d6 in mainline linux | |
|
43f70988 | 2025-04-28 01:40:01 | drm/i915/vrr: Add vrr.vsync_{start, end} in vrr_params_changed From Ankit Nautiyal a37e01fe60a35df354aa4c30762b91f26092ee93 in linux-6.12.y/6.12.25 a421f5033c82990d795f8fcd30d5b835f8975508 in mainline linux | |
|
c89fa4ac | 2025-04-28 01:38:14 | drm/amdgpu/mes12: optimize MES pipe FW version fetching From Alex Deucher 2b00b32e6137bd5ed600c387cfb16274f93b91dc in linux-6.12.y/6.12.25 34779e14461cf715238dec5fd43a1e11977ec115 in mainline linux | |
|
85baafc9 | 2025-04-28 01:36:46 | drm/amd/pm/powerplay/hwmgr/vega20_thermal: Prevent division by zero From Denis Arefev 42f7b5d12c28b2a601a98d10a80c6db1fe1a2900 in linux-6.12.y/6.12.25 4e3d9508c056d7e0a56b58d5c81253e2a0d22b6c in mainline linux | |
|
c9658f66 | 2025-04-28 01:35:32 | drm/amd/pm/swsmu/smu13/smu_v13_0: Prevent division by zero From Denis Arefev fb803d4bb9ea0a61c21c4987505e4d4ae18f9fdc in linux-6.12.y/6.12.25 f23e9116ebb71b63fe9cec0dcac792aa9af30b0c in mainline linux | |
|
737f7404 | 2025-04-28 01:33:44 | drm/amd/pm/powerplay/hwmgr/smu7_thermal: Prevent division by zero From Denis Arefev 8e9c4f8d197d5709c75effa5d58e80b4fa01981a in linux-6.12.y/6.12.25 7c246a05df51c52fe0852ce56ba10c41e6ed1f39 in mainline linux | |
|
26da8915 | 2025-04-28 01:32:16 | drm/amd/pm/smu11: Prevent division by zero From Denis Arefev 63a150400194592206817124268ff6f43947e8c9 in linux-6.12.y/6.12.25 7ba88b5cccc1a99c1afb96e31e7eedac9907704c in mainline linux | |
|
8006f89a | 2025-04-28 01:30:55 | drm/amd/pm/powerplay: Prevent division by zero From Denis Arefev bd4d90adbca1862d03e581e10e74ab73ec75e61b in linux-6.12.y/6.12.25 4b8c3c0d17c07f301011e2908fecd2ebdcfe3d1c in mainline linux | |
|
dafe47ac | 2025-04-28 01:29:24 | drm/amd/pm: Prevent division by zero From Denis Arefev 6413fed016208171592c88b5df002af8a1387e24 in linux-6.12.y/6.12.25 7d641c2b83275d3b0424127b2e0d2d0f7dd82aef in mainline linux | |
|
6385b815 | 2025-04-28 01:27:36 | drm/amd/display: Increase vblank offdelay for PSR panels From Leo Li 2a2b7b6f90a2e378959445097f5aa7d25a1edf37 in linux-6.12.y/6.12.25 f21e6d149b49c92f9e68aa0c76033e1e13d9f5da in mainline linux |