All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Huang Adrian <adrianhuang0701@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Adrian Huang <ahuang12@lenovo.com>
Subject: Re: [PATCH 1/1] exec: fix typo and grammar mistake in comment
Date: Wed, 25 Aug 2021 22:31:56 -0700	[thread overview]
Message-ID: <465a5f46-59e2-9999-9176-77ba63731dd7@infradead.org> (raw)
In-Reply-To: <CAHKZfL1H2LKnOw1EfNA-xri0EPDF-hYwXa1u_39ttoMZHvSOGg@mail.gmail.com>

On 8/25/21 10:25 PM, Huang Adrian wrote:
> On Thu, Aug 26, 2021 at 11:27 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 8/25/21 8:14 PM, Adrian Huang wrote:
>>> From: Adrian Huang <ahuang12@lenovo.com>
>>>
>>> 1. backwords -> backwards
>>> 2. Remove 'and'
>>
>>     3. correct the possessive form of "process"
>>
>>>
>>> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
>>> ---
>>>    fs/exec.c | 4 ++--
>>>    1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/exec.c b/fs/exec.c
>>> index 38f63451b928..7178aee0d781 100644
>>> --- a/fs/exec.c
>>> +++ b/fs/exec.c
>>> @@ -533,7 +533,7 @@ static int copy_strings(int argc, struct user_arg_ptr argv,
>>>                if (!valid_arg_len(bprm, len))
>>>                        goto out;
>>>
>>> -             /* We're going to work our way backwords. */
>>
>> That could just be a pun. Maybe Al knows...
> 
> Another comment in line 615 has the same sentence with 'backwards'.
> (https://github.com/torvalds/linux/blob/master/fs/exec.c#L615).
> 
> So, one of them should be corrected.

OK.

>>
>>> +             /* We're going to work our way backwards. */
>>>                pos = bprm->p;
>>>                str += len;
>>>                bprm->p -= len;
>>> @@ -600,7 +600,7 @@ static int copy_strings(int argc, struct user_arg_ptr argv,
>>>    }
>>>
>>>    /*
>>> - * Copy and argument/environment string from the kernel to the processes stack.
>>> + * Copy argument/environment strings from the kernel to the processe's stack.

I think this one should be:
       * Copy an argument/environment string from the kernel to the process's stack.

>> Either process's stack or process' stack. Not what is typed there.
>> I prefer process's, just as this reference does:
>>     https://forum.wordreference.com/threads/process-or-processs.1704502/
> 
> Oh, my bad. I should have deleted the letter 'e'. Thanks for this.
> 
> After Al confirms 'backwords', I'll also change "processes's" to
> "process's" in v2.
> (https://github.com/torvalds/linux/blob/master/fs/exec.c#L507)
> 
>>>     */
>>>    int copy_string_kernel(const char *arg, struct linux_binprm *bprm)
>>>    {


-- 
~Randy


      reply	other threads:[~2021-08-26  5:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  3:14 [PATCH 1/1] exec: fix typo and grammar mistake in comment Adrian Huang
2021-08-26  3:27 ` Randy Dunlap
2021-08-26  5:25   ` Huang Adrian
2021-08-26  5:31     ` Randy Dunlap [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=465a5f46-59e2-9999-9176-77ba63731dd7@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=adrianhuang0701@gmail.com \
    --cc=ahuang12@lenovo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.