linux-kernel - Re: [PATCH] EDAC, sb_edac: remove redundant update of tad

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] [day] [month] [year] [list]

Message-ID: <20190509150146.GE17053@zn.tnic>
Date:   Thu, 9 May 2019 17:01:46 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Colin Ian King <colin.king@...onical.com>
Cc:     Tony Luck <tony.luck@...el.com>, Qiuxu Zhuo <qiuxu.zhuo@...el.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        James Morse <james.morse@....com>, linux-edac@...r.kernel.org,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] EDAC, sb_edac: remove redundant update of tad_base

On Thu, May 09, 2019 at 03:55:32PM +0100, Colin Ian King wrote:
> Yep, I agree, but explaining all the Coverity error types in a kernel
> doc is going to take some effort, which I really don't have much time
> for at the moment.

I'm not suggesting you should document them all or write a comprehensive
howto on how to run Coverity - all I'm suggesting is starting a small
doc somewhere in Documentation/ which contains some info on what all
those tools tags we use, mean and how people can find the information
they contain. Basically what you said above (which I've snipped).

But it would be a lot more helpful if it is written down so that people
can look it up. Also, that doc will serve as a documentation of all
those tags we're using in the kernel and what their format, etc would
be.

Otherwise we'll have the current head scratching when a tag like that is
encountered...

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.