Linux Kernel Mentees list
 help / color / mirror / Atom feed
From: Kurt Manucredo <fuzzybritches0@gmail.com>
To: esmethedev@gmail.com,
	linux-kernel-mentees@lists.linuxfoundation.org,
	syzkaller@googlegroups.com
Subject: Starting a Wiki for Syzkaller Bug Fixing Resources
Date: Wed, 28 Apr 2021 15:13:14 +0200	[thread overview]
Message-ID: <5705-18963-curtm@phaethon> (raw)
In-Reply-To: <e486aee7-993c-e50f-f14f-aac7f701b752@gmail.com>


On  Wed, 28 Apr 2021 04:50:18 +0800  Esme Xuan Lim <esmethedev@gmail.com> wrote:
> 
> Hi there,
> 
> Having been on the bug fixing mentorship, I've been collating a bunch of
> resources that helped me as I was going. I've been thinking that there
> might be a big gap in resources in where interns might be looking and
> was keen on trying to put one together. Given the current conversation
> Greg has brought up about syzkaller bugs needing more attention, I
> figured this could help fix it if interns are the only ones available
> for this task.
> 
> I think it'd help the kernel mentees current and future sink their teeth
> quicker into fixing bugs, and less into helping themselves learn what is
> needed. This appears to be a big gap that would really help if it were
> filled. Resources are heavily abundant for the Linux kernel, but a good
> level of curation and maintained resources could help with bug fixing.
> Resources look old, but are incredibly insightful. I would have skipped
> looking at these resources given my experience with more modern
> frameworks and toolkits (which is that it would be best to avoid
> outdated ones as APIs change very quickly - but this is not the case
> with the kernel)
> 
> I've got links and things but I've been wondering if it made sense to
> build on the Kernel Mentees or to build a wiki (and host it) on
> something more modern like github.
> 
> I'd love to hear suggestions for how best to go about this, and if
> anyone would like to contribute to it too.
> 
I would love to contribute. I've started my blog on:

https://fuzzybritches0.github.io/

If any of these entries I made are helpful, I'd love to help you
incorporate them into your wiki. I'd also love to get feedback on these
entries. Count me in.

thanks and kind regards

Kurt Manucredo

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  parent reply	other threads:[~2021-04-28 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 20:50 Starting a Wiki for Syzkaller Bug Fixing Resources Esme Xuan Lim
2021-04-28  5:42 ` Dmitry Vyukov via Linux-kernel-mentees
2021-04-28 13:13 ` Kurt Manucredo [this message]
2021-04-28 13:55   ` Esme Xuan Lim
2021-04-28 14:15     ` Kurt Manucredo

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=5705-18963-curtm@phaethon \
    --to=fuzzybritches0@gmail.com \
    --cc=esmethedev@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=syzkaller@googlegroups.com \
    /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