From: Cong Wang <xiyou.wangcong@gmail.com>
To: Dileep Sankhla <dileepsankhla.ds@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: seeking beginner-friendly mm bugs to work on
Date: Sun, 18 May 2025 19:27:04 -0700 [thread overview]
Message-ID: <CAM_iQpU3VHANZwpoEZ9VUX5qm44-mfiWNmy=YwqbN8A4x9f1SQ@mail.gmail.com> (raw)
In-Reply-To: <CAHxc4bshhM4p8o21KhTbZT3uM+F7JdhNJ7DPxMUhiDq7_xnaqw@mail.gmail.com>
Hi Dileep,
On Sat, May 17, 2025 at 3:27 AM Dileep Sankhla
<dileepsankhla.ds@gmail.com> 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?
There are many bugs reported by the syzkaller fuzzer here:
https://syzkaller.appspot.com/upstream/s/mm
Those with C reproducers are usually easier to fix, although it is not
always the case, at least they are good starters, IMHO.
Hope this helps.
Regards,
Cong Wang
next prev parent reply other threads:[~2025-05-19 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 10:31 Dileep Sankhla
2025-05-17 10:49 ` Harry Yoo
2025-05-17 15:14 ` Dileep Sankhla
2025-05-19 2:27 ` Cong Wang [this message]
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='CAM_iQpU3VHANZwpoEZ9VUX5qm44-mfiWNmy=YwqbN8A4x9f1SQ@mail.gmail.com' \
--to=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox