linux-kernel - Re: [PATCH] Spell fix in fs/proc/kcore.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Mar 2012 14:24:46 +0200
From:	Daniel Baluta <daniel.baluta@...il.com>
To:	Laura Vasilescu <laura@...edu.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Spell fix in fs/proc/kcore.c

On Mon, Mar 19, 2012 at 1:36 PM, Laura Vasilescu <laura@...edu.org> wrote:
> ---
>  fs/proc/kcore.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/proc/kcore.c b/fs/proc/kcore.c
> index d245cb2..e5e69af 100644
> --- a/fs/proc/kcore.c
> +++ b/fs/proc/kcore.c
> @@ -513,7 +513,7 @@ read_kcore(struct file *file, char __user *buffer, size_t buflen, loff_t *fpos)
>
>                                n = copy_to_user(buffer, (char *)start, tsz);
>                                /*
> -                                * We cannot distingush between fault on source
> +                                * We cannot distinguish between fault on source
>                                 * and fault on destination. When this happens
>                                 * we clear too and hope it will trigger the
>                                 * EFAULT again.
> --
> 1.7.2.5

That's nice. Thanks for your contribution.

Anyhow, please review this:
* add a Signed-off-by line
* add a proper prefix to Subject (e.g: kcore: spell fix in ... )
* don't forget to Cc the maintainers (run ./scripts/get_maintainer.pl
<your_patch>)

Daniel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/