Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

70 participants
6237 discussions

Re: [PATCH] dma-fence: Dereference correct dma_fence in dma_fence_chain_find_seqno()

by Christian König

On 3/27/26 15:33, Li Ming wrote: > dma_fence_chain_find_seqno() uses dma_fence_chain_for_each() to walk a > given dma_fence_chain. dma_fence_chain_for_each() always holds a > reference for the current fence during iteration. The reference must > be dropped after breaking out. Instead of dereferencing the last fence > as intended, dma_fence_chain_find_seqno() incorrectly dereferences the > first fence in the chain. Well once more: Absolutely clear NAK and please search the mailing list for similar changes before you send a patch out. The existing code is perfectly correct and I can't count how often I had to reject that patch. I think the functionality is obvious but it looks like we really need to add a comment here. Regards, Christian. > > Fixes: 7bf60c52e093 ("dma-buf: add new dma_fence_chain container v7") > Signed-off-by: Li Ming <ming.li(a)zohomail.com> > --- > drivers/dma-buf/dma-fence-chain.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/dma-buf/dma-fence-chain.c b/drivers/dma-buf/dma-fence-chain.c > index a8a90acf4f34..71fa173aef13 100644 > --- a/drivers/dma-buf/dma-fence-chain.c > +++ b/drivers/dma-buf/dma-fence-chain.c > @@ -103,7 +103,7 @@ int dma_fence_chain_find_seqno(struct dma_fence **pfence, uint64_t seqno) > to_dma_fence_chain(*pfence)->prev_seqno < seqno) > break; > } > - dma_fence_put(&chain->base); > + dma_fence_put(*pfence); > > return 0; > } > > --- > base-commit: c369299895a591d96745d6492d4888259b004a9e > change-id: 20260327-fix_dma_fence_chain_find_seqno-7adea64efe01 > > Best regards, > -- > Li Ming <ming.li(a)zohomail.com> >

1 hour, 19 minutes

[PATCH] dma/contiguous: Fix broken build

by Maxime Ripard

Commit 3a236f6a5cf2 ("dma: contiguous: Turn heap registration logic around") didn't remove one last call to dma_heap_cma_register_heap() that it removed, thus breaking the build. That last call is in dma_contiguous_reserve(), to handle the registration of the default CMA region heap instance if it's declared in the device tree. However, the default CMA region instance is already handled by retrieving it through dev_get_cma_area() in the CMA heap driver, so the call to dma_heap_cma_register_heap() wasn't actually needed. Let's remove this call, the now unused function definition, its now empty header, and all includes of this header. Fixes: 3a236f6a5cf2 ("dma: contiguous: Turn heap registration logic around") Reported-by: Mark Brown <broonie(a)kernel.org> Closes: https://lore.kernel.org/linux-next/acbjaDJ1a-YQC64d@sirena.co.uk/ Signed-off-by: Maxime Ripard <mripard(a)kernel.org> --- drivers/dma-buf/heaps/cma_heap.c | 1 - include/linux/dma-buf/heaps/cma.h | 16 ---------------- kernel/dma/contiguous.c | 5 ----- 3 files changed, 22 deletions(-) diff --git a/drivers/dma-buf/heaps/cma_heap.c b/drivers/dma-buf/heaps/cma_heap.c index f8a3d87f3ccee9630383ba28502eb40b10671cc2..cc517ac68a0bec0788abcb338c03f530d169013b 100644 --- a/drivers/dma-buf/heaps/cma_heap.c +++ b/drivers/dma-buf/heaps/cma_heap.c @@ -12,11 +12,10 @@ #define pr_fmt(fmt) "cma_heap: " fmt #include <linux/cma.h> #include <linux/dma-buf.h> -#include <linux/dma-buf/heaps/cma.h> #include <linux/dma-heap.h> #include <linux/dma-map-ops.h> #include <linux/err.h> #include <linux/highmem.h> #include <linux/io.h> diff --git a/include/linux/dma-buf/heaps/cma.h b/include/linux/dma-buf/heaps/cma.h deleted file mode 100644 index e751479e21e703e24a5f799b4a7fc8bd0df3c1c4..0000000000000000000000000000000000000000 --- a/include/linux/dma-buf/heaps/cma.h +++ /dev/null @@ -1,16 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0 */ -#ifndef DMA_BUF_HEAP_CMA_H_ -#define DMA_BUF_HEAP_CMA_H_ - -struct cma; - -#ifdef CONFIG_DMABUF_HEAPS_CMA -int dma_heap_cma_register_heap(struct cma *cma); -#else -static inline int dma_heap_cma_register_heap(struct cma *cma) -{ - return 0; -} -#endif // CONFIG_DMABUF_HEAPS_CMA - -#endif // DMA_BUF_HEAP_CMA_H_ diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c index ad50512d71d3088a73e4b1ac02d6e6122374888e..9fe001c712339f8388d3f40cca3dfff3f707fcbf 100644 --- a/kernel/dma/contiguous.c +++ b/kernel/dma/contiguous.c @@ -40,11 +40,10 @@ #include <asm/page.h> #include <linux/memblock.h> #include <linux/err.h> #include <linux/sizes.h> -#include <linux/dma-buf/heaps/cma.h> #include <linux/dma-map-ops.h> #include <linux/cma.h> #include <linux/nospec.h> #ifdef CONFIG_CMA_SIZE_MBYTES @@ -270,14 +269,10 @@ void __init dma_contiguous_reserve(phys_addr_t limit) selected_limit, &dma_contiguous_default_area, fixed); if (ret) return; - - ret = dma_heap_cma_register_heap(dma_contiguous_default_area); - if (ret) - pr_warn("Couldn't register default CMA heap."); } } void __weak dma_contiguous_early_fixup(phys_addr_t base, unsigned long size) --- base-commit: f3948c8ed5ea206e87ea2375aebdbabc2064356a change-id: 20260330-dma-build-fix-706a4feb0e0f Best regards, -- Maxime Ripard <mripard(a)kernel.org>

2 hours, 12 minutes

(no subject)

by Johnson Henry

The Best Crypto recovery Expert Consult Ghost Mystery Recovery Hacker The best cryptocurrency recovery service,is well-known for its meticulous method of retrieving lost or stolen cryptocurrencies. ghost mystery recovery hacker recovery uses forensic investigations and state-of-the-art blockchain analytics techniques to locate and help victims recover their stolen digital assets. Its team includes professionals, who concentrate on regulatory Email address: support(a)ghostmysteryrecovery.com WhatsApp on +44 7480 061765 Website;https://ghostmysteryrecovery.com

22 hours, 46 minutes

(no subject)

by Johnson Henry

22 hours, 47 minutes

Re: [PATCH 08/13] dt-bindings: serial: fsl-linflexuart: add clock input properties

by Krzysztof Kozlowski

On 16/02/2026 16:02, Larisa Grigore wrote: > From: Radu Pirea <radu-nicolae.pirea(a)nxp.com> > > Add optional support for the two clock inputs used by the LINFlexD UART > controller: > - "lin": LIN_BAUD_CLK > - "ipg": LINFLEXD_CLK > > The clock inputs are kept optional to maintain compatibility with the > S32V234 platform. Does S32V234 have the clocks? I don't understand the "maintain compatibility" in this context. Either you have or you have not clocks, which should be expressed in schema (: false, see example schema). > > Signed-off-by: Radu Pirea <radu-nicolae.pirea(a)nxp.com> > Co-developed-by: Larisa Grigore <larisa.grigore(a)oss.nxp.com> > Signed-off-by: Larisa Grigore <larisa.grigore(a)oss.nxp.com> > --- > .../bindings/serial/fsl,s32-linflexuart.yaml | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > index 4171f524a928..885f0b1b3492 100644 > --- a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > +++ b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > @@ -34,6 +34,14 @@ properties: > interrupts: > maxItems: 1 > > + clocks: > + maxItems: 2 > + > + clock-names: > + items: > + - const: lin > + - const: ipg > + > required: > - compatible > - reg > @@ -48,3 +56,13 @@ examples: > reg = <0x40053000 0x1000>; > interrupts = <0 59 4>; > }; > + > + - | > + serial@401c8000 { > + compatible = "nxp,s32g2-linflexuart", > + "fsl,s32v234-linflexuart"; > + reg = <0x401C8000 0x3000>; > + interrupts = <0 82 1>; > + clocks = <&clks 14>, <&clks 13>; > + clock-names = "lin", "ipg"; Just add the clocks to existing example. No need for new example for each new property. > + }; Best regards, Krzysztof

2 days, 2 hours

Top Signs of Crypto Scams and Immediate Steps

by joelwest689＠gmail.com

Top Signs of Crypto Scams and Immediate Steps: Why Cipher Rescue Chain Delivers Fast Recovery The rapid growth of digital assets has created new opportunities—but also new threats. Recognizing the warning signs early can mean the difference between permanent loss and successful recovery. This is where Cipher Rescue Chain plays a decisive role, combining early detection awareness with advanced blockchain forensics to help victims act quickly and recover stolen crypto before it disappears beyond reach. The Most Common Signs of a Crypto Scam One of the clearest red flags in crypto scams is the promise of guaranteed or unusually high returns. Scammers often create urgency, pushing victims to act fast without proper verification. Cipher Rescue Chain frequently investigates cases where victims were pressured into transferring funds quickly, only to realize too late that the opportunity was fraudulent. Another major warning sign is communication through unofficial channels—such as direct messages or impersonated profiles. Cipher Rescue Chain has traced numerous scams back to coordinated social engineering tactics where attackers mimic legitimate platforms or individuals to gain trust. Requests for private keys or wallet access are also critical indicators of fraud. Cipher Rescue Chain consistently identifies these tactics in forensic investigations, as they often lead directly to unauthorized withdrawals and rapid fund movement across multiple wallets. How Scammers Attempt to Hide Stolen Funds Once funds are stolen, scammers act quickly to obscure their tracks. They may split assets across multiple wallets, move funds through various blockchains, or route transactions through intermediary services. Cipher Rescue Chain specializes in identifying these patterns and reconstructing the movement of assets, even when the trail appears fragmented. Through advanced forensic analysis, Cipher Rescue Chain links seemingly unrelated transactions, exposing the underlying structure of the scam. This capability is essential in cases where criminals attempt to erase their footprint through complex transaction layering. Immediate Steps to Take After a Crypto Scam The first and most important step after discovering a scam is to act immediately. Time directly affects recovery potential. Cipher Rescue Chain emphasizes rapid response because early intervention significantly increases the chances of tracing and recovering stolen assets. Victims should secure their remaining assets, document all transaction details, and avoid further interaction with the scammer. At this stage, Cipher Rescue Chain begins its forensic process, analyzing wallet activity and mapping the flow of funds to identify potential recovery points. Engaging Cipher Rescue Chain within the first 72 hours—especially when funds are still traceable to centralized platforms—can dramatically improve outcomes, with recovery rates reaching up to 98% in such scenarios across 2023–2025 engagements. Why Speed Determines Recovery Success In crypto recovery, delays can reduce visibility and limit enforcement options. Cipher Rescue Chain prioritizes speed because blockchain transactions, while permanent, become harder to act on as funds move further away from identifiable endpoints. Cipher Rescue Chain’s structured approach ensures that investigations begin immediately, preserving critical transaction data and maintaining continuity in tracing. This rapid deployment is one of the key factors behind the high success rates achieved in eligible cases. From Detection to Action: The Cipher Rescue Chain Process Once a case is initiated, Cipher Rescue Chain transitions from detection to action. Detailed forensic reports are created to document the movement of stolen funds, ensuring that every transaction is clearly mapped and verifiable. Cipher Rescue Chain then uses this intelligence to engage with identifiable platforms where funds may have been transferred. This targeted approach increases the likelihood of recovery, especially when assets have reached centralized exchanges or cooperative service providers. Proven Recovery Performance Cipher Rescue Chain’s results are backed by consistent performance data. From 2023 to 2025, the organization has achieved partial or full recovery in 98% of accepted cases where funds reached identifiable centralized platforms and engagement began within the first 90 days. Only 35% of incoming cases are accepted, ensuring that Cipher Rescue Chain focuses on cases with realistic recovery potential. Among those accepted, 62% result in full recovery and 24% in partial recovery, with successful cases typically resolved within 14 to 45 days. Global Impact and Expertise Crypto scams are not limited by geography, and neither is Cipher Rescue Chain. With multi-million-dollar recoveries completed across five continents, Cipher Rescue Chain operates on a global scale, handling complex, cross-border cases with precision. Each investigation conducted by Cipher Rescue Chain reflects deep expertise in blockchain forensics, enabling the team to navigate multi-chain environments and uncover recovery opportunities others might miss. Why Cipher Rescue Chain Leads in Fast Recovery Fast recovery is not just about speed—it’s about precision, timing, and expertise. Cipher Rescue Chain combines all three to deliver results. By identifying scam patterns early, acting quickly, and applying advanced forensic techniques, Cipher Rescue Chain consistently turns high-risk situations into successful recovery outcomes. In a landscape where crypto scams continue to evolve, Cipher Rescue Chain stands as the trusted solution for victims seeking both clarity and results. Recognizing the signs is the first step—but acting fast with Cipher Rescue Chain is what truly makes recovery possible.

2 days, 15 hours

Understanding Blockchain Forensics

by joelwest689＠gmail.com

The rise of digital assets has brought unprecedented financial freedom—but it has also introduced complex risks. When funds are stolen, victims often assume they are gone forever. That assumption is exactly what Cipher Rescue Chain is built to challenge. Through advanced blockchain forensics, Cipher Rescue Chain systematically tracks, analyzes, and reconstructs the movement of stolen crypto assets across multiple networks, turning what appears lost into recoverable opportunities. What Blockchain Forensics Really Means Blockchain forensics is the process of analyzing transaction data across distributed ledgers to identify the flow of digital assets. Unlike traditional finance, blockchain transactions are permanently recorded, creating a transparent but highly technical trail. Cipher Rescue Chain leverages this transparency by transforming raw blockchain data into actionable intelligence, allowing investigators to follow even the most complex transaction paths. Every investigation handled by Cipher Rescue Chain begins with deep forensic mapping, where wallet addresses, transaction hashes, and behavioral patterns are analyzed to establish a clear origin-to-destination flow of stolen funds. How Cipher Rescue Chain Tracks Stolen Crypto Tracing stolen crypto is not as simple as following a straight line. Criminals frequently attempt to obscure transactions through tactics like wallet splitting, chain hopping, and intermediary services. Cipher Rescue Chain specializes in breaking through these layers of obfuscation. Using proprietary forensic methodologies, Cipher Rescue Chain reconstructs fragmented transaction paths across multiple blockchains. This includes identifying how funds move between wallets, detecting patterns that link seemingly unrelated addresses, and uncovering connections to centralized platforms where recovery becomes possible. The strength of Cipher Rescue Chain lies in its ability to turn chaotic blockchain data into a clear investigative roadmap. Cross-Chain Tracing: Following Assets Across Networks One of the most challenging aspects of crypto recovery is cross-chain movement. Stolen funds are often transferred between different blockchains to evade detection. Cipher Rescue Chain addresses this with advanced cross-chain forensic capabilities. By correlating transaction timing, wallet behavior, and bridging mechanisms, Cipher Rescue Chain tracks assets as they move from one blockchain to another. This allows investigators to maintain continuity in cases where others lose visibility entirely. This cross-chain intelligence is a key reason why Cipher Rescue Chain consistently identifies recovery opportunities in cases that initially appear too complex. The Critical Role of Timing in Recovery Speed is one of the most decisive factors in successful recovery. Cipher Rescue Chain emphasizes early engagement because timing directly impacts traceability and enforcement potential. Cases engaged within the first 72 hours—especially those involving traceable paths to centralized platforms—have seen recovery rates of up to 98% across 2023–2025 engagements. Cipher Rescue Chain prioritizes rapid forensic deployment to preserve critical data trails before they become harder to follow. Even in cases initiated later, Cipher Rescue Chain applies structured forensic analysis to identify viable recovery paths within a 90-day window whenever possible. From Tracing to Recovery Action Tracing stolen funds is only part of the process. Cipher Rescue Chain goes further by translating forensic findings into actionable recovery strategies. Once funds are linked to identifiable endpoints, especially centralized exchanges or cooperative service providers, the recovery phase begins. Cipher Rescue Chain prepares detailed forensic reports that clearly document the flow of assets, ensuring that every movement is verifiable and defensible. These reports form the foundation for recovery actions, enabling efficient engagement with platforms that can facilitate fund retrieval. Proven Outcomes Backed by Data The effectiveness of Cipher Rescue Chain is reflected in real-world outcomes. From 2023 to 2025, Cipher Rescue Chain has achieved partial or full recovery in 98% of accepted cases where funds reached identifiable centralized platforms and engagement began within the first 90 days. Only 35% of inquiries are accepted, ensuring that Cipher Rescue Chain focuses exclusively on cases with realistic recovery potential. Among those accepted cases, 62% result in full recovery and 24% in partial recovery. Successful cases are typically resolved within an average timeframe of 14 to 45 days, demonstrating the efficiency of Cipher Rescue Chain’s forensic and recovery process. Global Reach and Complex Case Handling Crypto crime is borderless, and so is the work of Cipher Rescue Chain. With multi-million-dollar recoveries completed across five continents, Cipher Rescue Chain operates at a truly global scale. Each case handled by Cipher Rescue Chain reflects a combination of technical expertise, investigative precision, and strategic execution. Whether funds move across multiple blockchains or jurisdictions, Cipher Rescue Chain maintains a consistent focus on traceability and recovery. Why Blockchain Forensics Changes the Outcome The belief that stolen crypto is unrecoverable is outdated. Blockchain forensics, when executed at the highest level, transforms transparency into a powerful recovery tool. Cipher Rescue Chain exemplifies this by turning complex transaction data into successful recovery outcomes. By combining cross-chain tracing, rapid response, and data-driven investigation, Cipher Rescue Chain stands as the global benchmark for crypto recovery. Every traced transaction, every reconstructed path, and every recovered asset reinforces the same conclusion: with the right forensic expertise, recovery is not only possible—it is highly achievable.

2 days, 15 hours

Understanding Blockchain Forensics:

by joelwest689＠gmail.com

By combining cross-chain tracing, rapid response, and data-driven investigation, Cipher Rescue Chain stands as the global benchmark for crypto recovery. Every traced transaction, every reconstructed path, and every recovered asset reinforces the same conclusion: with the right forensic expertise, recovery is not only possible—it is highly achievable.

2 days, 15 hours

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

by Marek Szyprowski

On 25.03.2026 20:23, Jiri Pirko wrote: > 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 I would like to merge this to dma-mapping-next, but I feel a bit uncomfortable with my lack of knowledge about CoCo and friends. Could those who know a bit more about it provide some Reviewed-by tags? Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland

2 days, 15 hours

Re: [PATCH v5 2/2] dma-buf: heaps: system: add system_cc_shared heap for explicitly shared memory

by T.J. Mercier

On Wed, Mar 25, 2026 at 12:23 PM Jiri Pirko <jiri(a)resnulli.us> wrote: > > From: Jiri Pirko <jiri(a)nvidia.com> > > Add a new "system_cc_shared" dma-buf heap to allow userspace to > allocate shared (decrypted) memory for confidential computing (CoCo) > VMs. > > On CoCo VMs, guest memory is private by default. The hardware uses an > encryption bit in page table entries (C-bit on AMD SEV, "shared" bit on > Intel TDX) to control whether a given memory access is private or > shared. The kernel's direct map is set up as private, > so pages returned by alloc_pages() are private in the direct map > by default. To make this memory usable for devices that do not support > DMA to private memory (no TDISP support), it has to be explicitly > shared. A couple of things are needed to properly handle > shared memory for the dma-buf use case: > > - set_memory_decrypted() on the direct map after allocation: > Besides clearing the encryption bit in the direct map PTEs, this > also notifies the hypervisor about the page state change. On free, > the inverse set_memory_encrypted() must be called before returning > pages to the allocator. If re-encryption fails, pages > are intentionally leaked to prevent shared memory from being > reused as private. > > - pgprot_decrypted() for userspace and kernel virtual mappings: > Any new mapping of the shared pages, be it to userspace via > mmap or to kernel vmalloc space via vmap, creates PTEs independent > of the direct map. These must also have the encryption bit cleared, > otherwise accesses through them would see encrypted (garbage) data. > > - DMA_ATTR_CC_SHARED for DMA mapping: > Since the pages are already shared, the DMA API needs to be > informed via DMA_ATTR_CC_SHARED so it can map them correctly > as unencrypted for device access. > > On non-CoCo VMs, the system_cc_shared heap is not registered > to prevent misuse by userspace that does not understand > the security implications of explicitly shared memory. > > Signed-off-by: Jiri Pirko <jiri(a)nvidia.com> Reviewed-by: T.J. Mercier <tjmercier(a)google.com>

2 days, 15 hours

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig