Project Description

Due previous hackweek (https://hackweek.opensuse.org/projects/test-mainline-kernel-on-an-older-qualcomm-soc-msm89xx-explore-mainline-kernel-qualcomm-mainlining) both msm8994 angler and msm8992 bullhead are booting and due other activity (including my work) both have working SD card, but that's just start. Add support for other functionality.

Goal for this Hackweek

There are still some memory issues for bullhead (SMEM, invalid patch: https://lore.kernel.org/linux-arm-msm/20230128055214.33648-1-jamiemdouglass@gmail.com/), fix them.
Regulators support for angler (basic for other functionality)
USB support for both angler and bullhead
Haptics support (https://wiki.postmarketos.org/wiki/Haptics)
Document on

Resources

https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git
https://wiki.postmarketos.org/wiki/Qualcomm_Glossary
https://wiki.postmarketos.org/wiki/Mainlining
https://wiki.postmarketos.org/wiki/Mainlining_Guide

Result

[RFC PATCH 1/1] arm64: dts: qcom: msm8994-huawei-angler: Add regulators (TODO, based on my previous work in my free time)
[PATCH 1/1] arm64: dts: qcom: msm8992-lg-bullhead: Enable regulators => merged in v6.3-rc1 as 2866527093dd ("arm64: dts: qcom: msm8992-lg-bullhead: Enable regulators")
[PATCH 1/2] arm64: dts: msm8994-angler: Fix cont_splash_mem mapping => merged into qcom/for-next (will be in v6.4) as fe88480a6be9 ("arm64: dts: qcom: msm8994-angler: Fix cont_splash_mem mapping")
[PATCH 2/2] arm64: dts: msm8994-angler: removed clash with smem_region => merged into qcom/for-next (will be in v6.4) as c85c8a992794 ("arm64: dts: qcom: msm8994-angler: removed clash with smem_region")
[PATCH 1/1] arm64: defconfig: Enable qcom msm8994 clk drivers (TODO), => later v2, which was merged as 8f680c287445 ("arm64: defconfig: Switch msm8996 clk drivers to module") and 8f680c287445 ("arm64: defconfig: Switch msm8996 clk drivers to module")

Join this project Leave this project

Looking for hackers with the skills:

kernel aarch64 mainlining soc qualcomm linux

This project is part of:

Hack Week 22 Hack Week 23

Activity

almost 2 years ago: iivanov liked this project.

almost 2 years ago: clin liked this project.

almost 2 years ago: pvorel started this project.

almost 2 years ago: dmdiss liked this project.

almost 2 years ago: pvorel added keyword "kernel" to this project.

almost 2 years ago: pvorel added keyword "aarch64" to this project.

almost 2 years ago: pvorel added keyword "mainlining" to this project.

almost 2 years ago: pvorel added keyword "soc" to this project.

almost 2 years ago: pvorel added keyword "qualcomm" to this project.

almost 2 years ago: pvorel added keyword "linux" to this project.

almost 2 years ago: pvorel originated this project.

Comments

Be the first to comment!

Similar Projects

kernel

Create a DRM driver for VGA video cards by tdz

Yes, those VGA video cards. The goal of this project is to implement a DRM graphics driver for such devices. While actual hardware is hard to obtain or even run today, qemu emulates VGA output.

VGA has a number of limitations, which make this project interesting.

There are only 640x480 pixels (or less) on the screen. That resolution is also a soft lower limit imposed by DRM. It's mostly a problem for desktop environments though.
Desktop environments assume 16 million colors, but there are only 16 colors with VGA. VGA's 256 color palette is not available at 640x480. We can choose those 16 colors freely. The interesting part is how to choose them. We have to build a palette for the displayed frame and map each color to one of the palette's 16 entries. This is called dithering, and VGA's limitations are a good opportunity to learn about dithering algorithms.
VGA has an interesting memory layout. Most graphics devices use linear framebuffers, which store the pixels byte by byte. VGA uses 4 bitplanes instead. Plane 0 holds all bits 0 of all pixels. Plane 1 holds all bits 1 of all pixels, and so on.

The driver will probably not be useful to many people. But, if finished, it can serve as test environment for low-level hardware. There's some interest in supporting old Amiga and Atari framebuffers in DRM. Those systems have similar limitations as VGA, but are harder to obtain and test with. With qemu, the VGA driver could fill this gap.

Apart from the Wikipedia entry, good resources on VGA are at osdev.net and FreeVGA

Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

Result

In the end I concentrated again to msm8994:

FizzBuzz OS by mssola

Project Description

FizzBuzz OS (or just fbos) is an idea I've had in order to better grasp the fundamentals of the low level of a RISC-V machine. In practice, I'd like to build a small Operating System kernel that is able to launch three processes: one that simply prints "Fizz", another that prints "Buzz", and the third which prints "FizzBuzz". These processes are unaware of each other and it's up to the kernel to schedule them by using the timer interrupts as given on openSBI (fizz on % 3 seconds, buzz on % 5 seconds, and fizzbuzz on % 15 seconds).

This kernel provides just one system call, write, which allows any program to pass the string to be written into stdout.

This project is free software and you can find it here.

Goal for this Hackweek

Better understand the RISC-V SBI interface.
Better understand RISC-V in privileged mode.
Have fun.

Resources

Results

The project was a resounding success Lots of learning, and the initial target was met.

Contributing to Linux Kernel security by pperego

Description

A couple of weeks ago, I found this blog post by Gustavo Silva, a Linux Kernel contributor.

I always strived to start again into hacking the Linux Kernel, so I asked Coverity scan dashboard access and I want to contribute to Linux Kernel by fixing some minor issues.

I want also to create a Linux Kernel fuzzing lab using qemu and syzkaller

Goals

Fix at least 2 security bugs
Create the fuzzing lab and having it running

The story so far

Day 1: setting up a virtual machine for kernel development using Tumbleweed. Reading a lot of documentation, taking confidence with Coverity dashboard and with procedures to submit a kernel patch
Day 2: I read really a lot of documentation and I triaged some findings on Coverity SAST dashboard. I have to confirm that SAST tool are great false positives generator, even for low hanging fruits.
Day 3: Working on trivial changes after I read this blog post: https://www.toblux.com/posts/2024/02/linux-kernel-patches.html. I have to take confidence with the patch preparation and submit process yet.
- First trivial patch sent: using strtruefalse() macro instead of hard-coded strings in a staging driver for a lcd display
- Fix for a dereference before null check issue discovered by Coverity (CID 1601566) https://scan7.scan.coverity.com/#/project-view/52110/11354?selectedIssue=1601566
Day 4: Triaging more issues found by Coverity.
- The patch for CID 1601566 was refused. The check against the NULL pointer was pointless so I prepared a version 2 of the patch removing the check.
- Fixed another dereference before NULL check in iwlmvmparsewowlaninfo_notif() routine (CID 1601547). This one was already submitted by another kernel hacker :(
Day 5: Wrapping up. I had to do some minor rework on patch for CID 1601566. I found a stalker bothering me in private emails and people I interacted with me, advised he is a well known bothering person. Markus Elfring for the record.
Wrapping up: being back doing kernel hacking is amazing and I don't want to stop it. My battery pack is completely drained but changing the scope gave me a great twist and I really want to feel this energy not doing a single task for months.

I failed in setting up a fuzzing lab but I was too optimistic for the patch submission process.

The patches

Create DRM drivers for VESA and EFI framebuffers by tdz

Description

We already have simpledrm for firmware framebuffers. But the driver is originally for ARM boards, not PCs. It is already overloaded with code to support both use cases. At the same time it is missing possible features for VESA and EFI, such as palette modes or EDID support. We should have DRM drivers for VESA and EFI interfaces. The infrastructure exists already and initial drivers can be forked from simpledrm.

Goals

Initially, a bare driver for VESA or EFI should be created. It can take functionality from simpledrm.
Then we can begin to add additional features. The boot loader can provide EDID data. With VGA hardware, VESA can support paletted modes or color management. Example code exists in vesafb.

aarch64

Investigate non-booting Forlinx OKMX8MX-C board (aarch64) by a_faerber

Description

In the context of a SUSE customer inquiry last year, a Forlinx OKMX8MX-C arm64 board had been relayed to me from China that a customer was not successful booting SUSE Linux Micro on. Typically this happens when the vendor's bootloader (e.g., U-Boot) is not configured properly (e.g., U-Boot's distro boot) to be compliant with Arm SystemReady Devicetree (formerly IR) band. Unfortunately I could not immediately get it to emit any output, to even diagnose why it wasn't working. There was no public documentation on the vendor's website to even confirm I was checking the right UARTs.

Earlier this year (2024) I happened to meet the ODM/OEM, Forlinx, at Embedded World 2024 in Nuremberg and again the Monday before Hackweek 24 at Electronica 2024 in Munich. The big puzzle was that the PCB print "OKMX8MX-C" does not match any current Forlinx product, there being OKMX8MM-C and OKMX8MP-C products with the Mini and Plus variants of NXP i.MX 8M family instead. One suggestion from Forlinx staff was to double-check the DIP switches on the board for boot mode selection.

Goals

Double-check the board name and investigate further what may be wrong with this board.

Resources

none

Progress

The board name is indeed as spelled above, not matching any product on forlinx.net.
The DIP switches were set to boot from microSD.
Changing the DIP switches to eMMC boot did result in UART1 RS-232 output! (although at times garbled with the cable supplied and USB adapter used)
As feared, it did not automatically load our GRUB from USB.
Booting our GRUB manually from USB (via eMMC U-Boot commands fatload+bootefi) was unsuccessful, with partially Chinese error messages.
This confirmed the initial suspicion, already shared with Forlinx at Embedded World 2024, that the Forlinx System-on-Module's boot firmware was not Arm SystemReady Devicetree compliant and that a firmware update would be necessary to remedy that.
The microSD card turned out not to contain a bootable image but to only include Chinese-language board documentation (dated 20220507) and BSP files. They used a diverging name of OKMX8MQ-C.

Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

Result

In the end I concentrated again to msm8994:

mainlining

Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

Result

In the end I concentrated again to msm8994:

soc

Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

Result

In the end I concentrated again to msm8994:

qualcomm

Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

Result

In the end I concentrated again to msm8994:

linux

VulnHeap by r1chard-lyu

Description

The VulnHeap project is dedicated to the in-depth analysis and exploitation of vulnerabilities within heap memory management. It focuses on understanding the intricate workflow of heap allocation, chunk structures, and bin management, which are essential to identifying and mitigating security risks.

Goals

Familiarize with heap
- Heap workflow
- Chunk and bin structure
- Vulnerabilities
Vulnerability
- Use after free (UAF)
- Heap overflow
- Double free
Use Docker to create a vulnerable environment and apply techniques to exploit it

Resources

https://heap-exploitation.dhavalkapil.com/divingintoglibc_heap
https://raw.githubusercontent.com/cloudburst/libheap/master/heap.png
https://github.com/shellphish/how2heap?tab=readme-ov-file

toptop - a top clone written in Go by dshah

Description

toptop is a clone of Linux's top CLI tool, but written in Go.

Goals

Learn more about Go (mainly bubbletea) and Linux

Resources

GitHub

Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
Package management (install, remove, update...)
Patching
Applying any basic salt state (including a formula)
Salt remote commands
Bonus point: Java part for product identification, and monitoring enablement
Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

If you don't have knowledge about some of the steps: ask the team
If you still don't know what to do: switch to another distribution and keep testing.

This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

Pending

FUSS

FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

https://fuss.bz.it/

Seems to be a Debian 12 derivative, so adding it could be quite easy.

[W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
[W] Onboarding (salt minion from UI, salt minion from bootstrap script, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Working for all 3 options (salt minion UI, salt minion bootstrap script and salt-ssh minion from the UI).
[W] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
[I] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already). No patches detected. Do we support patches for Debian at all?
[W] Applying any basic salt state (including a formula)
[W] Salt remote commands
[ ] Bonus point: Java part for product identification, and monitoring enablement

Contributing to Linux Kernel security by pperego

Description

A couple of weeks ago, I found this blog post by Gustavo Silva, a Linux Kernel contributor.

I always strived to start again into hacking the Linux Kernel, so I asked Coverity scan dashboard access and I want to contribute to Linux Kernel by fixing some minor issues.

I want also to create a Linux Kernel fuzzing lab using qemu and syzkaller

Goals

Fix at least 2 security bugs
Create the fuzzing lab and having it running

The story so far

Day 1: setting up a virtual machine for kernel development using Tumbleweed. Reading a lot of documentation, taking confidence with Coverity dashboard and with procedures to submit a kernel patch
Day 2: I read really a lot of documentation and I triaged some findings on Coverity SAST dashboard. I have to confirm that SAST tool are great false positives generator, even for low hanging fruits.
Day 3: Working on trivial changes after I read this blog post: https://www.toblux.com/posts/2024/02/linux-kernel-patches.html. I have to take confidence with the patch preparation and submit process yet.
- First trivial patch sent: using strtruefalse() macro instead of hard-coded strings in a staging driver for a lcd display
- Fix for a dereference before null check issue discovered by Coverity (CID 1601566) https://scan7.scan.coverity.com/#/project-view/52110/11354?selectedIssue=1601566
Day 4: Triaging more issues found by Coverity.
- The patch for CID 1601566 was refused. The check against the NULL pointer was pointless so I prepared a version 2 of the patch removing the check.
- Fixed another dereference before NULL check in iwlmvmparsewowlaninfo_notif() routine (CID 1601547). This one was already submitted by another kernel hacker :(
Day 5: Wrapping up. I had to do some minor rework on patch for CID 1601566. I found a stalker bothering me in private emails and people I interacted with me, advised he is a well known bothering person. Markus Elfring for the record.
Wrapping up: being back doing kernel hacking is amazing and I don't want to stop it. My battery pack is completely drained but changing the scope gave me a great twist and I really want to feel this energy not doing a single task for months.

I failed in setting up a fuzzing lab but I was too optimistic for the patch submission process.

The patches

Explore simple and distro indipendent declarative Linux starting on Tumbleweed or Arch Linux by janvhs

Description

Inspired by mkosi the idea is to experiment with a declarative approach of defining Linux systems. A lot of tools already make it possible to manage the systems infrastructure by using description files, rather than manual invocation. An example for this are systemd presets for managing enabled services or the /etc/fstab file for describing how partitions should be mounted.

If we would take inspiration from openSUSE MicroOS and their handling of the /etc/ directory, we could theoretically use systemd-sysupdate to swap out the /usr/ partition and create an A/B boot scheme, where the /usr/ partition is always freshly built according to a central system description. In the best case it would be possible to still utilise snapshots, but an A/B root scheme would be sufficient for the beginning. This way you could get the benefit of NixOS's declarative system definition, but still use the distros package repositories and don't have to deal with the overhead of Flakes or the Nix language.

Goals

A simple and understandable system
Check fitness of mkosi or write a simple extensible image builder tool for it
Create a declarative system specification
Create a system with swappable /usr/ partition
Create an A/B root scheme
Swap to the new system without reboot (kexec?)

Resources

Ideas that have been floating around in my head for a while
https://0pointer.net/blog/fitting-everything-together.html
GNOME OS
MicroOS
systemd mkosi
Vanilla OS