linux-kernel - Re: KVM: s390: Move two error code assignments in kvm_vm_ioctl_get_dirty

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, 23 Jan 2017 15:21:18 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc:     Christian Bornträger <borntraeger@...ibm.com>,
        kvm@...r.kernel.org, linux-s390@...r.kernel.org,
        Cornelia Huck <cornelia.huck@...ibm.com>,
        Heiko Carstens <heiko.carstens@...ibm.com>,
        Martin Schwidefsky <schwidefsky@...ibm.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org
Subject: Re: KVM: s390: Move two error code assignments in
 kvm_vm_ioctl_get_dirty_log()

On Mon, Jan 23, 2017 at 12:08:12PM +0100, SF Markus Elfring wrote:
> > but it certainly carries the risk of breaking something
> 
> This is usual in software development, isn't it?
> 

If you break something but you're trying to fix something then normally
you still end up fixing more than you break.  You haven't yet tried to
fix anything, but you've definitely introduced bugs...

We have had this discussion many times.

regards,
dan carpenter