linux-kernel - Re: GPU-DRM-QXL: Move three assignments in qxl_device

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 for Android: free password hash cracker in your pocket

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

Date:   Thu, 22 Sep 2016 23:24:19 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc:     dri-devel@...ts.freedesktop.org,
        Bhaktipriya Shridhar <bhaktipriya96@...il.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        David Airlie <airlied@...ux.ie>,
        Noralf Trønnes <noralf@...nnes.org>,
        Tejun Heo <tj@...nel.org>, Thierry Reding <treding@...dia.com>,
        LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org,
        Julia Lawall <julia.lawall@...6.fr>
Subject: Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()

On Thu, Sep 22, 2016 at 03:11:25PM +0200, SF Markus Elfring wrote:
> > If you restricted yourself to fixing bugs only then you would maybe fix more
> > bugs than you introduce but as it you are making the kernel worse.
> 
> Would you like to discuss the statistics for my failure (or success) rate
> a bit more so that involved issues can be clarified in a constructive way?

It should be that you target 20 bug fixes for each new regression that
you add.

Since you are just sending clean ups, every bug you introduce sets us
further and further back.  There is no hope for improving the kernel
because you are not even trying to fix 20 bugs, only introducing them.

Once you fix 20 bugs, then you will be even and you can start sending
cleanups again.  This is fair.

regards,
dan carpenter