linux-kernel - Re: [PATCH 0/2] ALSA: nm256: Fine-tuning for three function implementations

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:   Thu, 16 Nov 2017 18:15:23 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     "SF Markus Elfring" <elfring@...rs.sourceforge.net>
Cc:     <alsa-devel@...a-project.org>,
        "Arvind Yadav" <arvind.yadav.cs@...il.com>,
        "Jaroslav Kysela" <perex@...ex.cz>,
        "Takashi Sakamoto" <o-takashi@...amocchi.jp>,
        <kernel-janitors@...r.kernel.org>,
        "LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] ALSA: nm256: Fine-tuning for three function implementations

On Thu, 16 Nov 2017 18:05:27 +0100,
SF Markus Elfring wrote:
> 
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Thu, 16 Nov 2017 18:00:18 +0100
> 
> Two update suggestions were taken into account
> from static source code analysis.

Markus, I'd apply this kind of patches only when they are really
tested on the hardware, or they were converted systematically by a
script like spatch.  The reason is that you might break something (and
you already broke things in the past).  The merit by such a patch is
negligible in comparison of the risk of breakage.  These codes aren't
too bad without fixing, after all; everyone can read it pretty well as
is.

If these patches were tested on a real hardware, or at least on VM, so
that you can show that they don't break anything, I'll happily apply
them for the next (4.16) kernel.  In that case, please show that in 
the changelog explicitly.

Or, if you're really working on other real changes (no cosmetic coding
style fixes nor the code shuffling, but fixing a real bug) *and* such
a cleanup is mandatory as preliminary, it can be accepted, too.

thanks,

Takashi