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: <DS0PR11MB6373F27D0EE6CD28C784478BDCEC9@DS0PR11MB6373.namprd11.prod.outlook.com>
Date:   Mon, 26 Dec 2022 10:17:11 +0000
From:   "Wang, Wei W" <wei.w.wang@...el.com>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        "Christopherson,, Sean" <seanjc@...gle.com>
CC:     "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        柳菁峰 <liujingfeng@...nxin.com>
Subject: RE: [PATCH] KVM: Destroy target device if coalesced MMIO
 unregistration fails

On Saturday, December 24, 2022 1:14 AM, Paolo Bonzini wrote:
> On 12/20/22 04:04, Wang, Wei W wrote:
> > Another option is to let kvm_io_bus_unregister_dev handle this, and no
> > need for callers to make the extra kvm_iodevice_destructor() call.
> > This simplifies the usage for callers (e.g. reducing LOCs and no leakages like
> this):
> 
> Can you send this as a patch?  Thanks!

Sure. I can do it. I'm also fine if Sean would be interested in taking over the
code (or anything I should do to keep his credits for the original fixing?)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ