linux-kernel - Re: console: Complete exception handling in newport

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]

Message-ID: <68178ac9-ae0c-2f97-2620-38393741b3a1@web.de>
Date:   Thu, 23 Apr 2020 19:22:02 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Dejin Zheng <zhengdejin5@...il.com>,
        dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
        Coccinelle <cocci@...teme.lip6.fr>
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
        Florian Tobias Schandinat <FlorianSchandinat@....de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Ralf Bächle <ralf@...ux-mips.org>,
        Thomas Bogendörfer <tsbogend@...ha.franken.de>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: console: Complete exception handling in newport_probe()

>>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
…
> Sorry, I do not know how to use the SmPL script.

I proposed to take another look at the header of such a file.
I imagine that provided information can trigger further development ideas
for the continuation of a constructive patch review.


>> Would you like to let any more source code analysis tools help you
>> to find remaining update candidates?
>>
> yes, but I think the source code analysis tools only can found the simple
> repetitive issue.

I suggest to reconsider this view.


> and need spend some time learning to use it.

This approach can be usual.


> at different stages, it should have different methods for me.

I hope so.


> now, I think the best for me may be that read and check the source code.

This can be also usual for a while.

I am curious how much special tools can make your software developments
more convenient and safe over time.

Regards,
Markus