From: Harry Yoo <harry.yoo@oracle.com>
To: Dileep Sankhla <dileepsankhla.ds@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: seeking beginner-friendly mm bugs to work on
Date: Sat, 17 May 2025 19:49:53 +0900 [thread overview]
Message-ID: <aChp0TMlyXUj4rqp@harry> (raw)
In-Reply-To: <CAHxc4bshhM4p8o21KhTbZT3uM+F7JdhNJ7DPxMUhiDq7_xnaqw@mail.gmail.com>
On Sat, May 17, 2025 at 04:01:51PM +0530, Dileep Sankhla wrote:
> Hello everyone,
>
> Thank you all for improving, enhancing, and maintaining the memory
> management subsystem.
>
> I am new to Linux kernel development. Until now, I have only one
> contribution that fixes the checkpatch.pl warning. I have also
> attempted to create my own 64-bit Unix-like kernel from scratch for
> x86-64 PCs. I worked on implementing a physical memory manager and I
> also experimented with 64-bit paging.
>
> I want to begin solving a few beginner-friendly bugs. I searched
> bugzilla but I don't know which ones are for beginners like me. Could
> you guys help me in seeking bugs to work on?
Hi, Dileep.
I don't think we keep a list of newcomer-friendly bug—instead, we fix them
as they appear.
However, if you want to discover MM bugs, I believe the most effective
way to find them is to extensively test mm-new [1] branch each week.
I’ve discovered and fixed several bugs that way, and the community values
this kind of testing.
[1] https://web.git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/log/?h=mm-new
Once you're comfortable testing mm-new and discovering bugs, you may
want to start reviewing new patches as well; New code often introduces
bugs, and some issues can pass testing but become obvious (and get caught)
during code review.
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2025-05-17 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 10:31 seeking beginner-friendly mm bugs to work on Dileep Sankhla
2025-05-17 10:49 ` Harry Yoo [this message]
2025-05-17 15:14 ` Dileep Sankhla
2025-05-19 2:27 ` Cong Wang
2025-05-19 3:09 ` Dileep Sankhla
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=aChp0TMlyXUj4rqp@harry \
--to=harry.yoo@oracle.com \
--cc=dileepsankhla.ds@gmail.com \
--cc=linux-mm@kvack.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.