[<prev] [next>] [day] [month] [year] [list]
Message-Id: <06ecf4d9-80d7-fbfd-3f95-9241d8d0d5cd@linux.ibm.com>
Date: Tue, 7 Apr 2020 16:23:06 +1000
From: Andrew Donnellan <ajd@...ux.ibm.com>
To: Andrew Melnichenko <andrew@...nix.com>
Cc: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
jslaby@...e.com, virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH] Fix: buffer overflow during hvc_alloc().
On 6/4/20 6:05 pm, Andrew Melnichenko wrote:
>
> Steps to Reproduce:
>
> 1. boot guest with command [1]
> 2. load and unload virtio_console inside guest with loop.sh
> # cat loop.sh
> while [ 1 ]
> do
> modprobe virtio_console
> lsmod | grep virt
> modprobe -r virtio_console
> lsmod | grep virt
> done
>
>
>
> Actual results:
> Guest reboot and can get vmcore-dmesg.txt file
>
>
> Expected results:
> Guest works well without error
>
>
> Additional info:
> The whole log will attach to the attachments.
>
> Call Trace:
> [ 22.974500] fuse: init (API version 7.31)
> [ 81.498208] ------------[ cut here ]------------
> [ 81.499263] pvqspinlock: lock 0xffffffff92080020 has corrupted
> value 0xc0774ca0!
> [ 81.501000] WARNING: CPU: 0 PID: 785 at
> kernel/locking/qspinlock_paravirt.h:500
[snip]
Thanks!
You should include an appropriate excerpt from this - the WARNING
message and stack trace, and the steps to reproduce - in the commit
message of the patch.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@...ux.ibm.com IBM Australia Limited
Powered by blists - more mailing lists