* Jiri Slaby <[email protected]> wrote:
> Stanse found that there is an omitted unlock in kvm_create_pit in one fail
> path. Add proper unlock there.
>
> Signed-off-by: Jiri Slaby <[email protected]>
> Cc: Avi Kivity <[email protected]>
> Cc: Marcelo Tosatti <[email protected]>
> Cc: Thomas Gleixner <[email protected]>
> Cc: Ingo Molnar <[email protected]>
> Cc: "H. Peter Anvin" <[email protected]>
> Cc: [email protected]
> Cc: Gleb Natapov <[email protected]>
> Cc: "Michael S. Tsirkin" <[email protected]>
> Cc: Gregory Haskins <[email protected]>
> Cc: [email protected]
> ---
> arch/x86/kvm/i8254.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c
> index 467cc47..70db4d4 100644
> --- a/arch/x86/kvm/i8254.c
> +++ b/arch/x86/kvm/i8254.c
> @@ -696,6 +696,7 @@ struct kvm_pit *kvm_create_pit(struct kvm *kvm, u32 flags)
>
> pit->wq = create_singlethread_workqueue("kvm-pit-wq");
> if (!pit->wq) {
> + mutex_unlock(&pit->pit_state.lock);
> kfree(pit);
> return NULL;
> }
A cleanliness comment: why is that tear-down/dealloc sequence open-coded? It
should be at the end of the function, with goto labels, like we do it in
similar cases.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
