Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Dileep Sankhla <dileepsankhla.ds@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Identifying the initial bug within the x86 architecture subsystem
Date: Wed, 3 Jan 2024 11:12:57 +0530	[thread overview]
Message-ID: <CAHxc4bugoJuw=JwkrsWYphip8bkuQwJUtt4ipR3PwdxxY-JO_g@mail.gmail.com> (raw)

Hello,

I am new to Linux kernel development and have a keen interest in the
x86 architecture subsystem, particularly in the areas of boot and
feature flags. Before diving into adding or changing features, I would
like to address a few existing bugs. I am good in C and have some
knowledge of assembly language.

Last night, I dedicated time to go through bugs on Bugzilla (see [1]),
considering their priorities but I could not figure out which one to
pick. While I found only a couple of bugs with the latest modification
date, I lack the same hardware as the original poster (OP) to
reproduce and fix those bugs. How can I identify the first bug in this
subsystem? Given the relatively low number of bugs, should I consider
reaching out to the maintainer of `arch/x86/boot` if I cannot find a
suitable one to fix?

P.S. I have one commit in the kernel from 2018 (see [2]) , but it was
merely addressing a `checkpatch.pl` warning.

Regards,
Dileep

[1]: https://bugzilla.kernel.org/buglist.cgi?bug_severity=blocking&bug_severity=high&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=i386&component=x86-64&descending=on&longdesc=boot%2Cfeature%20flags&longdesc_type=anywordssubstr&order=changeddate%20DESC%2Cpriority%20DESC%2Cbug_severity&priority=P1&priority=P2&priority=P3&product=Platform%20Specific%2FHardware&query_format=advanced&rep_platform=Intel&rep_platform=i386&rep_platform=x86-64

[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b79f3f68cc306637b88072804396685dc037c779

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2024-01-03  5:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  5:42 Dileep Sankhla [this message]
2024-01-03  7:03 ` Identifying the initial bug within the x86 architecture subsystem Greg KH
2024-01-03  9:53   ` Dileep Sankhla
2024-01-03  9:58     ` Greg KH
2024-01-03 10:08       ` 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='CAHxc4bugoJuw=JwkrsWYphip8bkuQwJUtt4ipR3PwdxxY-JO_g@mail.gmail.com' \
    --to=dileepsankhla.ds@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).