linux-kernel - Re: [PATCH -next] x86/kprobes: functions should not be declared extern

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 31 May 2021 12:39:54 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Qiheng Lin <linqiheng@...wei.com>
Cc:     tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
        hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] x86/kprobes: functions should not be declared
 extern

> Subject: Re: [PATCH -next] x86/kprobes: functions should not be declared extern

The condensed patch description in the subject line should start with a
uppercase letter and should be written in imperative tone.

Also, the subject is wrong. Hint: "declaration" vs "definition".

On Mon, May 31, 2021 at 11:10:09AM +0800, Qiheng Lin wrote:
> The function declaration in kprobes.h is already marked extern, thus its
> definition should not have the keyword.
>
> This quiets the following sparse warning:
>  function 'arch_unoptimize_kprobes' with external linkage has definition

This sounds like you're fixing something just because some tool
complains and not because there's a real problem you're fixing.

Please rewrite your commit messages to state what the problem is and
why you're fixing that problem. The tool output can be used to say
something along the lines of "this problem was caught by this tool" but
not as "see, tool X complains and creates a warning and I must fix that
warning immediately."

Ok?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette