All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oscar Megia López" <megia.oscar@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: Contributing subsequent patch versions
Date: Sun, 30 Jul 2023 09:56:51 +0200	[thread overview]
Message-ID: <87leexn870.fsf@gmail.com> (raw)
In-Reply-To: <27a41740-9cdd-2adf-f3cc-1f9a2d9f2ed1@web.de> (Markus Elfring's message of "Sat, 29 Jul 2023 07:34:47 +0200")

Markus Elfring <Markus.Elfring@web.de> writes:

>> Sorry, but my experience says that is very easy make mistakes
>> when I am newbie.
>
> Which kind of errors would you like to produce if you would become
> an “expert” (like a system tester) in additional areas?
>
> Regards,
> Markus

I don't know, but what I've observed during my years working in IT is
that I come up with tests that no one else does. This way I find bugs
that no one else finds.

For example, I forked the project https://github.com/pixel/hexedit and
tried to find errors. I found many, such as what happens if you try to
load a very long filename, what happens if you try to load a very large
file, etc. I fixed them all, but because maintaner didn't accept my
first patch, I didn't carry on.

If anyone is interested in me testing their patch, I would love to do
it. Now I'm reading LINUX KERNEL DEBUGGING book (written by Kaiwan N
Billimoria) and I'm on chapter about strace and some tools like lttng,
so I can use these tools mentioned on book to test patches.

-- 
Un saludo/Regards
Oscar Megia López

      parent reply	other threads:[~2023-07-30  7:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 18:06 I need help to send v2 patch on linux-ext4 at vger.kernel.org Oscar Megia López
     [not found] ` <8ef54195-4102-0c6c-e14d-efc9bc45cddc@web.de>
2023-07-28  6:22   ` Contributing subsequent patch versions Oscar Megia López
2023-07-28 18:10     ` Theodore Ts'o
2023-07-30  6:23       ` Oscar Megia López
2023-07-30  8:23         ` Markus Elfring
2023-07-30 10:12           ` Greg KH
2023-07-30 10:12             ` Greg KH
     [not found]     ` <61a79836-3981-b6e0-cbbf-fe03507dbea4@web.de>
2023-07-28 18:36       ` Oscar Megia López
2023-07-28 19:59         ` Theodore Ts'o
2023-07-30  7:10           ` Oscar Megia López
     [not found]         ` <27a41740-9cdd-2adf-f3cc-1f9a2d9f2ed1@web.de>
2023-07-30  7:56           ` Oscar Megia López [this message]

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=87leexn870.fsf@gmail.com \
    --to=megia.oscar@gmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=error27@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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.