From: Francis Laniel <laniel_francis@privacyrequired.com>
To: akpm@linux-foundation.org
Cc: danielmicay@gmail.com, dja@axtens.net, keescook@chromium.org,
mm-commits@vger.kernel.org
Subject: Re: + correct-wrong-filenames-in-comment.patch added to -mm tree
Date: Tue, 24 Nov 2020 11:13:48 +0100 [thread overview]
Message-ID: <6349599.higeI0jBtf@machine> (raw)
In-Reply-To: <20201124011927.EkMZzlqAw%akpm@linux-foundation.org>
I am not sure if I should add a mailing list to this mail but thank you for
the addition of the patches!
Le mardi 24 novembre 2020, 02:19:27 CET akpm@linux-foundation.org a écrit :
> The patch titled
> Subject: drivers/misc/lkdtm/lkdtm.h: correct wrong filenames in comment
> has been added to the -mm tree. Its filename is
> correct-wrong-filenames-in-comment.patch
>
> This patch should soon appear at
>
> https://ozlabs.org/~akpm/mmots/broken-out/correct-wrong-filenames-in-commen
> t.patch and later at
>
> https://ozlabs.org/~akpm/mmotm/broken-out/correct-wrong-filenames-in-commen
> t.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when testing
> your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
>
> ------------------------------------------------------
> From: Francis Laniel <laniel_francis@privacyrequired.com>
> Subject: drivers/misc/lkdtm/lkdtm.h: correct wrong filenames in comment
>
> In lkdtm.h, files targeted in comments are named "lkdtm_file.c" while
> there are named "file.c" in directory.
>
> Link:
> https://lkml.kernel.org/r/20201122162451.27551-6-laniel_francis@privacyrequ
> ired.com Signed-off-by: Francis Laniel <laniel_francis@privacyrequired.com>
> Acked-by: Kees Cook <keescook@chromium.org>
> Cc: Daniel Axtens <dja@axtens.net>
> Cc: Daniel Micay <danielmicay@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/misc/lkdtm/lkdtm.h | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> --- a/drivers/misc/lkdtm/lkdtm.h~correct-wrong-filenames-in-comment
> +++ a/drivers/misc/lkdtm/lkdtm.h
> @@ -6,7 +6,7 @@
>
> #include <linux/kernel.h>
>
> -/* lkdtm_bugs.c */
> +/* bugs.c */
> void __init lkdtm_bugs_init(int *recur_param);
> void lkdtm_PANIC(void);
> void lkdtm_BUG(void);
> @@ -35,7 +35,7 @@ void lkdtm_CORRUPT_PAC(void);
> void lkdtm_FORTIFY_OBJECT(void);
> void lkdtm_FORTIFY_SUBOBJECT(void);
>
> -/* lkdtm_heap.c */
> +/* heap.c */
> void __init lkdtm_heap_init(void);
> void __exit lkdtm_heap_exit(void);
> void lkdtm_OVERWRITE_ALLOCATION(void);
> @@ -47,7 +47,7 @@ void lkdtm_SLAB_FREE_DOUBLE(void);
> void lkdtm_SLAB_FREE_CROSS(void);
> void lkdtm_SLAB_FREE_PAGE(void);
>
> -/* lkdtm_perms.c */
> +/* perms.c */
> void __init lkdtm_perms_init(void);
> void lkdtm_WRITE_RO(void);
> void lkdtm_WRITE_RO_AFTER_INIT(void);
> @@ -62,7 +62,7 @@ void lkdtm_EXEC_NULL(void);
> void lkdtm_ACCESS_USERSPACE(void);
> void lkdtm_ACCESS_NULL(void);
>
> -/* lkdtm_refcount.c */
> +/* refcount.c */
> void lkdtm_REFCOUNT_INC_OVERFLOW(void);
> void lkdtm_REFCOUNT_ADD_OVERFLOW(void);
> void lkdtm_REFCOUNT_INC_NOT_ZERO_OVERFLOW(void);
> @@ -83,10 +83,10 @@ void lkdtm_REFCOUNT_SUB_AND_TEST_SATURAT
> void lkdtm_REFCOUNT_TIMING(void);
> void lkdtm_ATOMIC_TIMING(void);
>
> -/* lkdtm_rodata.c */
> +/* rodata.c */
> void lkdtm_rodata_do_nothing(void);
>
> -/* lkdtm_usercopy.c */
> +/* usercopy.c */
> void __init lkdtm_usercopy_init(void);
> void __exit lkdtm_usercopy_exit(void);
> void lkdtm_USERCOPY_HEAP_SIZE_TO(void);
> @@ -98,7 +98,7 @@ void lkdtm_USERCOPY_STACK_FRAME_FROM(voi
> void lkdtm_USERCOPY_STACK_BEYOND(void);
> void lkdtm_USERCOPY_KERNEL(void);
>
> -/* lkdtm_stackleak.c */
> +/* stackleak.c */
> void lkdtm_STACKLEAK_ERASING(void);
>
> /* cfi.c */
> _
>
> Patches currently in -mm which might be from
> laniel_francis@privacyrequired.com are
>
> stringh-add-fortify-coverage-for-strscpy.patch
> add-new-file-in-lkdtm-to-test-fortified-strscpy.patch
> correct-wrong-filenames-in-comment.patch
prev parent reply other threads:[~2020-11-24 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 1:19 + correct-wrong-filenames-in-comment.patch added to -mm tree akpm
2020-11-24 10:13 ` Francis Laniel [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=6349599.higeI0jBtf@machine \
--to=laniel_francis@privacyrequired.com \
--cc=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--cc=dja@axtens.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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.