From: Miguel Miranda <mmikernel@gmail.com>
To: RT <linux-rt-users@vger.kernel.org>
Subject: Seeking input on beginner-level bugs related to preempt_RT
Date: Fri, 12 Apr 2024 17:00:39 -0600 [thread overview]
Message-ID: <27cfdcdc-f0d0-42ae-9b53-937828a4fd7d@gmail.com> (raw)
Hello everyone,
I am currently looking for beginner-level bugs related to preempt_RT for
the Linux kernel Bug Fixing Spring Unpaid 2024. Although I am not an
expert in RT, I have been trying to identify some bugs and our mentors
have suggested using ring testers such as syzkaller and test frameworks
like kernelselftests to find and reproduce these bugs on our own.
I have a few questions and would appreciate any input you may have.
Firstly, is there a specific CI ring or channel that lists KTODOs, or a
preferred platform where bugs related to PREEMPT_RT are reported?
Secondly, I have been following the LKML and have seen some
console_blast.sh results, but I am not sure where to find this
console_blast. Lastly, I have come across some recent discussions about
printk() related work, but I'm unsure if there is a list to avoid rework.
Thank you for your time.
next reply other threads:[~2024-04-12 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 23:00 Miguel Miranda [this message]
2024-04-17 17:42 ` Seeking input on beginner-level bugs related to preempt_RT John B. Wyatt IV
2024-04-29 9:45 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27cfdcdc-f0d0-42ae-9b53-937828a4fd7d@gmail.com \
--to=mmikernel@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.