Pull to refresh
Logo
ELISA adds Cregit and stress-ng to Linux safety-critical software ecosystem

ELISA adds Cregit and stress-ng to Linux safety-critical software ecosystem

New Capabilities

Code analysis and stress testing tools join the open source toolkit for certifying Linux-based safety systems

Yesterday: ELISA adds Cregit and stress-ng to ecosystem

Overview

Updated 34 minutes ago

Linux now runs in cars, planes, and factory equipment where a software failure can be fatal, and every one of those systems needs documented proof of reliability before regulators approve it. The ELISA (Enabling Linux In Safety Applications) Fund, a Linux Foundation project, added two open-source tools on October 5 at Open Source Summit Europe in Prague to help developers build that proof.

Cregit traces the history of Linux kernel code at the level of individual tokens, so engineers can see who introduced a change and how it evolved. stress-ng runs more than 390 stress tests that push system components to their limits to expose reliability problems. Both join an ecosystem of shared tools, methods, and documentation for safety-critical Linux development, though neither tool certifies a system on its own, that responsibility stays with each company.

Why it matters

Safety-certified Linux systems in cars, aircraft, and factories need documented evidence of reliability; these tools help developers assemble that evidence.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

2
New projects added to ELISA ecosystem
Cregit for code history analysis and stress-ng for system stress testing joined the umbrella in October 2026.
390+
Stress tests in stress-ng
Configurable workloads that push Linux subsystems and kernel interfaces to expose behavior under pressure.
95%
Cregit's token-level blame accuracy
Compared to 70–80% for git's line-based blame, measured in empirical evaluation of mature software systems.
5
Founding corporate members
Arm, BMW Car IT, KUKA, Linutronix, and Toyota launched ELISA in 2019.

Voices

Curated perspectives — historical figures and your fellow readers.

Ever wondered what historical figures would say about today's headlines?

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

2019 October 2026

4 events Latest: Yesterday
Tap a bar to jump to that date
  1. ELISA adds Cregit and stress-ng to ecosystem

    Latest Announcement

    The Linux Foundation project expanded its ecosystem with two tools covering code analysis and system reliability testing, announced at Open Source Summit Europe in Prague.

  2. Safe Systems with Linux microconference begins

    Conference

    ELISA helps lead a microconference at Linux Plumbers Conference in Prague on requirements traceability, testing, and documentation in the Linux kernel.

  3. Cregit introduced in ELISA seminar series

    Presentation

    Daniel German presented Cregit's token-level code history approach to address git blame's line-level limitation.

  4. ELISA founded by five corporate members

    Founding

    Arm, BMW Car IT, KUKA, Linutronix, and Toyota launched the project to make Linux-based safety certification more practical.

Scenarios

1

Safety case studies cite Cregit and stress-ng in certification work

Possible Resolves by Oct 5, 2027

Discussed by: The ELISA announcement's framing, which positions the tools as strengthening the ecosystem across the software lifecycle

Companies in automotive, aerospace, or industrial sectors integrate Cregit for code provenance analysis and stress-ng for reliability testing into their safety assessment workflows. The tools appear in published case studies and certification guides as documented evidence sources. Adoption would show that the ELISA ecosystem is becoming a practical resource for companies preparing Linux-based systems for certification.

2

Linux kernel development adopts stress-ng and Cregit as standard tools

Possible Resolves by Oct 5, 2027

Discussed by: ELISA community members presenting at Open Source Summit Europe and Linux Plumbers Conference

Kernel maintainers and developers begin using stress-ng in routine testing of kernel subsystems, and Cregit for understanding code provenance during review. The tools get referenced in kernel documentation or recommended in major distributions' testing guidance. This outcome would mean the tools influence upstream development, not just certification workflows.

3

Cregit and stress-ng stay niche within the ELISA community

Possible Resolves by Oct 5, 2027

Discussed by: RuntimeWire's analysis, which notes that tool access alone does not certify a Linux-based system and warns the practical test is whether developers connect tools to repeatable evidence

The tools remain useful within the ELISA community but do not gain broad adoption across regulated industries or upstream kernel development. Companies continue using proprietary or in-house tools for safety analysis, and the new projects' impact stays limited to the existing ELISA member base. This outcome would mean the announcement expanded the option set without changing industry practice.

Historical Context

2 moments from history that rhyme with this story — and how they unfolded.

circa 2004 – November 2024

PREEMPT_RT real-time Linux development (early 2000s–2024)

Ingo Molnar and a community of developers built PREEMPT_RT patches to give Linux real-time response guarantees, a hard requirement for industrial and automotive safety systems. The patches developed in parallel with the mainline kernel for nearly two decades.

Then

The work merged into the mainline kernel with Linux 6.12 in November 2024, making real-time capabilities standard Linux rather than a separate fork.

Now

It demonstrated that safety-critical requirements can be integrated into open source through sustained community effort, setting a precedent for how safety needs get upstreamed.

Why this matters now

Like PREEMPT_RT, Cregit and stress-ng address safety-critical needs as open-source projects. Their success depends on the same dynamic: whether the broader community adopts and integrates them.

2000–2003

SELinux security extension (2000–2003)

The National Security Agency released Security-Enhanced Linux in 2000 as patches providing mandatory access control, a security feature absent from standard Linux. The patches required community refinement and development before they were ready for mainline inclusion.

Then

SELinux merged into Linux 2.6 in 2003 and became a standard security feature in major distributions.

Now

It showed how a critical-safety feature developed outside the mainline could become standard Linux infrastructure through community collaboration.

Why this matters now

SELinux's path from external patches to standard feature mirrors the question facing Cregit and stress-ng: whether safety-focused open-source tools can gain enough community traction to become standard practice.

Sources

(7)