Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

28 participants
7088 discussions

Cybersecurity Experts Helping You Stay One Step Ahead Lee Ultimate Hacker

by ludolftom64＠gmail.com

Leeultimatehacker @ a o l . c o m) whatspp +1 ( 7 1 5 ) 3 1 4 - 9 2 4 8 Lee Ultimate Hacker is a professional cybersecurity platform specializing in advanced digital protection, ethical hacking services, cyber risk assessment, and online security solutions for businesses, entrepreneurs, and individuals seeking stronger protection against modern cyber threats. As cybercrime continues to rise globally, securing websites, networks, databases, and online accounts has become a critical priority. Lee Ultimate Hacker delivers reliable cybersecurity services designed to help clients strengthen their digital infrastructure, prevent unauthorized access, and protect valuable information from hackers, malware, phishing attacks, ransomware, and data breaches. With a strong reputation for professionalism and technical expertise, Lee Ultimate Hacker provides customized cybersecurity solutions tailored to the needs of each client. The platform focuses on ethical hacking practices, vulnerability testing, penetration testing, and cybersecurity consulting to identify weaknesses before cybercriminals can exploit them. By using modern security techniques and industry-standard methodologies, clients receive effective protection strategies that improve online safety and long-term digital resilience. Businesses today depend heavily on digital technology for communication, e-commerce, financial transactions, and customer engagement. Without proper cybersecurity protection, organizations face serious risks that can lead to financial losses, damaged reputations, and operational disruptions. Lee Ultimate Hacker helps businesses reduce these risks through proactive cybersecurity measures, security monitoring, and strategic defense planning. From website security optimization to network protection and cyber threat analysis, every solution is designed to maintain secure and stable digital operations. Lee Ultimate Hacker also supports individuals who want stronger personal cybersecurity and privacy protection. Cybercriminals often target personal accounts, online wallets, and private information through scams, phishing emails, and malicious software. Through cybersecurity consultation and digital protection guidance, clients can improve password security, strengthen account protection, and reduce exposure to online threats. The platform promotes cybersecurity awareness and encourages safer online practices to help users protect their digital identity and sensitive information. What sets Lee Ultimate Hacker apart is a commitment to confidentiality, ethical standards, and customer satisfaction. Every project is handled with professionalism, discretion, and attention to detail to ensure clients receive trustworthy cybersecurity support. The platform continuously stays updated with the latest cybersecurity trends, hacking techniques, and threat intelligence to provide modern and effective security solutions in a constantly evolving digital landscape. Search engines value websites that provide authoritative, relevant, and high-quality cybersecurity content. Lee Ultimate Hacker is focused on delivering informative and reliable cybersecurity services that align with modern digital protection standards. By combining technical expertise with practical security solutions, the platform continues to build credibility as a dependable source for ethical hacking, cyber defense, and online security consulting. Whether you are looking for website security services, vulnerability assessment, penetration testing, ethical hacking consultation, network security support, or advanced digital protection, Lee Ultimate Hacker provides professional cybersecurity solutions designed to protect your online presence and secure your digital assets. The goal is to help businesses and individuals operate with greater confidence, knowing their systems and information are protected by modern cybersecurity strategies.

3 months

UncertainRouteCanvas

by wernerkatherine77＠proton.me

Thermal Logic: Why Gambling Ended Up at the Heart of the German Resort Economy Thermal resorts in the 18th and 19th centuries http://auslaendische-online-casinos.de/ needed a way to keep wealthy visitors entertained past dinner. Concerts helped. Theater helped more. But nothing extended the stay — and the spending — quite like a well-appointed room where money could change hands in a socially acceptable setting. Baden-Baden understood this before most. The Kurhaus became a model not because it was unique but because it made the interdependence visible. A guest who came for the waters stayed for the tables, spent on the hotel, bought things in the shops, and left having funded an entire local economy for several days. The logic was circular and deliberately so. Civic planners in spa towns across what would become Germany replicated it, which is why the origins of casinos in Germany are not found in any single invention but in a distributed experiment conducted across dozens of small resort towns competing for the same aristocratic clientele throughout the 1800s. Bad Homburg refined the roulette wheel. Wiesbaden attracted the Russian literary crowd. Aachen positioned itself for the Belgian and French market. Each town adapted the model to its geography and its visitors, and the result was a casino culture embedded in regional identity rather than sitting apart from it. Prussia's 1868 ban interrupted that trajectory sharply. The decades that followed pushed gambling into legal ambiguity across German territories, and the post-war reconstruction of the industry happened unevenly — shaped more by which states had surviving spa infrastructure than by any coherent national policy. That patchwork is still visible today in the distribution of licensed land-based establishments, clustered around the same historic resort towns that invented the format in the first place. The digital era forced a reckoning with this geography. Online platforms do not have a location in any meaningful sense, which made the old state-by-state regulatory model collapse under its own inconsistencies. The 2021 Glücksspielstaatsvertrag addressed this by creating a unified federal framework and, critically, establishing the conditions under which providers could obtain a casino Germany EU license — a mechanism bringing domestic law into functional alignment with the internal market principles Brussels had been pressing for years. The treaty imposed strict behavioral constraints: mandatory deposit limits, real-time transaction monitoring, advertising watersheds, and a hard prohibition on certain product categories that had flourished in the unregulated online space. For operators already holding licenses in Malta or Gibraltar, the German market became accessible in theory and expensive in practice. Compliance infrastructure, local tax obligations, and the administrative requirements of the new framework made entry calculations difficult for anyone below a certain scale. Consolidation followed, as it tends to. The broader European picture remains deliberately fragmented. France runs its online market through a state-backed monopoly logic. The Netherlands introduced licensing in 2021 under its own Remote Gambling Act, with a different set of consumer protection priorities. Sweden liberalized in 2019 and has spent the years since managing the gap between projected and actual outcomes in problem gambling rates. Germany sits somewhere in this spectrum — more open than its pre-2021 self, more restrictive than the offshore destinations its residents had been using freely for years before the law caught up.

3 months

Re: DEPT (the dependency tracker) as AI review prompt?

by Yunseong Kim

Hi Harry, On 5/23/26 16:34, Harry Yoo wrote: > > > On 5/23/26 11:00 PM, Yunseong Kim wrote: >> I've previously experimented with running DEPT alongside syzkaller fuzzing, >> and many hung tasks missed by lockdep are caught by DEPT, but the resulting >> high volume of reports makes it easy for issues to get lost in the massive >> log output. Sorting through that output manually is a huge bottleneck, so >> leveraging a well-crafted AI prompt to triage the warnings and filter out >> the false positives would be incredibly valuable. > > I mean both 1) detection of deadlock issues AND 2) false positive elimination with AI. I completely agree. Implanting DEPT's model into an AI review prompt is a great idea. As you suggested, the patterns we develop for the AI could provide valuable feedback to enhance DEPT's itself. > If the review prompt is only used to eliminate DEPT's false positives, I think that would be quite hard to get broad use. > > Someone would have to build out-of-tree DEPT, collect the reports, and then feed those back into the AI. I don't think building that kind of pipeline would actually work well in practice. I also have a huge dept report of DEPT reports, and manually reviewing all of them is makes me sigh. The constant kernel rebuilds required for lockup testing every time are also quite expensive. Thanks for the summary! Best Regards, Yunseong

3 months

How to Hire a Hacker to remove unwanted information & files from all search engines linked on the internet

by lenarichmond49＠gmail.com

Have you been a victim of scams, fake investments, romance fraud, or online job scams? Losing your hard-earned money can be devastating, but you don't have to accept defeat! Recovery is 95% possible. Hire Digital Light Solutions messages E m ai l: digital,light,solution@ quality,service.c om & Telegram —digitallightsolution

3 months

How to Hire a Hacker to remove unwanted information & files from all search engines linked on the internet

by lenarichmond49＠gmail.com

3 months

How to Hire a Hacker to remove unwanted information & files from all search engines linked on the internet

by lenarichmond49＠gmail.com

3 months

How to Hire a Hacker to remove unwanted information & files from all search engines linked on the internet

by lenarichmond49＠gmail.com

3 months

[PATCH v5 0/2] dma-buf: heaps: system: add an option to allocate explicitly shared/decrypted memory

by Jiri Pirko

From: Jiri Pirko <jiri(a)nvidia.com> Confidential computing (CoCo) VMs/guests, such as AMD SEV and Intel TDX, run with private/encrypted memory which creates a challenge for devices that do not support DMA to it (no TDISP support). For kernel-only DMA operations, swiotlb bounce buffering provides a transparent solution by copying data through shared memory. However, the only way to get this memory into userspace is via the DMA API's dma_alloc_pages()/dma_mmap_pages() type interfaces which limits the use of the memory to a single DMA device, and is incompatible with pin_user_pages(). These limitations are particularly problematic for the RDMA subsystem which makes heavy use of pin_user_pages() and expects flexible memory usage between many different DMA devices. This patch series enables userspace to explicitly request shared (decrypted) memory allocations from new dma-buf system_cc_shared heap. Userspace can mmap this memory and pass the dma-buf fd to other existing importers such as RDMA or DRM devices to access the memory. The DMA API is improved to allow the dma heap exporter to DMA map the shared memory to each importing device. Based on dma-mapping-for-next e7442a68cd1ee797b585f045d348781e9c0dde0d Jiri Pirko (2): dma-mapping: introduce DMA_ATTR_CC_SHARED for shared memory dma-buf: heaps: system: add system_cc_shared heap for explicitly shared memory drivers/dma-buf/heaps/system_heap.c | 103 ++++++++++++++++++++++++++-- include/linux/dma-mapping.h | 10 +++ include/trace/events/dma.h | 3 +- kernel/dma/direct.h | 14 +++- kernel/dma/mapping.c | 13 +++- 5 files changed, 132 insertions(+), 11 deletions(-) -- 2.51.1

3 months

[PATCH v4] drm/virtio: use uninterruptible resv lock for plane updates

by Deepanshu Kartikey

virtio_gpu_cursor_plane_update() and virtio_gpu_resource_flush() lock the framebuffer BO's dma_resv via virtio_gpu_array_lock_resv() and ignore its return value. The function can fail with -EINTR from dma_resv_lock_interruptible() (signal during lock wait) or with -ENOMEM from dma_resv_reserve_fences() (fence slot allocation), leaving the resv lock not held. The queue path then walks the object array and calls dma_resv_add_fence(), which requires the lock held; with lockdep enabled this trips dma_resv_assert_held(): WARNING: drivers/dma-buf/dma-resv.c:296 at dma_resv_add_fence+0x71e/0x840 Call Trace: virtio_gpu_array_add_fence virtio_gpu_queue_ctrl_sgs virtio_gpu_queue_fenced_ctrl_buffer virtio_gpu_cursor_plane_update drm_atomic_helper_commit_planes drm_atomic_helper_commit_tail commit_tail drm_atomic_helper_commit drm_atomic_commit drm_atomic_helper_update_plane __setplane_atomic drm_mode_cursor_universal drm_mode_cursor_common drm_mode_cursor_ioctl drm_ioctl __x64_sys_ioctl Beyond the WARN, mutating the dma_resv fence list without the lock races with concurrent readers/writers and can corrupt the list. Both call sites run inside the .atomic_update plane callback, which DRM atomic helpers do not allow to fail (by the time it runs, the commit has been signed off to userspace and there is no clean rollback path). Moving the lock acquisition to .prepare_fb was rejected because the broader lock scope deadlocks against other BO locking paths in the same atomic commit. Introduce virtio_gpu_lock_one_resv_uninterruptible() that uses dma_resv_lock() instead of dma_resv_lock_interruptible(). This eliminates the -EINTR failure mode -- the realistic syzbot trigger -- without extending the lock hold across the commit. The helper locks a single BO and rejects nents > 1 with -EINVAL; both fix sites lock exactly one BO. Use it from virtio_gpu_cursor_plane_update() and virtio_gpu_resource_flush(); check the return value to handle the remaining -ENOMEM case from dma_resv_reserve_fences() by freeing the objs and skipping the plane update for that frame. The framebuffer BOs touched here are not shared with other contexts and lock contention is expected to be brief, so the loss of signal-interruptibility is acceptable. Other callers of virtio_gpu_array_lock_resv() (the ioctl paths) continue to use the interruptible variant. The bug was reported by syzbot, triggered via fault injection (fail_nth) on the DRM_IOCTL_MODE_CURSOR path, which forces the -ENOMEM branch in dma_resv_reserve_fences(). Reported-by: syzbot+72bd3dd3a5d5f39a0271(a)syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=72bd3dd3a5d5f39a0271 Fixes: 5cfd31c5b3a3 ("drm/virtio: fix virtio_gpu_cursor_plane_update().") Cc: stable(a)vger.kernel.org Signed-off-by: Deepanshu Kartikey <kartikey406(a)gmail.com> --- v4: Rename the helper to virtio_gpu_lock_one_resv_uninterruptible() and reject objs->nents > 1 with -EINVAL. The v3 helper's multi-object branch used drm_gem_lock_reservations(), which is interruptible, contradicting the "uninterruptible" name; both fix sites lock a single BO so the multi-object path is dropped. (Dmitry Osipenko) v3: Drop the prepare_fb/cleanup_fb approach from v2 (it deadlocked against virtio_gpu_resource_flush(), which also locks the BO in the same atomic commit). Instead add an uninterruptible variant of the resv lock helper and use it in both virtio_gpu_cursor_plane_update() and virtio_gpu_resource_flush(). (Dmitry Osipenko) v2: Move resv lock acquisition from .atomic_update (which must not fail) to .prepare_fb (which may), per maintainer review of v1. The v1 approach of silently skipping the cursor update on lock failure violated the atomic-commit contract with userspace. --- drivers/gpu/drm/virtio/virtgpu_drv.h | 1 + drivers/gpu/drm/virtio/virtgpu_gem.c | 17 +++++++++++++++++ drivers/gpu/drm/virtio/virtgpu_plane.c | 10 ++++++++-- 3 files changed, 26 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/virtgpu_drv.h index f17660a71a3e..2f3531950aa4 100644 --- a/drivers/gpu/drm/virtio/virtgpu_drv.h +++ b/drivers/gpu/drm/virtio/virtgpu_drv.h @@ -317,6 +317,7 @@ virtio_gpu_array_from_handles(struct drm_file *drm_file, u32 *handles, u32 nents void virtio_gpu_array_add_obj(struct virtio_gpu_object_array *objs, struct drm_gem_object *obj); int virtio_gpu_array_lock_resv(struct virtio_gpu_object_array *objs); +int virtio_gpu_lock_one_resv_uninterruptible(struct virtio_gpu_object_array *objs); void virtio_gpu_array_unlock_resv(struct virtio_gpu_object_array *objs); void virtio_gpu_array_add_fence(struct virtio_gpu_object_array *objs, struct dma_fence *fence); diff --git a/drivers/gpu/drm/virtio/virtgpu_gem.c b/drivers/gpu/drm/virtio/virtgpu_gem.c index f22dc5c21cd4..435d37d36034 100644 --- a/drivers/gpu/drm/virtio/virtgpu_gem.c +++ b/drivers/gpu/drm/virtio/virtgpu_gem.c @@ -238,6 +238,23 @@ int virtio_gpu_array_lock_resv(struct virtio_gpu_object_array *objs) return ret; } +int virtio_gpu_lock_one_resv_uninterruptible(struct virtio_gpu_object_array *objs) +{ + int ret; + + if (objs->nents != 1) + return -EINVAL; + + dma_resv_lock(objs->objs[0]->resv, NULL); + + ret = dma_resv_reserve_fences(objs->objs[0]->resv, 1); + if (ret) { + virtio_gpu_array_unlock_resv(objs); + return ret; + } + return 0; +} + void virtio_gpu_array_unlock_resv(struct virtio_gpu_object_array *objs) { if (objs->nents == 1) { diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c index a126d1b25f46..652352424744 100644 --- a/drivers/gpu/drm/virtio/virtgpu_plane.c +++ b/drivers/gpu/drm/virtio/virtgpu_plane.c @@ -215,7 +215,10 @@ static void virtio_gpu_resource_flush(struct drm_plane *plane, if (!objs) return; virtio_gpu_array_add_obj(objs, vgfb->base.obj[0]); - virtio_gpu_array_lock_resv(objs); + if (virtio_gpu_lock_one_resv_uninterruptible(objs)) { + virtio_gpu_array_put_free(objs); + return; + } virtio_gpu_cmd_resource_flush(vgdev, bo->hw_res_handle, x, y, width, height, objs, vgplane_st->fence); @@ -459,7 +462,10 @@ static void virtio_gpu_cursor_plane_update(struct drm_plane *plane, if (!objs) return; virtio_gpu_array_add_obj(objs, vgfb->base.obj[0]); - virtio_gpu_array_lock_resv(objs); + if (virtio_gpu_lock_one_resv_uninterruptible(objs)) { + virtio_gpu_array_put_free(objs); + return; + } virtio_gpu_cmd_transfer_to_host_2d (vgdev, 0, plane->state->crtc_w, -- 2.43.0

3 months

[PATCH V1] Revert "accel/amdxdna: Support read-only user-pointer BO mappings"

by Lizhi Hou

This reverts commit f649e63d4a6423eda8eb208638849fd6396aedd7. The read-only feature requires further consideration. Signed-off-by: Lizhi Hou <lizhi.hou(a)amd.com> --- drivers/accel/amdxdna/amdxdna_ubuf.c | 29 ++-------------------------- 1 file changed, 2 insertions(+), 27 deletions(-) diff --git a/drivers/accel/amdxdna/amdxdna_ubuf.c b/drivers/accel/amdxdna/amdxdna_ubuf.c index 3769210c55cc..4c0647057759 100644 --- a/drivers/accel/amdxdna/amdxdna_ubuf.c +++ b/drivers/accel/amdxdna/amdxdna_ubuf.c @@ -125,26 +125,6 @@ static const struct dma_buf_ops amdxdna_ubuf_dmabuf_ops = { .vunmap = amdxdna_ubuf_vunmap, }; -static int readonly_va_entry(struct amdxdna_drm_va_entry *va_ent) -{ - struct mm_struct *mm = current->mm; - struct vm_area_struct *vma; - int ret; - - mmap_read_lock(mm); - - vma = find_vma(mm, va_ent->vaddr); - if (!vma || - vma->vm_start > va_ent->vaddr || - vma->vm_end - va_ent->vaddr < va_ent->len) - ret = -ENOENT; - else - ret = vma->vm_flags & VM_WRITE ? 0 : 1; - - mmap_read_unlock(mm); - return ret; -} - struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev, u32 num_entries, void __user *va_entries) { @@ -154,7 +134,6 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev, struct amdxdna_ubuf_priv *ubuf; u32 npages, start = 0; struct dma_buf *dbuf; - bool readonly = true; int i, ret; DEFINE_DMA_BUF_EXPORT_INFO(exp_info); @@ -193,10 +172,6 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev, ret = -EINVAL; goto free_ent; } - - /* Pin pages as writable as long as not all entries are read-only. */ - if (readonly && readonly_va_entry(&va_ent[i]) != 1) - readonly = false; } ubuf->nr_pages = exp_info.size >> PAGE_SHIFT; @@ -219,7 +194,7 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev, npages = va_ent[i].len >> PAGE_SHIFT; ret = pin_user_pages_fast(va_ent[i].vaddr, npages, - (readonly ? 0 : FOLL_WRITE) | FOLL_LONGTERM, + FOLL_WRITE | FOLL_LONGTERM, &ubuf->pages[start]); if (ret >= 0) { start += ret; @@ -236,7 +211,7 @@ struct dma_buf *amdxdna_get_ubuf(struct drm_device *dev, exp_info.ops = &amdxdna_ubuf_dmabuf_ops; exp_info.priv = ubuf; - exp_info.flags = (readonly ? O_RDONLY : O_RDWR) | O_CLOEXEC; + exp_info.flags = O_RDWR | O_CLOEXEC; dbuf = dma_buf_export(&exp_info); if (IS_ERR(dbuf)) { -- 2.34.1

3 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig