Linaro-mm-sig March 2026

linaro-mm-sig@lists.linaro.org

133 participants
1109 discussions

Cryptera Chain Signals 2026 Advanced Blockchain Forensics for Digital Asset Protection

by luisannete22＠gmail.com

In the high-stakes world of digital asset protection, where billions are exposed annually to scams and unauthorized activity, Cryptera Chain Signals (CCS) stands as the undisputed leader. While most firms rely solely on basic transaction flow tracing—often leading to dead ends when assets are moved through mixers or cross-chain bridges—CCS employs a groundbreaking Multi-Layer Attribution system. This advanced methodology links wallets with identity certainty, turning guesswork into precise, actionable intelligence. This multi-layer approach analyzes not just direct transfers but deeper patterns: funding sources, gas sponsorship, bridge sequencing, behavioral fingerprints, and DeFi interaction habits. The result? Unparalleled success in tracing and protecting assets, even in the most sophisticated cases. Here's how CCS’s innovative techniques make them the top blockchain forensics partner in 2026. The Huge Difference: Beyond Simple Transaction Flow Traditional firms stop at surface-level tracing: following visible inflows and outflows. Bad actors exploit this by using privacy tools, multiple hops, and chain-switching to obscure trails. CCS goes layers deeper, clustering wallets controlled by the same entity through multiple independent signals. This creates a robust "fingerprint" that persists even when addresses change. In real-world cases, this has enabled CCS to protect and reclaim millions that others deemed untraceable. Funding Source Analysis: Tracing the Origin CCS excels by identifying the initial funding source of suspicious wallets. Bad actors often fund new addresses from centralized exchanges with KYC-linked accounts or known problem pools.Example: In a 2025 unauthorized transfer case protecting $2.3 million in Bitcoin, CCS traced assets to a cluster of wallets. By analyzing funding sources—linking back to deposits from a compromised exchange account with verified user data—they pinpointed the origin. Collaborating with the exchange, CCS froze outflows, enabling full protection and return.This technique reveals the "root" of suspicious activity, providing legal evidence for intervention. Gas Sponsorship Detection: Unmasking Hidden Controllers On networks like Ethereum, "gas sponsorship" (where one wallet pays transaction fees for another) is a telltale sign of common control—often used to hide user-facing addresses.CCS’s tools flag these patterns automatically.Example: During a $737,000 suspicious platform incident, CCS noticed consistent gas payments from a single sponsor wallet to multiple addresses. This sponsorship link clustered them as one entity, allowing tracing through obfuscation layers and asset freeze via global partners.Without this layer, these wallets would appear unrelated. Bridge Sequencing: Cross-Chain Mastery Actors frequently "bridge" assets across chains to evade detection. CCS analyzes bridge sequencing—the timing, amounts, and protocols used—to link pre- and post-bridge wallets.Example: In a $2 million Ethereum case involving cross-chain movement, CCS identified sequential bridges with matching amounts and near-identical timings. This sequencing pattern reconstructed the full path, predicting next moves and enabling proactive intervention with bridges and exchanges.CCS’s cross-chain expertise outshines competitors limited to single-blockchain analysis. Behavioral Fingerprints: Habits That Betray Identity Even anonymous wallets leave behavioral fingerprints: transaction timings, preferred denominations, or interaction styles.CCS uses AI to detect these persistent patterns.Example: Protecting $514,000 from a social-media-based fraud attempt, CCS linked scattered wallets through recurring behaviors—like consistent late-night transactions and fixed-amount movements. These fingerprints tied them to a known group, leading to rapid asset protection.Habits are harder to fake than addresses, making this a powerful attribution tool. DeFi Interaction Habits: Decoding Protocol Patterns DeFi users often follow unique habits: favorite lending pools, yield farming strategies, or swap routes.CCS profiles these DeFi interaction habits to cluster wallets.Example: In a complex $1 million+ unauthorized access case, CCS identified repeated interactions with specific DEXs and liquidity pools across "unrelated" addresses. Matching habits confirmed common ownership, unraveling the movement chain and facilitating protection through protocol partnerships.This layer catches sophisticated actors who vary direct flows but stick to familiar DeFi tools. Why CCS Is the Top Choice in 2026 By combining these five layers, Cryptera Chain Signals achieves identity certainty far beyond competitors. Their transparent model, encrypted client portals, and proven results ensure trust and outcomes. If you've experienced a digital asset incident, don't rely on basic analysis—choose the multi-layer experts. Contact Cryptera Chain Signals today for a free evaluation. Website: https://www.crypterachainsignals.com/ Email: info(a)crypterachainsignals.com

4 months, 1 week

Cryptera Chain Signals 2026 – The Most Trusted Name in Blockchain Forensics & Asset Retrieval

by luisannete22＠gmail.com

As cryptocurrencies continue to reshape the global financial landscape in 2026, digital assets such as Bitcoin, Ethereum, stablecoins, and other tokens have become part of everyday investing. Alongside this growth, however, there has been a noticeable rise in scams, unauthorized transactions, account takeovers, and cases of lost wallet access. When digital assets are compromised, retrieval is rarely simple and often requires expert investigation. In this environment, Cryptera Chain Signals has emerged as a recognized leader in blockchain forensics and asset retrieval, known for its investigative discipline, transparency, and responsible client engagement. Cryptera Chain Signals (CCS), accessible via https://www.crypterachainsignals.com/, focuses on helping victims of digital asset incidents understand what happened, trace where assets moved, and explore legitimate retrieval options. Rather than making unrealistic guarantees, the company emphasizes evidence-based investigation, technical accuracy, and clear communication throughout the entire process. Why Blockchain Forensics & Asset Retrieval Services Are Essential Digital assets operate on decentralized networks, meaning transactions cannot be reversed by a central authority. While this structure supports transparency and independence, it also complicates retrieval when something goes wrong. Losses may result from fraudulent investment platforms, phishing attacks, compromised wallets, forgotten recovery phrases, or unauthorized transfers. Because of these challenges, professional forensics and retrieval services play an important role. Cryptera Chain Signals specializes in navigating the technical and procedural barriers involved in digital asset loss cases. By combining blockchain forensics with investigative coordination, the company helps clients determine whether retrieval is possible and what steps can realistically be taken. What a Legitimate Blockchain Forensics Company Does A legitimate forensics company does more than track transactions. Its role includes detailed case analysis, evidence documentation, and responsible coordination with relevant platforms or authorities when appropriate. Cryptera Chain Signals supports clients in several key areas: • Tracing digital asset movement using blockchain analytics • Analyzing wallet activity and transaction histories • Supporting access restoration in credential-related cases • Coordinating with exchanges to flag suspicious transactions • Preparing investigative documentation when escalation is required This structured approach allows cases to be handled professionally rather than through guesswork or automated tools alone. Why Cryptera Chain Signals Stands Out in 2026 Cryptera Chain Signals has built its reputation by focusing on process, accuracy, and ethical standards. The company’s investigators use advanced blockchain analysis tools to reconstruct transaction paths across multiple networks, including decentralized platforms. This technical capability is essential in cases where funds have been deliberately moved to obscure their origin. Another defining strength is CCS’s collaborative approach. Where appropriate, the company works within compliance frameworks and engages with exchanges or regulatory channels to support retrieval efforts. This level of coordination is especially important in cross-border cases, which are increasingly common in 2026. Client communication is also central to CCS’s identity. Every case begins with a consultation that explains feasibility, limitations, and possible outcomes. Clients receive consistent updates and are informed in plain language, helping them make informed decisions throughout the process. How the CCS Retrieval Process Works Cryptera Chain Signals follows a clear and transparent framework: The process begins with an initial assessment, during which transaction records, wallet addresses, timelines, and incident details are reviewed. This stage determines whether retrieval is technically and procedurally viable. If the case is feasible, a tailored investigation strategy is developed. This may involve blockchain tracing, wallet activity analysis, or coordination with platforms that can take preventative action. During execution, progress is monitored closely and clients receive updates through agreed communication channels. After retrieval efforts conclude, CCS also provides guidance on improving wallet security and reducing future exposure to risk. Verified Client Experiences Clients who have worked with Cryptera Chain Signals often highlight clarity and professionalism rather than promises of instant results. One client, who lost funds through a fraudulent trading platform, reported that CCS helped trace asset movement and document the case in a way that made the situation understandable for the first time. While not all funds were recovered, the investigation provided closure and actionable outcomes. Another client who experienced unauthorized wallet access noted that CCS explained the technical cause of the breach, assisted with partial retrieval, and provided security guidance that prevented further losses. The client emphasized transparency and realistic expectations as key strengths of the company. These experiences reflect CCS’s focus on responsible retrieval rather than speculation. Emerging Trends in Blockchain Forensics in 2026 The forensics industry continues to evolve. Improvements in blockchain analytics and artificial intelligence are making transaction tracing faster and more precise. Regulatory cooperation is also expanding, enabling better coordination between forensics companies, exchanges, and oversight bodies. Education is becoming a major focus as well. Cryptera Chain Signals invests in client awareness, helping individuals recognize common threat structures and improve asset security before incidents occur. Preventing Future Digital Asset Losses While forensics companies provide essential support, prevention remains the strongest defense. CCS encourages best practices such as: • Using reputable hardware wallets for long-term storage • Enabling multi-factor authentication on all accounts • Verifying platforms before investing • Maintaining secure backups of recovery phrases • Staying informed about evolving threat techniques Frequently Asked Questions Does a forensics company guarantee asset return? No. Digital asset retrieval depends on timing, transaction paths, and third-party cooperation. A legitimate company provides investigation and guidance, not guarantees. What cases does Cryptera Chain Signals handle? CCS assists with unauthorized access, lost credentials, unauthorized transfers, and complex transaction tracing. How long does retrieval take? Timelines vary widely. Some cases progress quickly, while others require extended investigation. How are fees structured? Costs depend on case complexity. CCS explains all terms clearly during consultation before any work begins. Conclusion: Choosing a Responsible Forensics Partner in 2026 In 2026, blockchain forensics companies play an important role in helping individuals and businesses respond to digital asset loss. Cryptera Chain Signals stands out by prioritizing investigation, transparency, and ethical practice over unrealistic claims. By focusing on technical accuracy and client understanding, CCS provides a legitimate pathway for those seeking clarity and potential resolution after digital incidents. For consultation or further information, Cryptera Chain Signals can be contacted at: Website: https://www.crypterachainsignals.com/ Email: info(a)crypterachainsignals.com

4 months, 1 week

Why Cryptera Chain Signals

by rogerstewer＠gmail.com

As cryptocurrencies continue to reshape finance in 2026, the risk of scams, hacks, and lost access credentials remains a major challenge. Recovering lost or stolen digital assets requires expert intervention, and Cryptera Chain Signals (CCS), accessible via https://www.crypterachainsignals.com/, stands out as a leading and trusted crypto recovery provider. With advanced blockchain forensics, a strong emphasis on client support, and a proven track record, Cryptera Chain Signals offers reliable solutions to help reclaim assets. This guide highlights top crypto recovery approaches for 2026, with Cryptera Chain Signals recognized for its professionalism, and explores emerging trends and FAQs to guide your recovery journey. Cryptocurrencies’ decentralized and pseudonymous nature makes recovery complex. Losses from scams, forgotten seed phrases, or hacked wallets highlight the need for professional services. Cryptera Chain Signals specializes in navigating these issues, using cutting-edge tools and realistic strategies to trace funds and restore access where feasible. Crypto recovery services assist with: Tracing stolen funds: Blockchain analytics to track transaction paths. Recovering access: Resolving wallet lockouts (e.g., lost seeds/hardware issues). Legal support: Coordinating with authorities for viable cases. Exchange coordination: Assisting platforms to freeze suspicious accounts. Cryptera Chain Signals excels in these areas, leveraging proprietary multi-layer wallet attribution and partnerships for tracing across chains, mixers, bridges, and DeFi protocols—making it a strong choice for complex cases. Several services stand out in 2026, but Cryptera Chain Signals is frequently praised for its transparency and results: Advanced blockchain forensics: Proprietary tools trace funds precisely, even in obfuscated cases, with detailed reports and high success in viable scenarios (e.g., 90% recoveries noted in client testimonials for phishing/scams). Client-centric support: Free consultations, 24/7 availability, ongoing updates, and educational guidance on prevention build trust. Proven track record: Over 426 successful projects, 28 years in digital forensics/cybersecurity, and a 4.28/5 rating from 2,467+ verified reviews. Global reach: International support addresses cross-border issues effectively. Contact Cryptera Chain Signals at info(a)crypterachainsignals.com for a free consultation to start your recovery journey. Other reputable options include: Crypto Asset Recovery specialists: Focus on lost seed phrases and inaccessible wallets with technical expertise. Wallet Recovery Services: Excel in private key/wallet restoration for complex access issues. While these are solid, Cryptera Chain Signals’ comprehensive forensics-driven approach and client feedback make it highly regarded for 2026. Cryptera Chain Signals follows a structured, transparent process: Initial assessment: Free consultation gathers TXIDs, addresses, and details to evaluate feasibility. Customized strategy: AI-enhanced analytics trace movements and outline plans (e.g., exchange coordination or authority support). Execution and monitoring: Implement steps with regular client updates. Post-recovery support: Guidance on security (e.g., MFA, hardware wallets) to prevent future losses. The crypto recovery landscape evolves with trends: Enhanced blockchain analysis: AI/machine learning for faster tracing, as seen in Cryptera Chain Signals’ multi-layer attribution. Stronger regulatory ties: Cooperation with agencies like IC3 streamlines actions. Consumer education: Emphasis on prevention via resources and guidance. Prevention is key—follow these practices: Use hardware wallets (Ledger/Trezor) for offline storage. Enable multi-factor authentication. Verify platforms and stay informed on scam tactics. Use secure backups and avoid sharing seeds/keys. Q1: Does working with a recovery service guarantee asset return? A1: No—blockchain complexity means no guarantees. Cryptera Chain Signals maximizes chances in viable cases through forensics and coordination, with strong testimonials in scam/phishing recoveries. Q2: What situations do recovery services help with? A2: Cryptera Chain Signals assists with hacked wallets, lost private keys/seeds, erroneous transactions, scams, phishing, and hardware failures. Q3: How long does recovery take? A3: Timelines vary (days to months) based on complexity and cooperation. Cryptera Chain Signals’ swift assessments and 24/7 support accelerate viable cases. Q4: What are the costs? A4: Varies; Cryptera Chain Signals offers flexible, transparent structures discussed in free consultations—focus on realistic, client-aligned terms. In 2026, crypto recovery services remain essential for reclaiming assets. Cryptera Chain Signals leads with advanced forensics, ethical practices, and client-focused support. Act swiftly and engage via official channels for confidence in the process. Website: https://www.crypterachainsignals.com/ Email: info(a)crypterachainsignals.com Secure your assets and leverage Cryptera Chain Signals’ expertise to navigate recovery in 2026. With a solid reputation for professionalism and results, it offers a dependable path forward. Always report incidents to authorities (e.g., FBI IC3) first, document evidence, and verify providers independently to avoid secondary scams.

4 months, 1 week

How Funds Reclaimer Company Investigates Pig Butchering Fraud

by petersongreg565＠gmail.com

I am writing to express my deepest gratitude to FUNDS RECLAIMER COMPANY for their invaluable assistance in recovering my Bitcoin, which was unfortunately lost to a scammer. The expertise and professionalism displayed by their team were instrumental in retrieving my stolen funds, and I am truly thankful for their support throughout this ordeal. After falling victim to a sophisticated scam, I thought all hope was lost, and my Bitcoin was gone for good. However, I decided to reach out to FUNDS RECLAIMER COMPANY, and their team promptly responded with a clear plan of action to recover my stolen funds. Their dedication and expertise in navigating the complexities of cryptocurrency transactions were impressive, and they worked tirelessly to track down the scammer and retrieve my Bitcoin. The entire process, from initial consultation to the final recovery of my funds, was handled with utmost care and transparency. The team at FUNDS RECLAIMER COMPANY kept me informed every step of the way, providing regular updates on the progress of the recovery efforts. Their commitment to customer satisfaction was evident in the way they handled my case, and I was constantly reassured that my case was being treated with the utmost importance. I am thrilled to have my Bitcoin back, and I attribute this success entirely to the exceptional work of FUNDS RECLAIMER COMPANY. Their knowledge and experience in dealing with cryptocurrency scams are unparalleled, and I would highly recommend their services to anyone who has fallen victim to similar situations. The company's expertise and professionalism are a beacon of hope for those who have lost their funds to scammers, and I am living proof of their ability to deliver results. In conclusion, I would like to extend my sincerest appreciation to FUNDS RECLAIMER COMPANY for their outstanding service and support. Their expertise and dedication have given me a second chance to recover my lost Bitcoin, and I will be forever grateful for their help. If you or someone you know has been a victim of a cryptocurrency scam, I strongly recommend reaching out to FUNDS RECLAIMER COMPANY for assistance. They are truly the experts in recovering lost funds, and their professionalism and transparency make them a trusted partner in the fight against scammers. Info Below: Website: https//:funds-reclaimercompany.org Email: fundsreclaimer(a)consultant.com

4 months, 1 week

[#FCH-3077772]: Notification from lists.linaro.org

by Technical Support

4 months, 1 week

[PATCH v2 00/12] media: stm32: dcmi: stability & performance enhancements

by Alain Volmat

This series improve stability of the capture by fixing the handling of the overrun which was leading to captured frame corruption. Locking within the driver is also simplified and the way DMA is handled is reworked allowing to avoid having a specific handling for the JPEG data. Performances of capture can now be increased via the usage of a DMA->MDMA chaining which allows for capture of higher resolution / framerate. Signed-off-by: Alain Volmat <alain.volmat(a)foss.st.com> --- Changes in v2: - Fix pm_sleep_ptr -> pm_ptr to avoid unused function warning - Fix typo / remove useless comment in binding - Link to v1: https://lore.kernel.org/r/20251218-stm32-dcmi-dma-chaining-v1-0-39948ca6cbf… --- Alain Volmat (12): media: stm32: dcmi: Switch from __maybe_unused to pm_ptr() media: stm32: dcmi: perform dmaengine_slave_config at probe media: stm32: dcmi: only create dma descriptor once at buf_prepare media: stm32: dcmi: stop the dma transfer on overrun media: stm32: dcmi: rework spin_lock calls media: stm32: dcmi: perform all dma handling within irq_thread media: stm32: dcmi: use dmaengine_terminate_async in irq context media: stm32: dcmi: continuous mode capture in JPEG dt-bindings: media: st: dcmi: add DMA-MDMA chaining properties media: stm32: dcmi: addition of DMA-MDMA chaining support ARM: dts: stm32: add sram node within stm32mp151.dtsi ARM: dts: stm32: enable DCMI DMA-MDMA chaining on stm32mp157c-ev1.dts .../devicetree/bindings/media/st,stm32-dcmi.yaml | 11 +- arch/arm/boot/dts/st/stm32mp151.dtsi | 8 + arch/arm/boot/dts/st/stm32mp157c-ev1.dts | 15 + drivers/media/platform/st/stm32/stm32-dcmi.c | 475 +++++++++++++-------- 4 files changed, 341 insertions(+), 168 deletions(-) --- base-commit: f7231cff1f3ff8259bef02dc4999bc132abf29cf change-id: 20251213-stm32-dcmi-dma-chaining-9ea1da83007d Best regards, -- Alain Volmat <alain.volmat(a)foss.st.com>

4 months, 1 week

Premier US-Based Hardware Wallet Recovery Service: An In-Depth Look at Cryptera Chain Signals

by rogerstewer＠gmail.com

In the high-stakes world of digital assets, losing access to a hardware wallet—due to a forgotten PIN, damaged device, misplaced seed phrases, or hardware failure—can be devastating. The recovery industry for these scenarios demands extreme technical expertise, forensic precision, and unwavering trust. Among providers addressing hardware wallet challenges, Cryptera Chain Signals stands out as a leading, trusted option with capabilities in wallet lockout resolutions and asset restoration, often highlighted in client feedback for handling such cases effectively. This article examines their operational profile, methods, and key factors potential clients must consider when seeking specialized recovery for hardware wallets like Ledger, Trezor, or similar devices. Operational Profile and Unique Positioning Cryptera Chain Signals positions itself as a professional, client-focused provider with a strong emphasis on digital forensics and cybersecurity. Key attributes include: Global Expertise with US Accessibility: While operating internationally, they offer toll-free support for US clients, ensuring jurisdictional familiarity and ease of access under professional standards. Forensic and Cybersecurity Pedigree: With 28 years in digital forensics and cybersecurity, their team specializes in tracing stolen assets, resolving wallet access issues (including hardware-related lockouts), and investigating scams/phishing that may affect hardware wallets. Specialized Wallet Recovery Focus: They handle wallet lockout resolutions, such as forgotten seeds/hardware issues, using proprietary multi-layer wallet attribution and forensic tools. This extends to recovering access or tracing funds in compromised scenarios without requiring private keys or seeds upfront. Compliance and Security Framework: Processes prioritize confidentiality, secure communications, and ethical practices—no private key requests, free consultations, and realistic assessments. They emphasize data minimization and prevention education (e.g., multisig setups, secure backups). Proven Track Record: Over 426 successful projects reported, with client testimonials noting quick resolutions for lost wallet access and high recovery percentages in viable cases (e.g., 90% from phishing or scam-related losses involving hardware wallets). A 4.28/5 rating from 2,467+ verified reviews underscores consistent satisfaction. The Hallmarks of a Legitimate Recovery Service Cryptera Chain Signals aligns with industry expectations for credible providers: Clear Processes and Transparency: Free case assessments outline realistic expectations—if recovery isn't feasible (e.g., due to physical destruction of secure elements), they communicate honestly. Forensic Methodology: Proprietary tools for multi-layer attribution trace paths and support access restoration or fund recovery, producing detailed reports. No High-Risk Requests: Never ask for seeds, private keys, or remote access—essential for distinguishing legitimate services. Client-Centric Focus: 24/7 support, educational guidance on prevention, and emphasis on swift action for time-sensitive cases. Essential Due Diligence and Critical Considerations Engaging any recovery service requires thorough verification—hardware wallet recovery is highly technical and limited by device security (e.g., no service can bypass a truly destroyed secure chip without seeds). Independent Verification: Cross-check reviews on trusted platforms, search for media mentions or forum discussions, and confirm claims through direct consultation. Technical and Legal Scope: Understand conditions—success is higher for software/firmware issues or traceable funds post-compromise than for irreversible hardware damage. Forensic reports may support legal/estate needs. Security and Contractual Terms: Demand a clear agreement outlining processes, fees (often flexible or success-aligned), data handling (e.g., secure deletion of images), and confidentiality. Have it reviewed by your attorney. Beware Absolute Guarantees: Claims of "100% success" warrant skepticism—complex damage can be insurmountable. Focus on providers offering honest evaluations. Red Flags: Upfront non-refundable large fees, seed phrase requests, unsolicited contacts, or no verifiable reviews. Conclusion Cryptera Chain Signals presents a profile of a reliable, forensics-driven provider well-suited for hardware wallet access issues, lost seeds/hardware failures, or related scam recoveries. For individuals, attorneys, or estates dealing with significant assets locked in devices like Trezor or Ledger, their specialized tools, strong client feedback, and transparent approach offer a viable path forward. Always start by reporting to authorities (e.g., FBI IC3 at ic3.gov) if theft is involved, document evidence, and act promptly. Contact them directly for a free assessment: Website: https://www.crypterachainsignals.com/ Email: info(a)crypterachainsignals.com Proceed with caution: Verify independently, prioritize facts over promises, and avoid secondary scams targeting desperate victims. With the right expertise and evidence, many hardware wallet challenges become solvable investigations.

4 months, 1 week

[RFC PATCH 2/7] virtio: use pr_debug_ratelimited to avoid flooding

by Jim Cromie

When I test dynamic-debug's static-key toggling performance in a virtme-ng session, it is too easy to create an enormous flood of printks to the console. #> echo +p > /proc/dynamic_debug/control #> echo -p > /proc/dynamic_debug/control Now theres no "good reason" to shoot your own foot, but this is also easy to fix, by ratelimiting the sources of the flood. I don't think theres a loss of utility to virtio. Example console output is below the snip. For this test-case, ratelimiting suppresses >900k callbacks. It also allows this simple load test for the static-key toggling performance in a following patch. Signed-off-by: Jim Cromie <jim.cromie(a)gmail.com> --- root@drm-misc-fixes-2026-02-26-80-g9a2f253ad689:/home/jimc/projects/lx/wk-D/b0-dd# ddcmdq -p [ 619.868567] dyndbg: query 0: "-p" mod:* Delta-CAL (IPI): 71 - above is a noop baseline. root@drm-misc-fixes-2026-02-26-80-g9a2f253ad689:/home/jimc/projects/lx/wk-D/b0-dd# ddcmdq +p [ 648.876520] dyndbg: query 0: "+p" mod:* [ 648.878263] dyndbg: match on module: led_class [ 648.878350] dyndbg: match on module: probe [ 648.878474] dyndbg: match on module: pci [ 648.878636] dyndbg: match on module: pci_driver [ 648.878743] dyndbg: match on module: irq [ 648.878845] dyndbg: match on module: setup_bus [ 648.879032] dyndbg: match on module: pcieportdrv [ 648.879139] dyndbg: match on module: bwctrl [ 648.879197] dyndbg: match on module: aspm [ 648.879241] dyndbg: match on module: slot [ 648.879328] dyndbg: match on module: pci_acpi [ 648.879431] dyndbg: match on module: quirks [ 648.879521] dyndbg: match on module: pci_hotplug [ 648.879576] dyndbg: match on module: vgaarb [ 648.879710] dyndbg: match on module: backlight [ 648.879826] dyndbg: match on module: fb [ 648.879900] dyndbg: match on module: tables [ 648.880012] dyndbg: match on module: acpi [ 648.880977] dyndbg: match on module: ac [ 648.881021] dyndbg: match on module: button [ 648.881097] dyndbg: match on module: fan [ 648.881196] dyndbg: match on module: video [ 648.881295] dyndbg: match on module: processor [ 648.881558] dyndbg: match on module: thermal_lib [ 648.881671] dyndbg: match on module: thermal [ 648.881784] dyndbg: match on module: srat [ 648.881860] dyndbg: match on module: battery [ 648.881938] dyndbg: match on module: acpi_x86 [ 648.882088] dyndbg: match on module: pnp [ 648.882219] dyndbg: match on module: dmaengine [ 648.882351] dyndbg: match on module: virt_dma [ 648.882429] dyndbg: match on module: acpi_dma [ 648.882518] dyndbg: match on module: dw_dmac_core [ 648.882619] dyndbg: match on module: virtio_ring [ 648.882833] dyndbg: match on module: tty_io [ 648.882835] virtqueue_get_buf_ctx_split: 852672 callbacks suppressed [ 648.882836] No more buffers in queue [ 648.882837] virtqueue_add_split: 4962 callbacks suppressed [ 648.882838] Added buffer head 0 to 00000000531af360 [ 648.882842] No more buffers in queue [ 648.882843] No more buffers in queue [ 648.882843] No more buffers in queue [ 648.882844] No more buffers in queue [ 648.882844] No more buffers in queue [ 648.882845] No more buffers in queue [ 648.882845] No more buffers in queue [ 648.882846] No more buffers in queue [ 648.882846] No more buffers in queue [ 648.882857] Added buffer head 0 to 00000000531af360 [ 648.882869] Added buffer head 0 to 00000000531af360 [ 648.882874] vring_interrupt: 88637 callbacks suppressed [ 648.882876] virtqueue interrupt with no work for 00000000e20c0e9d [ 648.882882] Added buffer head 0 to 00000000531af360 [ 648.882899] Added buffer head 0 to 00000000531af360 [ 648.882909] Added buffer head 0 to 00000000531af360 [ 648.882919] Added buffer head 0 to 00000000531af360 [ 648.882930] Added buffer head 0 to 00000000531af360 [ 648.882941] Added buffer head 0 to 00000000531af360 [ 648.882951] Added buffer head 0 to 00000000531af360 [ 648.883860] virtqueue interrupt with no work for 00000000531af360 [ 648.883920] virtqueue interrupt with no work for 0000000088284d45 [ 648.883980] virtqueue interrupt with no work for 000000006b8c4aa3 [ 648.884033] virtqueue interrupt with no work for 00000000f205a9b7 [ 648.884085] virtqueue interrupt with no work for 0000000021930e68 [ 648.884138] virtqueue interrupt with no work for 0000000081dad94c [ 648.884190] virtqueue interrupt with no work for 0000000097d16d2d [ 648.884243] virtqueue interrupt with no work for 00000000b4539010 [ 648.884296] virtqueue interrupt with no work for 00000000ac870038 [ 648.884418] dyndbg: match on module: tty_jobctrl [ 648.884476] dyndbg: match on module: vt_ioctl [ 648.884528] dyndbg: match on module: serial_base [ 648.884625] dyndbg: match on module: 8250 [ 648.884698] dyndbg: match on module: 8250_base [ 648.884795] dyndbg: match on module: 8250_exar [ 648.884856] dyndbg: match on module: 8250_pci [ 648.884962] dyndbg: match on module: 8250_pericom [ 648.885014] dyndbg: match on module: virtio_console [ 648.885091] dyndbg: match on module: iommu [ 648.885132] dyndbg: match on module: init [ 648.885174] dyndbg: match on module: ppr [ 648.885216] dyndbg: match on module: iommu [ 648.885256] dyndbg: match on module: dmar [ 648.885334] dyndbg: match on module: iommu [ 648.885419] dyndbg: match on module: virtio_iommu [ 648.885481] dyndbg: match on module: drm [ 648.885577] dyndbg: match on module: ttm [ 648.885651] dyndbg: match on module: component [ 648.885756] dyndbg: match on module: core [ 648.885979] dyndbg: match on module: bus [ 648.886081] dyndbg: match on module: dd [ 648.886238] dyndbg: match on module: syscore [ 648.886339] dyndbg: match on module: class [ 648.886429] dyndbg: match on module: platform [ 648.886519] dyndbg: match on module: faux [ 648.886567] dyndbg: match on module: main [ 648.886664] dyndbg: match on module: wakeup [ 648.886765] dyndbg: match on module: firmware_class [ 648.886925] dyndbg: match on module: regmap [ 648.886971] dyndbg: match on module: regcache [ 648.887089] dyndbg: match on module: regcache_flat [ 648.887142] dyndbg: match on module: regmap_debugfs [ 648.887195] dyndbg: match on module: mei [ 648.887914] dyndbg: match on module: mei_me [ 648.888149] dyndbg: match on module: dax [ 648.888267] dyndbg: match on module: dma_buf [ 648.888322] dyndbg: match on module: scsi_mod [ 648.888413] dyndbg: match on module: virtio_scsi [ 648.888486] dyndbg: match on module: libata [ 648.888736] dyndbg: match on module: ahci [ 648.888816] dyndbg: match on module: libahci [ 648.888895] dyndbg: match on module: ata_piix [ 648.888960] dyndbg: match on module: pata_amd [ 648.889050] dyndbg: match on module: pata_oldpiix [ 648.889124] dyndbg: match on module: pata_sch [ 648.889172] dyndbg: match on module: mdio_bus [ 648.889229] dyndbg: match on module: libphy [ 648.889303] dyndbg: match on module: realtek [ 648.889395] dyndbg: match on module: fwnode_mdio [ 648.889468] dyndbg: match on module: virtio_net [ 648.889697] dyndbg: match on module: pcmcia_core [ 648.889848] dyndbg: match on module: pcmcia [ 648.890263] dyndbg: match on module: pci_quirks [ 648.890322] dyndbg: match on module: i8042 [ 648.890355] dyndbg: match on module: libps2 [ 648.890441] dyndbg: match on module: input_core [ 648.890546] dyndbg: match on module: ff_memless [ 648.890670] dyndbg: match on module: atkbd [ 648.890724] dyndbg: match on module: psmouse [ 648.890981] dyndbg: match on module: rtc_core [ 648.891135] dyndbg: match on module: rtc_cmos [ 648.891242] dyndbg: match on module: i2c_boardinfo [ 648.891303] dyndbg: match on module: i2c_core [ 648.891519] dyndbg: match on module: i2c_smbus [ 648.891624] dyndbg: match on module: i2c_i801 [ 648.891757] dyndbg: match on module: pps_core [ 648.891925] dyndbg: match on module: power_supply [ 648.892085] dyndbg: match on module: hwmon [ 648.892129] dyndbg: match on module: thermal_sys [ 648.892260] dyndbg: match on module: therm_throt [ 648.892315] dyndbg: match on module: md_mod [ 648.892570] dyndbg: match on module: dm_mod [ 648.892696] dyndbg: match on module: sysfs [ 648.892741] dyndbg: match on module: dmi_scan [ 648.892787] dyndbg: match on module: qemu_fw_cfg [ 648.892889] dyndbg: match on module: esrt [ 648.892935] dyndbg: match on module: mailbox [ 648.893006] dyndbg: match on module: pcc [ 648.893051] dyndbg: match on module: nvmem_core [ 648.893103] dyndbg: match on module: snd [ 648.893191] dyndbg: match on module: snd_timer [ 648.893249] dyndbg: match on module: snd_pcm [ 648.893356] dyndbg: match on module: snd_seq [ 648.893514] dyndbg: match on module: snd_intel8x0 [ 648.893572] dyndbg: match on module: snd_ac97_codec [ 648.893667] dyndbg: match on module: snd_hda_core [ 648.893867] dyndbg: match on module: snd_intel_dspcfg [ 648.894017] dyndbg: match on module: snd_intel_sdw_acpi [ 648.894131] dyndbg: match on module: snd_hda_codec [ 648.894336] dyndbg: match on module: snd_hda_codec_realtek_lib [ 648.894479] dyndbg: match on module: snd_hda_codec_alc269 [ 648.894585] dyndbg: match on module: snd_hda_scodec_component [ 648.894655] dyndbg: match on module: snd_hda_codec_generic [ 648.894775] dyndbg: match on module: snd_hda_intel [ 648.894939] dyndbg: match on module: sock [ 648.894987] dyndbg: match on module: dev [ 648.895119] dyndbg: match on module: sch_api [ 648.895174] dyndbg: match on module: route [ 648.895215] dyndbg: match on module: ip_fragment [ 648.895264] dyndbg: match on module: ip_output [ 648.895313] dyndbg: match on module: tcp [ 648.895350] dyndbg: match on module: tcp_input [ 648.895468] dyndbg: match on module: tcp_output [ 648.895575] dyndbg: match on module: tcp_timer [ 648.895634] dyndbg: match on module: tcp_ipv4 [ 648.895687] dyndbg: match on module: tcp_cong [ 648.895743] dyndbg: match on module: tcp_fastopen [ 648.895796] dyndbg: match on module: tcp_recovery [ 648.895854] dyndbg: match on module: udp [ 648.895951] dyndbg: match on module: arp [ 648.895994] dyndbg: match on module: icmp [ 648.896096] dyndbg: match on module: devinet [ 648.896151] dyndbg: match on module: fib_trie [ 648.896250] dyndbg: match on module: ping [ 648.896409] dyndbg: match on module: sysctl_net_ipv4 [ 648.896505] dyndbg: match on module: ipconfig [ 648.896567] dyndbg: match on module: tcp_cubic [ 648.896625] dyndbg: match on module: ip6_checksum [ 648.896718] dyndbg: match on module: sysctl_net [ 648.896832] dyndbg: match on module: i386 [ 648.896886] dyndbg: match on module: mmconfig_shared [ 648.896944] dyndbg: match on module: fixup [ 648.897029] dyndbg: match on module: acpi [ 648.897087] dyndbg: match on module: irq [ 648.897185] dyndbg: match on module: decompress [ 648.897253] dyndbg: match on module: kobject [ 648.897366] dyndbg: match on module: kobject_uevent [ 648.897478] dyndbg: applied queued updates to 1900 sites in total [ 648.897586] applying 1879 queued jump_labels [ 648.898378] virtqueue callback for 00000000b8493952 (000000004941ab6e) [ 648.898493] virtio_fs_send_req: opcode 5 unique 0x45a0 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.898493] virtio_fs_send_req: opcode 5 unique 0x459e nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.898582] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.898752] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.898905] virtio_fs_send_req: opcode 5 unique 0x45a2 nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.898912] virtio_fs_send_req: opcode 5 unique 0x45a4 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.899066] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.899183] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.899276] virtio_fs_send_req: opcode 5 unique 0x45a6 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.899281] virtio_fs_send_req: opcode 5 unique 0x45a8 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.899413] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.899528] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.899608] virtio_fs_send_req: opcode 5 unique 0x45ac nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.899608] virtio_fs_send_req: opcode 5 unique 0x45aa nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.899711] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.899850] virtqueue callback for 00000000531af360 (00000000df837aee) [ 648.899957] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.899989] virtio_fs_send_req: opcode 5 unique 0x45ae nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.899992] virtio_fs_send_req: opcode 5 unique 0x45b0 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.900080] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.900084] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.900520] virtio_fs_send_req: opcode 5 unique 0x45b2 nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.900557] virtio_fs_send_req: opcode 5 unique 0x45b4 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.900725] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.901958] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.902056] virtio_fs_send_req: opcode 5 unique 0x45b6 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.902069] virtio_fs_send_req: opcode 14 unique 0x45b8 nodeid 0x245 in.len 48 out.len 16 queue_id 1 [ 648.902292] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.902409] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.902506] virtio_fs_send_req: opcode 5 unique 0x45ba nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.902507] overlayfs: open(00000000cc553079[bin/grep/l], 0100040) -> (00000000ebc0a9b2, 01100040) [ 648.902707] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.902793] virtio_fs_send_req: opcode 5 unique 0x45bc nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.902861] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.903071] virtio_fs_send_req: opcode 14 unique 0x45be nodeid 0x28 in.len 48 out.len 16 queue_id 1 [ 648.903072] virtio_fs_send_req: opcode 5 unique 0x45c0 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.903325] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.903329] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.903546] overlayfs: open(0000000044db1ed7[lib64/ld-linux-x86-64.so.2/l], 0100040) -> (00000000ce7f73a3, 01100040) [ 648.903629] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.903800] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.903896] virtio_fs_send_req: opcode 5 unique 0x45c2 nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.903921] virtio_fs_send_req: opcode 14 unique 0x45c4 nodeid 0x2b in.len 48 out.len 16 queue_id 1 [ 648.904123] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.904252] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.904382] overlayfs: open(0000000044db1ed7[/ld.so.cache/l], 0100000) -> (00000000a546e0ec, 01100000) [ 648.904421] virtio_fs_send_req: opcode 5 unique 0x45c6 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.904521] virtio_fs_send_req: opcode 25 unique 0x45c8 nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.904698] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.904849] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.904982] virtio_fs_send_req: opcode 5 unique 0x45ca nodeid 0x2f2 in.len 40 out.len 4095 queue_id 1 [ 648.905003] virtio_fs_send_req: opcode 5 unique 0x45cc nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.905214] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.905333] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.905469] virtio_fs_send_req: opcode 14 unique 0x45ce nodeid 0x2f3 in.len 48 out.len 16 queue_id 1 [ 648.905476] virtio_fs_send_req: opcode 5 unique 0x45d0 nodeid 0x4b in.len 40 out.len 4095 queue_id 1 [ 648.905672] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.905803] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.905910] overlayfs: open(00000000b23a5ecd[bin/gawk/l], 0100040) -> (0000000042a63553, 01100040) [ 648.905918] virtio_fs_send_req: opcode 14 unique 0x45d2 nodeid 0x4c in.len 48 out.len 16 queue_id 1 [ 648.906095] virtio_fs_send_req: opcode 5 unique 0x45d4 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.906255] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.906359] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.906486] overlayfs: open(0000000044db1ed7[lib64/libpcre2-8.so.0.15.0/l], 0100000) -> (00000000761f1272, 01100000) [ 648.906498] virtio_fs_send_req: opcode 14 unique 0x45d6 nodeid 0x28 in.len 48 out.len 16 queue_id 1 [ 648.906653] virtio_fs_send_req: opcode 25 unique 0x45d8 nodeid 0x4c in.len 64 out.len 0 queue_id 1 [ 648.906842] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.906929] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.907050] overlayfs: open(000000001dc27c49[lib64/ld-linux-x86-64.so.2/l], 0100040) -> (00000000cb9765b4, 01100040) [ 648.907060] virtio_fs_send_req: opcode 5 unique 0x45da nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.907329] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.907428] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.907453] virtio_fs_send_req: opcode 14 unique 0x45dc nodeid 0x2b in.len 48 out.len 16 queue_id 1 [ 648.907633] virtio_fs_send_req: opcode 14 unique 0x45de nodeid 0x30 in.len 48 out.len 16 queue_id 1 [ 648.907709] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.907848] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.907943] overlayfs: open(0000000044db1ed7[lib64/libc.so.6/l], 0100000) -> (000000003b97b39b, 01100000) [ 648.907943] overlayfs: open(000000001dc27c49[/ld.so.cache/l], 0100000) -> (00000000fce78bd3, 01100000) [ 648.908091] virtio_fs_send_req: opcode 25 unique 0x45e0 nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.908169] virtio_fs_send_req: opcode 25 unique 0x45e2 nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.908341] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.908447] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.908581] virtio_fs_send_req: opcode 5 unique 0x45e4 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.908724] virtio_fs_send_req: opcode 18 unique 0x45e6 nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.908776] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.908895] virtio_fs_send_req: opcode 14 unique 0x45e8 nodeid 0x2a7 in.len 48 out.len 16 queue_id 1 [ 648.908956] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.909155] virtio_fs_send_req: opcode 5 unique 0x45ea nodeid 0x2f4 in.len 40 out.len 4095 queue_id 1 [ 648.909156] overlayfs: open(0000000044db1ed7[locale/locale-archive/l], 0100000) -> (00000000a546e0ec, 01100000) [ 648.909346] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.909427] virtio_fs_send_req: opcode 25 unique 0x45ec nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.909506] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.909725] virtio_fs_send_req: opcode 14 unique 0x45ee nodeid 0x2f5 in.len 48 out.len 16 queue_id 1 [ 648.909764] virtio_fs_send_req: opcode 14 unique 0x45f0 nodeid 0x2a9 in.len 48 out.len 16 queue_id 1 [ 648.910023] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.910119] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.910240] overlayfs: open(0000000044db1ed7[gconv/gconv-modules.cache/l], 0100000) -> (0000000046b528d3, 01100000) [ 648.910245] overlayfs: open(000000001dc27c49[lib64/libreadline.so.8.3/l], 0100000) -> (000000006c3dd911, 01100000) [ 648.910382] virtio_fs_send_req: opcode 25 unique 0x45f2 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.910515] virtio_fs_send_req: opcode 25 unique 0x45f4 nodeid 0x2f5 in.len 64 out.len 0 queue_id 1 [ 648.910662] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.910775] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.910915] virtio_fs_send_req: opcode 5 unique 0x45f6 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.910930] virtio_fs_send_req: opcode 14 unique 0x45f8 nodeid 0x2b2 in.len 48 out.len 16 queue_id 1 [ 648.911124] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.911233] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.911331] overlayfs: open(0000000044db1ed7[locale/locale.alias/l], 0100000) -> (000000001b94a7b7, 01100000) [ 648.911332] virtio_fs_send_req: opcode 5 unique 0x45fa nodeid 0x2f6 in.len 40 out.len 4095 queue_id 1 [ 648.911483] virtio_fs_send_req: opcode 25 unique 0x45fc nodeid 0x2b2 in.len 64 out.len 0 queue_id 1 [ 648.911664] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.911757] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.911865] virtio_fs_send_req: opcode 18 unique 0x45fe nodeid 0x2b2 in.len 64 out.len 0 queue_id 1 [ 648.911870] virtio_fs_send_req: opcode 14 unique 0x4600 nodeid 0x2f7 in.len 48 out.len 16 queue_id 1 [ 648.912086] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.912188] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.912284] overlayfs: open(000000001dc27c49[lib64/libmpfr.so.6.2.2/l], 0100000) -> (00000000dd259cff, 01100000) [ 648.912289] virtio_fs_send_req: opcode 18 unique 0x4602 nodeid 0x28 in.len 64 out.len 0 queue_id 1 [ 648.912456] virtio_fs_send_req: opcode 25 unique 0x4604 nodeid 0x2f7 in.len 64 out.len 0 queue_id 1 [ 648.912515] virtio_fs_send_req: opcode 18 unique 0x4606 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.912599] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.912603] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.912924] virtio_fs_send_req: opcode 18 unique 0x4608 nodeid 0x4c in.len 64 out.len 0 queue_id 1 [ 648.912943] virtio_fs_send_req: opcode 5 unique 0x460a nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.913017] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.913020] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.913078] virtio_fs_send_req: opcode 18 unique 0x460c nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.913298] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.913356] virtio_fs_send_req: opcode 18 unique 0x460e nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.913463] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.913537] virtio_fs_send_req: opcode 18 unique 0x4610 nodeid 0x245 in.len 64 out.len 0 queue_id 1 [ 648.913877] virtio_fs_send_req: opcode 5 unique 0x4612 nodeid 0x2f8 in.len 40 out.len 4095 queue_id 1 [ 648.913927] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.914084] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.914219] virtio_fs_send_req: opcode 14 unique 0x4614 nodeid 0x2f9 in.len 48 out.len 16 queue_id 1 [ 648.914388] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.914488] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.914586] overlayfs: open(000000001dc27c49[lib64/libgmp.so.10.5.0/l], 0100000) -> (00000000c480dc70, 01100000) [ 648.914746] virtio_fs_send_req: opcode 25 unique 0x4616 nodeid 0x2f9 in.len 64 out.len 0 queue_id 1 [ 648.914898] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.914993] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.915130] virtio_fs_send_req: opcode 5 unique 0x4618 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.915297] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.915391] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.915500] virtio_fs_send_req: opcode 14 unique 0x461a nodeid 0x42 in.len 48 out.len 16 queue_id 1 [ 648.915676] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.915772] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.915873] overlayfs: open(000000001dc27c49[lib64/libm.so.6/l], 0100000) -> (00000000aab89989, 01100000) [ 648.916022] virtio_fs_send_req: opcode 25 unique 0x461c nodeid 0x42 in.len 64 out.len 0 queue_id 1 [ 648.916184] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.916282] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.916386] virtio_fs_send_req: opcode 5 unique 0x461e nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.916559] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.916656] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.916756] virtio_fs_send_req: opcode 14 unique 0x4620 nodeid 0x30 in.len 48 out.len 16 queue_id 1 [ 648.916947] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.917045] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.917171] overlayfs: open(000000001dc27c49[lib64/libc.so.6/l], 0100000) -> (00000000065b2aff, 01100000) [ 648.917339] virtio_fs_send_req: opcode 25 unique 0x4622 nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.917498] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.917596] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.917710] virtio_fs_send_req: opcode 5 unique 0x4624 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.917901] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.917998] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.918105] virtio_fs_send_req: opcode 5 unique 0x4626 nodeid 0x1ed in.len 40 out.len 4095 queue_id 1 [ 648.918283] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.918380] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.918489] virtio_fs_send_req: opcode 14 unique 0x4628 nodeid 0x1ee in.len 48 out.len 16 queue_id 1 [ 648.918682] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.918780] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.918881] overlayfs: open(000000001dc27c49[lib64/libtinfo.so.6.5/l], 0100000) -> (0000000057c26190, 01100000) [ 648.919054] virtio_fs_send_req: opcode 25 unique 0x462a nodeid 0x1ee in.len 64 out.len 0 queue_id 1 [ 648.919219] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.919318] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.919997] virtio_fs_send_req: opcode 18 unique 0x462c nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.920159] virtio_fs_send_req: opcode 14 unique 0x462e nodeid 0x2a7 in.len 48 out.len 16 queue_id 1 [ 648.920169] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.920368] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.920492] overlayfs: open(000000001dc27c49[locale/locale-archive/l], 0100000) -> (00000000fce78bd3, 01100000) [ 648.920627] virtio_fs_send_req: opcode 25 unique 0x4630 nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.920772] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.920871] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.921036] virtio_fs_send_req: opcode 14 unique 0x4632 nodeid 0x2a9 in.len 48 out.len 16 queue_id 1 [ 648.921211] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.921308] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.921400] overlayfs: open(000000001dc27c49[gconv/gconv-modules.cache/l], 0100000) -> (00000000d54e120f, 01100000) [ 648.921523] virtio_fs_send_req: opcode 25 unique 0x4634 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.921666] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.921770] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.921832] virtqueue callback for 00000000531af360 (00000000df837aee) [ 648.922226] virtio_fs_send_req: opcode 18 unique 0x4636 nodeid 0x28 in.len 64 out.len 0 queue_id 1 [ 648.922326] virtio_fs_send_req: opcode 18 unique 0x4638 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.922400] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.922416] virtio_fs_send_req: opcode 18 unique 0x463a nodeid 0x2f5 in.len 64 out.len 0 queue_id 1 [ 648.922482] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.922564] virtio_fs_send_req: opcode 18 unique 0x463c nodeid 0x2f7 in.len 64 out.len 0 queue_id 1 [ 648.922690] virtio_fs_send_req: opcode 18 unique 0x463e nodeid 0x2f9 in.len 64 out.len 0 queue_id 1 [ 648.922762] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.922780] virtio_fs_send_req: opcode 18 unique 0x4640 nodeid 0x42 in.len 64 out.len 0 queue_id 1 [ 648.922847] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.922929] virtio_fs_send_req: opcode 18 unique 0x4642 nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.923060] virtio_fs_send_req: opcode 18 unique 0x4644 nodeid 0x1ee in.len 64 out.len 0 queue_id 1 [ 648.923126] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.923166] virtio_fs_send_req: opcode 18 unique 0x4646 nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.923228] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.923311] virtio_fs_send_req: opcode 18 unique 0x4648 nodeid 0x2f3 in.len 64 out.len 0 queue_id 1 [ 648.923487] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.923557] virtiofs virtio0: virtio_fs_vq_done requests.0 Delta-CAL (IPI): 6007 - this number is before the insert-sort, final number is better. [ 648.926990] virtio_fs_send_req: opcode 14 unique 0x464a nodeid 0xae in.len 48 out.len 16 queue_id 1 [ 648.927221] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.927312] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.927409] overlayfs: open(00000000ae2b3a37[/machine-id/l], 0100000) -> (00000000ebc0a9b2, 01100000) [ 648.927537] virtio_fs_send_req: opcode 25 unique 0x464c nodeid 0xae in.len 64 out.len 0 queue_id 1 [ 648.927709] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.927798] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.927888] virtio_fs_send_req: opcode 18 unique 0x464e nodeid 0xae in.len 64 out.len 0 queue_id 1 [ 648.928052] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.928135] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.928914] virtqueue callback for 00000000b8493952 (000000004941ab6e) [ 648.929008] virtio_fs_send_req: opcode 5 unique 0x4650 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.929175] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.929246] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.929318] virtio_fs_send_req: opcode 5 unique 0x4652 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.929467] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.929535] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.929604] virtio_fs_send_req: opcode 5 unique 0x4654 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.929751] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.929824] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.929899] virtio_fs_send_req: opcode 5 unique 0x4656 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.930043] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.930110] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.930188] virtio_fs_send_req: opcode 5 unique 0x4658 nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.930331] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.930399] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.930503] virtio_fs_send_req: opcode 5 unique 0x465a nodeid 0x23 in.len 40 out.len 4095 queue_id 1 [ 648.930648] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.930717] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.930795] virtio_fs_send_req: opcode 14 unique 0x465c nodeid 0x204 in.len 48 out.len 16 queue_id 1 [ 648.930976] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.931046] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.931132] overlayfs: open(00000000b23a5ecd[bin/sed/l], 0100040) -> (0000000074755de1, 01100040) [ 648.931288] virtio_fs_send_req: opcode 5 unique 0x465e nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.931448] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.931517] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.931600] virtio_fs_send_req: opcode 14 unique 0x4660 nodeid 0x28 in.len 48 out.len 16 queue_id 1 [ 648.931751] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.931826] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.931906] overlayfs: open(00000000fea37e0c[lib64/ld-linux-x86-64.so.2/l], 0100040) -> (00000000ebc0a9b2, 01100040) [ 648.932282] virtio_fs_send_req: opcode 14 unique 0x4662 nodeid 0x2b in.len 48 out.len 16 queue_id 1 [ 648.932437] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.932508] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.932593] overlayfs: open(00000000fea37e0c[/ld.so.cache/l], 0100000) -> (00000000a546e0ec, 01100000) [ 648.932710] virtio_fs_send_req: opcode 25 unique 0x4664 nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.932868] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.932945] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.933038] virtio_fs_send_req: opcode 5 unique 0x4666 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.933203] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.933285] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.933377] virtio_fs_send_req: opcode 5 unique 0x4668 nodeid 0x2c in.len 40 out.len 4095 queue_id 1 [ 648.933528] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.933606] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.933695] virtio_fs_send_req: opcode 14 unique 0x466a nodeid 0x2d in.len 48 out.len 16 queue_id 1 [ 648.933850] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.933924] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.934031] overlayfs: open(00000000fea37e0c[lib64/libacl.so.1.1.2302/l], 0100000) -> (000000003b97b39b, 01100000) [ 648.934194] virtio_fs_send_req: opcode 25 unique 0x466c nodeid 0x2d in.len 64 out.len 0 queue_id 1 [ 648.934349] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.934427] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.934513] virtio_fs_send_req: opcode 5 unique 0x466e nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.934668] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.934745] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.934835] virtio_fs_send_req: opcode 14 unique 0x4670 nodeid 0x41 in.len 48 out.len 16 queue_id 1 [ 648.934991] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.935069] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.935152] overlayfs: open(00000000fea37e0c[lib64/libselinux.so.1/l], 0100000) -> (00000000761f1272, 01100000) [ 648.935308] virtio_fs_send_req: opcode 25 unique 0x4672 nodeid 0x41 in.len 64 out.len 0 queue_id 1 [ 648.935462] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.935540] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.935650] virtio_fs_send_req: opcode 5 unique 0x4674 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.935800] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.935899] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.935994] virtio_fs_send_req: opcode 14 unique 0x4676 nodeid 0x30 in.len 48 out.len 16 queue_id 1 [ 648.936148] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.936226] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.936316] overlayfs: open(00000000fea37e0c[lib64/libc.so.6/l], 0100000) -> (0000000046b528d3, 01100000) [ 648.936448] virtio_fs_send_req: opcode 25 unique 0x4678 nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.936612] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.936691] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.936784] virtio_fs_send_req: opcode 5 unique 0x467a nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.936943] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.937022] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.937125] virtio_fs_send_req: opcode 5 unique 0x467c nodeid 0x43 in.len 40 out.len 4095 queue_id 1 [ 648.937274] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.937353] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.937447] virtio_fs_send_req: opcode 14 unique 0x467e nodeid 0x44 in.len 48 out.len 16 queue_id 1 [ 648.937604] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.937683] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.937769] overlayfs: open(00000000fea37e0c[lib64/libattr.so.1.1.2502/l], 0100000) -> (00000000ce7f73a3, 01100000) [ 648.937964] virtio_fs_send_req: opcode 25 unique 0x4680 nodeid 0x44 in.len 64 out.len 0 queue_id 1 [ 648.938148] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.938229] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.938329] virtio_fs_send_req: opcode 5 unique 0x4682 nodeid 0x26 in.len 40 out.len 4095 queue_id 1 [ 648.938499] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.938577] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.938669] virtio_fs_send_req: opcode 5 unique 0x4684 nodeid 0x4b in.len 40 out.len 4095 queue_id 1 [ 648.938831] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.938914] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.939013] virtio_fs_send_req: opcode 14 unique 0x4686 nodeid 0x4c in.len 48 out.len 16 queue_id 1 [ 648.939192] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.939272] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.939361] overlayfs: open(00000000fea37e0c[lib64/libpcre2-8.so.0.15.0/l], 0100000) -> (000000001b94a7b7, 01100000) [ 648.939502] virtio_fs_send_req: opcode 25 unique 0x4688 nodeid 0x4c in.len 64 out.len 0 queue_id 1 [ 648.939654] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.939734] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.940088] virtio_fs_send_req: opcode 18 unique 0x468a nodeid 0x2b in.len 64 out.len 0 queue_id 1 [ 648.940214] virtio_fs_send_req: opcode 1 unique 0x468c nodeid 0x1 in.len 48 out.len 128 queue_id 1 [ 648.940273] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.940394] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.940552] virtio_fs_send_req: opcode 14 unique 0x468e nodeid 0x2a7 in.len 48 out.len 16 queue_id 1 [ 648.940730] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.940819] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.940910] overlayfs: open(00000000fea37e0c[locale/locale-archive/l], 0100000) -> (00000000a546e0ec, 01100000) [ 648.941042] virtio_fs_send_req: opcode 25 unique 0x4690 nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.941215] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.941295] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.941413] virtio_fs_send_req: opcode 14 unique 0x4692 nodeid 0x2a9 in.len 48 out.len 16 queue_id 1 [ 648.941577] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.941654] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.941735] overlayfs: open(00000000fea37e0c[gconv/gconv-modules.cache/l], 0100000) -> (000000007d5f2653, 01100000) [ 648.941867] virtio_fs_send_req: opcode 25 unique 0x4694 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.942022] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.942105] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.942374] virtio_fs_send_req: opcode 18 unique 0x4696 nodeid 0x28 in.len 64 out.len 0 queue_id 1 [ 648.942487] virtio_fs_send_req: opcode 18 unique 0x4698 nodeid 0x2a9 in.len 64 out.len 0 queue_id 1 [ 648.942559] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.942599] virtio_fs_send_req: opcode 18 unique 0x469a nodeid 0x2d in.len 64 out.len 0 queue_id 1 [ 648.942660] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.942757] virtio_fs_send_req: opcode 18 unique 0x469c nodeid 0x41 in.len 64 out.len 0 queue_id 1 [ 648.942912] virtio_fs_send_req: opcode 18 unique 0x469e nodeid 0x30 in.len 64 out.len 0 queue_id 1 [ 648.942973] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.943020] virtio_fs_send_req: opcode 18 unique 0x46a0 nodeid 0x44 in.len 64 out.len 0 queue_id 1 [ 648.943084] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.943247] virtio_fs_send_req: opcode 18 unique 0x46a2 nodeid 0x4c in.len 64 out.len 0 queue_id 1 [ 648.943318] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.943353] virtio_fs_send_req: opcode 18 unique 0x46a4 nodeid 0x2a7 in.len 64 out.len 0 queue_id 1 [ 648.943417] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.943514] virtio_fs_send_req: opcode 18 unique 0x46a6 nodeid 0x204 in.len 64 out.len 0 queue_id 1 [ 648.943698] virtqueue callback for 00000000ffb9412a (00000000c5ce06f7) [ 648.943776] virtiofs virtio0: virtio_fs_vq_done requests.0 [ 648.948394] uart_wait_until_sent(0), jiffies=4295316070, expire=4295316142... root@drm-misc-fixes-2026-02-26-80-g9a2f253ad689:/home/jimc/projects/lx/wk-D/b0-dd# --- drivers/virtio/virtio_ring.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 335692d41617..99f9e547d264 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@ -759,7 +759,7 @@ static inline int virtqueue_add_split(struct vring_virtqueue *vq, vq->split.avail_idx_shadow); vq->num_added++; - pr_debug("Added buffer head %i to %p\n", head, vq); + pr_debug_ratelimited("Added buffer head %i to %p\n", head, vq); END_USE(vq); /* This is very unlikely, but theoretically possible. Kick @@ -930,7 +930,7 @@ static void *virtqueue_get_buf_ctx_split(struct vring_virtqueue *vq, } if (!more_used_split(vq)) { - pr_debug("No more buffers in queue\n"); + pr_debug_ratelimited("No more buffers in queue\n"); END_USE(vq); return NULL; } @@ -1595,7 +1595,7 @@ static int virtqueue_add_indirect_packed(struct vring_virtqueue *vq, vq->num_added += 1; - pr_debug("Added buffer head %i to %p\n", head, vq); + pr_debug_ratelimited("Added buffer head %i to %p\n", head, vq); END_USE(vq); return 0; @@ -1744,7 +1744,7 @@ static inline int virtqueue_add_packed(struct vring_virtqueue *vq, vq->packed.vring.desc[head].flags = head_flags; vq->num_added += descs_used; - pr_debug("Added buffer head %i to %p\n", head, vq); + pr_debug_ratelimited("Added buffer head %i to %p\n", head, vq); END_USE(vq); return 0; @@ -1902,7 +1902,7 @@ static inline int virtqueue_add_packed_in_order(struct vring_virtqueue *vq, vq->packed.vring.desc[head].flags = head_flags; vq->num_added += total_sg; - pr_debug("Added buffer head %i to %p\n", head, vq); + pr_debug_ratelimited("Added buffer head %i to %p\n", head, vq); END_USE(vq); return 0; @@ -3231,7 +3231,7 @@ irqreturn_t vring_interrupt(int irq, void *_vq) struct vring_virtqueue *vq = to_vvq(_vq); if (!more_used(vq)) { - pr_debug("virtqueue interrupt with no work for %p\n", vq); + pr_debug_ratelimited("virtqueue interrupt with no work for %p\n", vq); return IRQ_NONE; } -- 2.53.0

4 months, 1 week

Best cryptocurrency companies

by ruthdressler567＠gmail.com

This experience strengthened me and taught me more about security than any success ever could. If you find yourself in similar situation , i'm here to tell you that there is a way out. you can also recovery your stollen bitcoin like i did.

4 months, 1 week

[PATCH v2 0/6] dma-buf: heaps: add coherent reserved-memory heap

by Albert Esteve

This patch introduces a new heap driver to expose DT non‑reusable "shared-dma-pool" coherent regions as dma-buf heaps, so userspace can allocate buffers from each reserved, named region. Because these regions are device‑dependent, each heap instance binds a heap device to its reserved‑mem region via a newly introduced helper function -namely, of_reserved_mem_device_init_with_mem()- so coherent allocations use the correct dev->dma_mem. Charging to cgroups for these buffers is intentionally left out to keep review focused on the new heap; I plan to follow up based on Eric’s [1] and Maxime’s [2] work on dmem charging from userspace. This series also makes the new heap driver modular, in line with the CMA heap change in [3]. [1] https://lore.kernel.org/all/20260218-dmabuf-heap-cma-dmem-v2-0-b249886fb7b2… [2] https://lore.kernel.org/all/20250310-dmem-cgroups-v1-0-2984c1bc9312@kernel.… [3] https://lore.kernel.org/all/20260303-dma-buf-heaps-as-modules-v3-0-24344812… Signed-off-by: Albert Esteve <aesteve(a)redhat.com> --- Changes in v2: - Removed dmem charging parts - Moved coherent heap registering logic to coherent.c - Made heap device a member of struct dma_heap - Split dma_heap_add logic into create/register, to be able to access the stored heap device before registered. - Avoid platform device in favour of heap device - Added a wrapper to rmem device_init() op - Switched from late_initcall() to module_init() - Made the coherent heap driver modular - Link to v1: https://lore.kernel.org/r/20260224-b4-dmabuf-heap-coherent-rmem-v1-1-dffef4… --- Albert Esteve (5): dma-buf: dma-heap: split dma_heap_add of_reserved_mem: add a helper for rmem device_init op dma-buf: heaps: Add Coherent heap to dmabuf heaps dma: coherent: register to coherent heap dma-buf: heaps: coherent: Turn heap into a module John Stultz (1): dma-buf: dma-heap: Keep track of the heap device struct drivers/dma-buf/dma-heap.c | 138 +++++++++-- drivers/dma-buf/heaps/Kconfig | 9 + drivers/dma-buf/heaps/Makefile | 1 + drivers/dma-buf/heaps/coherent_heap.c | 429 ++++++++++++++++++++++++++++++++++ drivers/of/of_reserved_mem.c | 27 ++- include/linux/dma-heap.h | 16 ++ include/linux/dma-map-ops.h | 7 + include/linux/of_reserved_mem.h | 8 + kernel/dma/coherent.c | 34 +++ 9 files changed, 642 insertions(+), 27 deletions(-) --- base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f change-id: 20260223-b4-dmabuf-heap-coherent-rmem-91fd3926afe9 Best regards, -- Albert Esteve <aesteve(a)redhat.com>

4 months, 1 week

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig March 2026